Yes, it looks like that. When I started noticing issues, the status page hadn't been updated yet. Uff, they've been having a rough time.

I hear cpu and motherboard prices are expected to increase soon as well fyi

Someone on our team bought 192gb for just under $600 a few months ago 😭

Omg same, so frustrated with memory processing that I gave up after all.

Not exactly the same thing but we’ve been creating jobs from sql databases for some time with this github.com/brancz/locutus

It only works out to be beneficial if each request is relatively large, which happens to be the case for our product.

It’s somewhat specific to what I want to do. I want to route the same customer’s traffic to the same zone in GCP. Within that zone I run a load balancer infra structure myself with eg. nginx. Ingress traffic itself is free on cloud providers. So I use workers as my global load balancer.

Back of the envelope says we'd be ~40% less with Cloudflare workes. Interesting! Probably not enough to warrant the change at the moment, but good exercise.

I have to do some calculations, but Cloudflare workers could be interesting!

developers.cloudflare.com/workers/plat...

No no, the target directory holds build caches etc. as well. The binaries are still big though (100mb without and 1gb with debuginfos each).

I see, never heard of the term. In that case, no not at all. These binaries depend on libc and Linux more generally a lot.

What do you mean by free standing binaries?