4 ms·
It would be great if the author of this post could respond here with how many requests per second it took to bring down the site... I assume using a RPi is stil
by chrisshroba 6y ago
It would be great if the author of this post could respond here with how many requests per second it took to bring down the site... I assume using a RPi is still a viable solution for 99% of the time
- jandrese 6y agoI wonder if he was running a database driven site off of his Pi? It wouldn't take many queries per second to kill off something running on a SD card. A static site would probably be able to saturate the Ethernet before the Pi gave up. Even old Pentiums could saturate Fast Ethernet, although the Pi is penalized because the Ethernet runs off of USB so its extra processor intensive. Edit: is blog is back up. It apparently run on Node, and most of the article is about how you break through multiple layers of NAT via a Google service. Very useful if you are hosting your blog off of your cell service or something, although someone with a regular router on a regular ISP can just port forward and set up dynamic DNS to avoid the headache of a Google service that will be discontinued in a year or two.
- qubex 6y agoI don’t disagree, but I think the PRi 4 no longer suffers from the USB-Ethernet bottleneck (never pushed my 3 and 4 hard enough to notice, to be honest).
- jandrese 6y agoEven if it isn't the bottleneck, running the Ethernet over USB means the CPU has to get involved to do all of the Bus Mastering, which cuts into cycles it could be spending on preparing the packets.