Cool, makes you wonder how many more of these oneliners are scattered across the codebase (in application and also OS etc).
Sidenote, I wonder how close we are to detect these automatically. From profiling many various applications, it feels like that should be a tractable problem.
I'm more curious on how much manual effort was required to find said line of code? Strikes me as moest of these optimizations are super easy to verify, very difficult to find
What part of the stack takes the majority of the time for spawning a new replica? Is it the time to boot a VM/environment or is it application doing bunch of init work setting up connections etc?
Would this work for hosting databases too? I found the biggest annoyance and expense on my "infrequently accessed" side projects are databases, which are almost always idle.
> I've discovered recently that tire wear actually creates about as many particles as exhaust fumes,
> And the worst part for the wire tear (and I think road tear), apparently it scales to the POWER OF 4 (!!!).
That's very interesting. I'm a default sceptic, but would love to learn more, because if true, that could nullify a lot of the local air arguments. Do you have any sources for these?