[atanasb]

> To slow down or stop attacks, we limit requests made by a specific user / IP. [...] While that confirms that we can limit unauthorized and bad users who make too many requests, the testing failed because we also blocked the simulated good users on the same IP.

I don't understand the problem this is trying to solve. In the test setup both good and malicious actors are simulated on the same IP address (which coincidentally might also be a real world situation).

So you're trying to load test - but failing because you get throttled/rate-limited - which is good.

But how does Squid help in this case - doesn't it just mask away the actual load by caching content?

In that case are you actually testing the ControlAPI load - or how good Squid's caching is?

Aside from that - pretty interesting read. Would live to see a bit more technical detail and depth for the next blog post!