4 ms·
In addition to performance it also has to do with politeness: it’s not polite to ask for the same resources again and again from a server when you could cache i
by hk__2 2y ago
In addition to performance it also has to do with politeness: it’s not polite to ask for the same resources again and again from a server when you could cache it, especially when it has explicit headers about it in its response. Think of small self-hosted blogs with hundreds of readers that constantly poll it.
- cogman10 2y agoEven with a small self-hosted blog, assuming you have more than a 56k hookup to the internet, a raspberry pi can service up 100s of requests per second. At the time of writing this, the HN rss feed is 12kb. That'd mean you'd need 10Mbps upload to handle 100s of requests to the rss feed per second. (Again, not saying you shouldn't optimize this, just questioning how big a problem it is).
- deleted 2y ago[deleted]
- DamonHD 2y agoWhen I was being low-grade DDoSed the other day my off-grid RPi3B server was taken out by ~60 bogus requests per second. It is otherwise entirely happy with normal HTTP loads, plus being primary DNS server, SMTP, NTP, ... One podcaster halved its bandwidth bill overnight getting just one of these fixed, see "A saving bandwidth special!": https://podnews.net/update/podlp-cloud-phone https://podnews.net/update/podlp-cloud-phone