Re: [Mldonkey-users] [Patch] Toggle browsing of share list

[Roland Arendes]

hi João Correia,

JC>         Imagine you're downloading a two part vacation movie. Isn't it
JC> fair to think that anyone that has one part of it probably has the
JC> other? Its only logical the program should ask working sources
JC> previously found for one file to try and see if those same sources also
JC> have other files you need.

I understand your point, but the implementation is more a quick hack
than a logical step. But make this togglable.

I can't use this version, it blasts my upstream away again. Even if I
set the max_hard_upload_rate back to 1, I can't stand the requests
mldonkey creates.

The ratio of requests/upload is going mad like the cvs 2.00. I have a
bad feeling about this. Every mldonkey I had *never* worked with any
max_hard_upload_rates. Even with new_upload_system to false.

And, to continue my research, I'm not able to upload files with more
than 5k/s at all. Even if I pause all downloads, so that no more
requests are created, I can't get more than 4-5k/s effective upload
out.

I *WANT* to upload, I *WANT* to give something back to other clients.

But this is rather bad till impossible with mldonkey. At least for me.

Look at your stats, and devide Total uploads with Uptime in seconds.
The upload rate is embarassing since the first version I had. Perhaps
I've set up something wrong, but max_hard_upload_rate never worked for
me.

ifmonitor told me I've been using my upstream with 13k/s the whole
night. I devided the bytes uploaded with the uptime (started right
before going to bed) and got about 4k/s. So 9k/s requests, 4k/s uploads.
Imagine every user out there would use mldonkey. We would all drown
in requests, and the download rate would perhaps stay at 4k/s, if
you're lucky.

So this patch makes everything worse. I have to lower my upload rate
again to get a rather free line (with HTB!). Without QoS everything
would lag like hell. Even with 2.01-1.

Well, the download rates are excellent, but .. at what price? We had
this again with 1.16 and got banned.

I have 3 mldonkeys at different routers and links which I look after,
and everywhere the same picture.

This can't be me, can it?

So, please mldonkey/simon/pango/whoever, fix the max_hard_upload_rate
and keep the request/upload ratio at a good value. I don't want to
slow down mldonkey using HTB (QoS algorithm), but I have to. :-(

-roland

PS: constructive critism disered