Hello,

I was just wondering, why there is such a low limit for the peers requested from a http tracker (numwant=100) as many trackers offer at least 200.

In the same context, is there a reason why there is a hard limit for the potential peer size of 150? (libbtcore/peer/peermanager.cpp -> PeerManager::addPotentialPeer)
I hit the limit even without changing the number of requested peers several times.

When increasing both numbers I immediately got a nice boost in the number of connected peers.

So I guess it wouldn't be bad to increase the maximum queue size to 300-400 and the numwant to 200 or make the latter configurable.

Or is there a strong reason against it?!

liquidfoo wrote:Hello,

I was just wondering, why there is such a low limit for the peers requested from a http tracker (numwant=100) as many trackers offer at least 200.

In the same context, is there a reason why there is a hard limit for the potential peer size of 150? (libbtcore/peer/peermanager.cpp -> PeerManager::addPotentialPeer)
I hit the limit even without changing the number of requested peers several times.

When increasing both numbers I immediately got a nice boost in the number of connected peers.

So I guess it wouldn't be bad to increase the maximum queue size to 300-400 and the numwant to 200 or make the latter configurable.

Or is there a strong reason against it?!

Not really, it seemed like enough at the time, and hasn't changed since.

I will increase them to 200 for numwant and 500 potential peers.

Great!

Thanks for the quick response and heads up.