6 ms·
I refreshed the page after 60 seconds to estimate how many people are clicking, and it came to 4.9 requests per second. All of a sudden I don't have as much sym
by throwup 4y ago
I refreshed the page after 60 seconds to estimate how many people are clicking, and it came to 4.9 requests per second. All of a sudden I don't have as much sympathy for HN knocking someone's site offline when it's just a static blog filled with text.
- codazoda 4y agoYeah, it’s no big deal for static content. My little Raspberry Pi had no trouble with it even though it uses a SQLite DB. https://joeldare.com/private-analtyics-and-my-raspberry-pi-400 https://joeldare.com/private-analtyics-and-my-raspberry-pi-4... Granted, it was a Sunday.
- datalopers 4y agoHN volume is pretty weak tbh. Web devs are just getting worse.
- taspeotis 4y agoPretty easy problem to solve too - just scale up the static asset Kubernetes cluster‽
- squeaky-clean 4y agoI'm seeing about 20 per second by doing the same method. Still nothing crazy, but it probably needs a bit more time at the top of HN
- marcus_cemes 4y agoProbably more to do with the fact that people are mashing F5 to see the difference.
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- arjvik 4y agoRefreshing every second and mentally averaging, I'm getting closer to 15-20 requests per second. But yes, only a badly designed static site should be crashing under that load (unless it's on a residential connection, perhaps it's ISP rate limiting?)
- gus_massa 4y agoAs a rule of thumb, if the post get N upvotes, you get 100N+50 visits. YYMV. The post has now 76 points in 40 minutes, so an average of (76*100+50)/40/60 ~= 3.2 that is close to your 4.9. But the peak may be much higher, like the 20/s reported by other users.