The actual blog post on this is more interesting.
Cloudflare’s blog posts are always more interesting. They have a really good postmortem process.
Thats wild. The last part about using the savings for their cache, did they mean the CDN type stuff or was that something related to the 1.1.1.1 stuff?
Either way their plans to use the new excess for the cache will further make things faster for everyone.
thank you for sharing this. very cool read
One silver lining about the component restraints, hopefully it drives people to start creating efficient software again. Actually optimizing what you’re doing to save on RAM rather than a gig per tab in Chrome.
“Claude, make this software more efficient.”
Wish that was the case for a lot of new video games instead of relying on DLSS or FSR to cover up their poor optimisation
Picture the level of quality and performance we could have if we had both traditional optimization AND upscaling optimization AND frame gen optimization.
Cause holy fuck the number of times I’ve seen fsr/dlss slaped onto a game and no effort put into making it perform well.
Cause there IS work you can do to make fsr/dlss actually look good and perform better.
I’m in a community making open source firmware for the Centauri Carbon 3d printer. The thing has 128MB of of RAM. The smarter people in the community worked some magic getting Klipper working on these things, and we’re still fighting to shave off a couple more MB in average use to get things working smoother.
Talk to the folks running Linux on sn esp32! That’s some shrinking
Seems to me like everything is instead becoming even more bloated with AI stuff. A Google chat tab uses 2 GIGABYTES on my work computer.
Yes!
stupid RAM price benefit: reduce bloat
AI IS THE GREATEST THING TO HAPPEN TO MANKIND (ignore literally everything else)
I never even thought about this before, but what kind of hardware is a root level DNS server like 1.1.1.1 or quad 8 run on? Are they all roughly the same, or do they take different approaches to the load?
Bit of a nitpick, but these providers are not running root servers. They’re just recursive caching servers, probably running unbound.
If you want to find out root servers - dig for
.- that’s a dot. A full stop. That’s the root. Those can then answer where to find your .coms, .nets, etc. Those, in turn, handle the domain you rent; so on and so forth.Dang. They do it all in one Pizza box. I figured it would be a whole rack per unit.
Most probably off-the-shelf hardware, but with software optimized out the wazoo. Like, reading directly from SSDs instead of using a filesystem. Or more likely using an in-memory database like Redis, perhaps with custom additions.
I knew a guy who went on to work for CloudFlare. Back at that job, he made a write-only static-file storage in Node.js, dumping the contents into a giant file bypassing the filesystem and its metadata overhead. That’s the kind of optimization you want — pretty similar to what database engines like MySQL/PostgreSQL do (iirc one of them does in fact support using a plain disk partition for the database).
Back in early-mid 2010s I’ve read an article on Pornhub’s architecture. They ran Redis behind Haproxy load balancers. An in-memory database, behind load balancers. Some people say that it’s normal, but I’ve never had conditions calling for such a thing instead of sharding harder.
Look up how Cloudflare does anycast BGP. They have servers in data centers everywhere and leverage the fact that they can all be 1.1.1.1 so people’s queries only hit the physically closest server, it’s pretty cool
40 bytes are saved, exactly this amount.
40 bytes, per record. 533 bytes per entry. 3-4 GB total savings on an instance.
