About seeding

[GoogleCodeExporter]

What steps will reproduce the problem?
1.I use libtorrent to seeding several thousand torrents, at the beginning
  it can use all my upload bandwidth(about 2.5 MB/s), but some times later the upload speed drop to about 500 KB/s.  
2.I restart it then it up to 2.5MB/s but some times later(several hours)
  it drop to several hundreds KB/s.
3.

What is the expected output? What do you see instead?
I expect it can stable.

What version of the product are you using? On what operating system?
libtorrent 0.16.13
OS: windows server 2008 R2

Please provide any additional information below.
My IP is static.

libtorrent settings as follows:

alert_queue_size = 6000000;
lazy_bitfields = true;
stop_tracker_timeout = 1;
auto_scrape_interval = 1200; // 20 minutes
announce_to_all_trackers = true;
announce_to_all_tiers = true;
auto_scrape_min_interval = 900; // 15 minutes
cache_size = 128 * 64;// 128 MB
dont_count_slow_torrents = true
active_seeds = -1;
active_limit = -1;
enable_incoming_utp = true;
enable_outgoing_utp = true;
enable_incoming_tcp = true;
enable_outgoing_tcp = true;
rate_limit_utp = true;
mixed_mode_algorithm = session_settings::prefer_tcp;
max_allowed_in_request_queue = 5000;
max_out_request_queue = 5000;
allow_multiple_connections_per_ip = true;
file_pool_size = 500;
connection_speed = 20;
half_open_limit = 5;
connections_limit = 100000;
listen_queue_size = 1000;
unchoke_slots_limit = 1000;
close_redundant_connections = true;
max_rejects = 10;
optimize_hashing_for_speed = true;
request_timeout = 10;
peer_timeout = 20;
inactivity_timeout = 20;
send_buffer_low_watermark = 1 * 1024 * 1024;
send_buffer_watermark = 3 * 1024 * 1024;
send_buffer_watermark_factor = 120;
utp_dynamic_sock_buf = true;
choking_algorithm = session_settings::fixed_slots_choker;

Original issue reported on code.google.com by voi...@hotmail.com on 20 Apr 2014 at 2:53

[GoogleCodeExporter]

could you enable session stats and provide those logs for me to analyze? 
enabling it is done by saying statistics=on in the bjam command line, or 
defining TORRENT_STATS when building.

feel free to email me the logs directly at arvid@rasterbar.com

the logs should start with the good speed and include the time when it has 
slowed down.

Original comment by arvid.no...@gmail.com on 20 Apr 2014 at 5:37

[GoogleCodeExporter]

Ok, these days, I will save some logs then send to your email.

Original comment by voi...@hotmail.com on 21 Apr 2014 at 1:41

[GoogleCodeExporter]

By the way, which logs file will help you, libtorrent_logs+port or 
session_status,
because these logs files in the libtorrent_logs+port are too large and to many.

Original comment by voi...@hotmail.com on 21 Apr 2014 at 2:08

[GoogleCodeExporter]

the ones in session_stats

Original comment by arvid.no...@gmail.com on 21 Apr 2014 at 5:30

[GoogleCodeExporter]

well, somedays later I will send logs file to your email again.

Original comment by voi...@hotmail.com on 22 Apr 2014 at 9:18

[GoogleCodeExporter]

The same reason as issue 606.

Original comment by voi...@hotmail.com on 28 Apr 2014 at 1:49