3 ms·
> The best way to mitigate the load from diffuse, unidentifiable, grey area participants is to have a fast and well engineered web product. I wonder what all t
by threeducks 1y ago
> The best way to mitigate the load from diffuse, unidentifiable, grey area participants is to have a fast and well engineered web product.
I wonder what all those people are doing that their server can't handle the traffic. Wouldn't a simple IP-based rate limit be sufficient? I only pay $1 per month for my VPS, and even that piece of trash can handle 1000s of requests per second.
- micahdeath 1y agoWe have some bots that use residential IP blocks (including TMobile, AT&T, Verizon, etc)... When they hit, it's 1 request per IP, but they use 1000 IPs easily. Then we don't see that IP again for a week or more.
- rollcat 1y ago> I only pay $1 per month for my VPS, and even that piece of trash can handle 1000s of requests per second. Depends on the computational cost per request. If you're serving static content from memory, 10k/s sounds easy. If you constantly have to calculate diffs across ranges of commits, I imagine a couple dozen can bring your box down. Also: who's your webhost? $1/m sounds like a steal.
- immibis 1y agoYou can sometimes find special (loss-leader) deals in this range on LowEndTalk. Typically you'll have to pay upfront for a block of one or two years.
- TylerE 1y agoIt starting hitting endpoints that do lots of db thrashing, and it’s usually ones that are NOT common or recent so caching won’t save you. Serving up a page that takes a few dozen db queries is a lot different than serving a static page.
- TZubiri 1y agoI'd wager a bet that there's a package.json lying somewhere that holds a lot of dependencies