As long as your CPU can handle the multi-threading for each bot instance and you have enough memory for storage of POST/GET response data, there is NO reason whatsoever for you to use less than full 250 bots on a proxied config.

I mean, your bots are proxied and proxies swapped out automatically upon ban so using lower bots on a proxied config is doing nothing but slowing the cracking process.. I understand lower bots on a proxyless config to avoid being rate-limited though..

TL;DR :: It's safe to use as many bots as you want on a proxied config, providing your CPU can handle the workload and you have sufficient RAM

There is a reason sadly, some companies are checking traffics and detecting brute force attacks so when you use 250 bots (or more) with proxies you have more chance to be detected. That's why some sites are adding something like reCaptcha just after trying to crack with config proxyless or with proxies.
The best way is to use HQ Private socks5 proxies and limited to 50 proxies max.
It's my own opinion of course.

(05-20-2017, 09:22 PM)Robot Wrote: There is a reason sadly, some companies are checking traffics and detecting brute force attacks so when you use 250 bots (or more) with proxies you have more chance to be detected. That's why some sites are adding something like reCaptcha just after trying to crack with config proxyless or with proxies.
The best way is to use HQ Private socks5 proxies and limited to 50 proxies max.
It's my own opinion of course.

-Robot

You're talking about rate-limiting, which is done at IP-level..
Proxies can only be rate-limited if there are more bots than proxies.
If you have >3000 proxies and only a 2000 combo then guaranteed you can't get ratelimited because more than enough proxies, when a proxy is rate-limited it is automatically swapped out (if your config has AfterFingerprint)