strange behaviour for test connection

[futurnet]

when I test my connection, nhp tell me that 40 threads are the optimum tune, but I can use up to 300 threads without any problem for check proxy, even ewith nhp too.
So, is this a bug of NHP?

My isp connection is:
ADSL 384 kb upstream - 7 Mb downstream
I am connected to my router by ethernet cable

[jimbobo2779]

If your connection is a 7Mb connection it is unlikely it would be able to sustain anywhere near 300 threads. At 7Mb I would guess it could handle around 30-50 so if NHP is reporting 40 I would say that is about right.

You could see for yourself by running at 300 and then running at 40 to see how the results compare. I have an 8Mb connection and run at 35 threads on my own dev machine, when I was running at 100 threads on the same connectioin I was getting less proxies found and more were failing because they were timing out. That is the issue, your connection can likely handle as many connections as you set it at providing you increase the timeouts accordingly as so many more connections will timeout when you have such a large amount of threads running at once.

If you find good success running at 300 threads compared to 40 then by all means run at 300 but it isn't a bug in the thread checker it is just checking connections within the timeout and when more are starting to fail it is reporting that as the cut off point.

[futurnet]

ok jimbobo, your point is interesting to investigate, in the next couple of days I will tune my threads to 40 to test, but I guess you right.

EDIT: I make the test right now, I test 1600 proxy:

300 threads = only 630 working proxy
40 threads = 1300 working proxy

no other comment need...