mirror of
https://github.com/transmission/transmission
synced 2024-12-27 18:18:10 +00:00
(trunk libT) There seems to be a lot of talk about T hosing routers, preventing other network traffic, etc. As an experiment let's try reducing the number of new connections we allow per second and see if/how that affects performance.
This commit is contained in:
parent
ae5c51060c
commit
2acc006807
1 changed files with 2 additions and 2 deletions
|
@ -63,11 +63,11 @@ enum
|
||||||
MAX_UPLOAD_IDLE_SECS = ( 60 * 5 ),
|
MAX_UPLOAD_IDLE_SECS = ( 60 * 5 ),
|
||||||
|
|
||||||
/* max # of peers to ask fer per torrent per reconnect pulse */
|
/* max # of peers to ask fer per torrent per reconnect pulse */
|
||||||
MAX_RECONNECTIONS_PER_PULSE = 16,
|
MAX_RECONNECTIONS_PER_PULSE = 8,
|
||||||
|
|
||||||
/* max number of peers to ask for per second overall.
|
/* max number of peers to ask for per second overall.
|
||||||
* this throttle is to avoid overloading the router */
|
* this throttle is to avoid overloading the router */
|
||||||
MAX_CONNECTIONS_PER_SECOND = 32,
|
MAX_CONNECTIONS_PER_SECOND = 16,
|
||||||
|
|
||||||
/* number of bad pieces a peer is allowed to send before we ban them */
|
/* number of bad pieces a peer is allowed to send before we ban them */
|
||||||
MAX_BAD_PIECES_PER_PEER = 5,
|
MAX_BAD_PIECES_PER_PEER = 5,
|
||||||
|
|
Loading…
Reference in a new issue