[jart]

That's because people are so accustomed to leveraging mountains of free candy that they've forgotten that a web page can be served with less than 1000ms of cpu time. I got a job once when I told a story about a web app I wrote was going viral getting a million visitors a day while I was strolling in the park. The web servers I write only need a single system call (writev) to serve gzip encoded assets so wrk says they can do a million requests per second on one pc. So it's not like it was any kind of big technical achievement even though it was a technical job. My point is that we're drowning in so much software that sometimes being a master class engineer all it takes is not using it.

[contingencies]

We're drowning in so much software that sometimes being a master class engineer all it takes is not using it.

Love it. Added to https://github.com/globalcitizen/taoup

[eternityforest]

I really think we need a major shift in how we handle static content. This stuff should be near zero-cost by now.

Ideally so cheap that your ISP has a CDN and publishers pay nothing to get them to cache it, it's just included in your internet service. For some people things could even be cached temporarily at the building level.

SSDs are very fast and hardware acceleration exists. Why so we need such massive servers in a data center?

A movie is only 90 minutes. A single disk and some ASICs should be able to serve tens of thousands of people, if you could make dedicated hardware without all the stuff that's irrelevant for streams, just a bunch of cores with DMA going straight into crypto and out a bunch of Ethernet ports.

If we can make a tiny 10 gigabit swith with tons of ports in one rack, why can we not add some sticks of ram and do CDNs in hardware?

[lionkor]

Do you have the source code published somewhere? I'd be very curious. My current implementation uses mmap and send(), so id love to get it faster than that.

[jart]

It's called redbean.