DeatheCore
Senior Member
Yeah that's a strange one tbh.. don't think SABnzbd manipulates packet size outside of the usual tcp norms, and has the ability to utilize more simultaneous connections/tcp threads based on your config. Do you trigger the DDoS protection when downloading something with a download manager, like IDM, with say 8 threads?I don't need to max it out, but what's the point of having gigabit and only being able to reach 300mbps on downloads? That's like buying a ferrari, and someone asking "Why do you need to go fast? Driving at the speed of a bus will still get you there?"
Anyhow, the issue isn't maxing it out, but that ANY NNTP download for me gets me blackholed by the DDoS protection software. @websquadza has explained the reason behind it and it's understandable, I'm just not enjoying being cut off for a few minutes every time NNTP is active, hence the request for a solution or a downgrade.
In my testing with SAB rate limiting, there is barely any difference in pps between 50MB/s @ 50 threads or 50MB/s @ 25 threads. Firstly both were able to saturature the 50MB/s limit. The difference I did notice however was the inconsistency in pps - higher initial burst, more spikes (higher and lower), and higher tcp error count @ 50 threads.
Lastly, downloading a youtube video with IDM, speed unrestricted, 8 threads yielded similar pps results to the SAB tests. You can check the graphs here if you want:
Obviously there are many differences between our two setups, like usenet server, ISP, FNO, LAN, etc.. also, I'm no expert in this stuff, just curious