Remix clone Hacker News

By the way how much malice can we attribute to cloud vendors?

>Moreover, Kubernetes’s slow autoscaling meant I had to over-provision services to ensure availability, paying for unused resources rather than scaling based on demand.

A typical Linux instance on AWS starts up in about 8 seconds from the asking to start to command line, so lets double that. You could start up and shut down instances in 15 seconds.

Why the hell do you need to overprovision instances then, or leave empty ones running?

I don't see any other reasonable explanation than its in the best interest of cloud vendors to not have short lived instances for the purposes of load balancing, as well as make you consume as much CPU time as possible, even if you don't need it.

▲

p_l 3 months ago | parent [-]

TL;DR someone didn't learn to plan capacity.

	▲	torginus 2 months ago \| parent [-]
		I don't like that enshittification of technology has created an entire profession around babying pretend servers - if the cloud lived up to the promise of being an operating system for a global server farm, capacity scaling would consist of a new computer being allocated in ~1ms, said computer downloading my 100MB binary in ~10ms and loading it into memory and jumping to the first instruction in ~0ms. And I'm being generous with the timings.You could literally spin up a server in the time it takes to process a request. If I write a program and decide to start a new thread, I don't need a dedicated ThreadOps professional moralizing about how I should've configured my app in the yaml file to use 2 threads instead of 1. I have long held the belief that the clowning around that happens in IT nowadays is the opposite of engineering.