5 ms·
How bad is the HN hug of death btw? My laptop can serve 200k QPS per core. I can't imagine HN is that much more intensive? Are 1vCPU VMs just that much worse?
by hansvm 2y ago
How bad is the HN hug of death btw? My laptop can serve 200k QPS per core. I can't imagine HN is that much more intensive? Are 1vCPU VMs just that much worse?
- thornewolf 2y agoYour laptop can serve 200k qps per core?
- hansvm 2y agoTo be fair, most modern computers can, but yes.
- lelandbatey 2y agoYes, they are much worse than bon-fide actual single cores on most recently purchased laptops. But also, the HN hug of death mostly happens with tiny non-static sites that are sloppily hosted. If you're serving static assets it's hard to "hug of death" a Casio watch.
- derefr 2y agoThe thing that gets saturated first for most at-home or cheap-VPS hosting is the low-throughput network uplink.
- deleted 2y ago[deleted]
- eptcyka 2y agoCan you serve 200GB of an average 1mb large HTML page per second too, per core?
- hansvm 2y agoNo, definitely not.
- pauldraper 2y agoHoly crap what kind of laptop are you running?
- chena12 2y ago[dead]
- hansvm 2y agoM3 at work, Acer Swift 3 at home. Both are comparable in that regard. You can do 200k QPS of actual work (a little protobuf parsing, a little old-school ML, handling the networking, a little HTTP1.1 parsing, ...), more if you just want vanity metrics, just by wrapping something like uSockets [0] and not doing anything to explicitly pessimize the system. You can do better with a hand-crafted solution, but most projects don't need anything fancier. [0] https://github.com/uNetworking/uSockets https://github.com/uNetworking/uSockets
- pauldraper 2y agoContext is a website, so HTTPS requests per second would be the relevant metric.
- hansvm 2y agoI'm also quoting HTTPS requests per second.