[jeffbee]

This is an aburdly bad result, mostly caused by the questionable 14W base power draw, but also due to the questionable choice of gzip compression, which is not exactly on the frontier of compression technology. Even zlib-deflate would decompress twice as fast at the same size ratios, but something like lz4 or snappy would be an order of magnitude less CPU time cost for similar compressed size.

The real way to have an energy-efficient service is to amortize away your idle usage and all of these inefficient conversion steps by just hosting your junk on App Engine.

[forkfork]

I’ll iterate towards a good solution. This was a somewhat realistic but naive solution (I have customers doing largely what I’ve described in the article).

If I could find a way to encourage people to run their work in a power efficient way using economies of scale from this series, I would be terribly happy.

Interestingly I suspect public-cloud FaaS solutions (e.g. AWS Lambda) will achieve highest utilisation rates due to high rate of CPU sharing - but I’m a long way off from showing that with data.