severe transfer obstructions

Sorry, some of my original text was lost. Therefor, once more:

I had posted this problem (it's really severe!) already at 07-09-2002 under the title "slowing down uploads until deadlock" but nobody seemed to recognize the severity.

Some clients slow down their transfer speed to zero and stay there, blocking other users.

I know, this behaviour is probably not a problem of the Limewire client, but the client could solve this severe problem.

The effect of this behaviour is that after a view hours, if I let run the Limewire client in the background, 16 of my 20 open channels are blocked by 8 users who have this problem. The remaining 4 transfers are constricted by 16 ineffective channels which do not really upload but stay still in the upload status. The effect is that, after a view hours, only 20 % of my valuable transfer volume can be used, 80 % are blocked by sick clients.

Unfortunately I could not find out which client is used by the hindering users because it never happened that one of them has enabled his chat function (maybe it is a client without chat function).

As a workaround I propose that the client does the same what I did by hand when I saw that this problem occurred: Watch the upload speed, and if it gets exactly zero and stays zero a given time (a few minutes), then kill this upload!

I hope you can recognize that this is a severe problem of the gnutella network activated by any unknown client type, maybe two or three months ago.

Regards
Hermann

it's actually a small bug in limewire -- should be fixed in the newest version.

[JohnReam]

Calling this issue "severe" is an overstatement. It is indeed just a minor bug.

If it's bothering you so much, then your solution is good:
You Watch the upload speed, and if it gets exactly zero and stays zero a given time (a few minutes), then kill this upload!

I've been doing this for weeks... which is no big deal since I occasionally monitor uploads to see what folks are interested in.

>which is no big deal since I occasionally monitor uploads to see what folks are interested in.

You'll be glad to know that the next version of LimeWire will do this for you.

The Library will have the new columns "Uploads", "Hits" and "Locations".

Uploads will display the amount of completed & attempted uploads, Hits will be the amount of searches your servent has recieved that matched the file, and Locations are the number of other places on the network [that your servent knows of] that have the exact same file.

Originally posted by JohnReam
Calling this issue "severe" is an overstatement. It is indeed just a minor bug.

Hi John,

My opinion is that this is neither "minor" nor a "bug" (of Limewire -- it's a bug on any other client).

If you know the circumstances you will see that this is a "severe" problem for me: I live in Europe and therefore the most important part of my Limewire session happens (at America's internet rush hour) when I am sleeping. And, unfortunately, I download nearly nothing but I share a lot of files.

The behaviour described is the reason why Limewire cannot do what is typically for this kind of application: running in the background.

I posted this bug when runnig the 2.5.5 Beta German. With that version the problem existed yet. A few hours ago I installed the 2.5.5 German. Up to now I have not yet any experience with this version.

Maybe this problem is already solved ???

Regards: Hermann

[efield]

I agree with you Hermann that this is a major bug. The Gnutella network only works if uploading files occurs seamlessly and without intervention. A reduction in available upload slots creates additional traffic from the requeries, etc. and slows down the network.

I'm dredging up old stuff here but when Napster was still working my Mac client had a similar bug. Setting upload slots to unlimited didn't work so I put it at the maximum 10. As time went by some file requests would sit in my queue and not make any progress. Overnight all of my upload slots would eventually fill and no one could download from me. Occasionally people would IM me to call me out but I was clearing the stalled transfers when I saw them. Just couldn't do that while sleeping.

Great to hear this problem will be fixed in the next LimeWire version.