[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Mldonkey-users] 2.02-6 collects too many sources
From: |
Roland Arendes |
Subject: |
[Mldonkey-users] 2.02-6 collects too many sources |
Date: |
Thu, 23 Jan 2003 22:01:17 +0100 |
hi mldonkey,
Is it possible to limit the global number of sources in the next
release (-7) to a specific value?
2.02-6 collects TOO many sources and is exclusively doing this.
I get no downloads, and my whole upstream of 16k/s (even if upload is
disabled with nu) consists all the time of the source management.
Even after 2,5 hours of uptime I have only 88 kB downloaded and
921 kB uploaded. Not even all chunks are checked (updated from an
older version, and the new chunk states still have to be verified).
10 of my 72 downloads are very popular files and have more than
30000 sources each (with none connected).
During writing of this mail I got an better idea: If one file has about
3-5 times more sources than the average of all files, stop querying
for it. The max_sources_per_file parameter can be removed, as it
seems to be ignored for 2.02-5 and newer. It isn't a good way to
limit sources anyway.
What do you think?
These are my current stats (removed senseless server columns):
Uptime: 9074 seconds (0+02:31)
Total seens: 9160
eDonkey: 53 (0.58 %)
old mldonkey: 72 (0.79 %)
new mldonkey: 248 (2.71 %)
Overnet: 0 (0.00 %)
old eMule: 0 (0.00 %)
new eMule: 8787 (95.93 %)
trusted mldonkey: 0 (0.00 %)
Total filerequests received: 30462
eDonkey: 169 (0.55 %)
old mldonkey: 5651 (18.55 %)
new mldonkey: 6748 (22.15 %)
Overnet: 0 (0.00 %)
old eMule: 0 (0.00 %)
new eMule: 17306 (56.81 %)
trusted mldonkey: 588 (1.93 %)
Total downloads: 90286
eDonkey: 61614 (68.24 %)
old mldonkey: 0 (0.00 %)
new mldonkey: 0 (0.00 %)
Overnet: 0 (0.00 %)
old eMule: 0 (0.00 %)
new eMule: 0 (0.00 %)
trusted mldonkey: 28672 (31.76 %)
Total uploads: 943104
eDonkey: 0 (0.00 %)
old mldonkey: 0 (0.00 %)
new mldonkey: 190464 (20.20 %)
Overnet: 0 (0.00 %)
old eMule: 0 (0.00 %)
new eMule: 436224 (46.25 %)
trusted mldonkey: 316416 (33.55 %)
Total banneds: 1221
eDonkey: 0 (0.00 %)
old mldonkey: 3 (0.25 %)
new mldonkey: 0 (0.00 %)
Overnet: 0 (0.00 %)
old eMule: 0 (0.00 %)
new eMule: 1218 (99.75 %)
trusted mldonkey: 0 (0.00 %)
Sources:
Queue[Good Clients]: 2979 sources
Queue[Ready Sources]: 240177 sources
Queue[Waiting Sources 0]: 750 sources
Queue[Waiting Sources 1]: 0 sources
Queue[Waiting Sources 2]: 0 sources
Positive/Negative: 244527/0
NotFound/Found/Chunk/Upload: 38/741/6011/0
Outside of queues: 621 sources
Total number of sources:244527
max_sources_per_file = 350
strict_bandwidth = false
max_opened_connections = 800
client_buffer_size = 100000
check_client_connections_delay = 180.
max_clients_per_second = 20
good_sources_threshold = 65
new_upload_system = true
sources_per_chunk = 5
ban_period = 1
max_hard_upload_rate = 1
max_hard_download_rate = 100
The upload rate was reducing for testing. I can't stand the limit of
upstream mldonkey 2.02-6 creates without even uploading a single byte.
Even with upload_rate = 1 I can't see any difference.
Any ideas? MLdonkey? Pango?
-roland