Using LimeWire 2.4.4, Java 1.4, Windows 2000, ADSL connection...

My ADSL isn't as asynchronous as I'd like it to be - maxed out uploads reduce my download bandwidth. Consequently I like to limit the upload bandwidth.

Unfortunately, this causes uploads to drop to 0KB/s and stay there - I end up not sharing anything unless I manually remove the stalled uploads (needs to be done every 6-12 hours).

If I don't limit downloads (Slider all the way to the right) then uploads continue without problem and do not stall.

Mark

Did you select Cable\ADSL in the setting? What's your up\down bandwidth?

Yes - I selected cable/DSL in the setup.

Theoretically (and largely in practice) my bandwidth is 576/288kbps up/down.

I set the upload bandwidth limit to be around 30KB/s. This is around the maximum speed for upload. This tends to limit my download speed until a few uploads have dropped to 0KB/s (which takes between half an hour and two hours).

Mark

Well, I have no idea, mine is 512\64 and the minimum upload bandwidth LimeWire allows me to set is 10 KB/S (which is my max upload bandwidth). However, I experience no problems uploading when I set the upload bandwidth to the minimum anyway.

How many simultaneous uploads do you usually have?

Usually between 10 and 20 - Currently 12 with 5 stalled at 0KB/s (The number of simultaneous uploads drops off as more are stalled).

Most of the files I share are large (smallest upload at the moment is 70MB).

I always have a fairly high demand for upload slots (just short of 350,000 upload requests (upload count under stats) in the last 24 hours).

Mark

Go to the options, set the Upload Slot Minimum to 1 (never increase it, it can cause lot's of problems) and set the Upload Slot Slot Maximum to 4 or 5, or even lower (I set it to 2).

Uploads will usually drop to 0k more seldom if you do so. One reason for 0k uploaders are hosts, that are disconnected without closing the socket due to a connection error, ISP connection reset, LimeWire is closed (- hey, that's a but indeed, LimeWire should close all sockets before exiting!!).

I have observed the asymmetry you described.

More formally, let 's' equal the send capacity, and 'r' equal the receive capacity.

A true asymmetric connection's relationship between send capacity and receive capacity can be defined using the following function:

r = f(s)

f(x)=C

where C is a constant.

Some providers, in an attempt to lower bandwidth costs, frustrate p2p applications by changing f(x). In the simplest form, f(x) can be redefined as:

f(x)=C1 for x<=X0
f(x)=C2 for x>X0

where X0 is the send cap and C2 is much less than C1.

This allows normal users who are surfing or downloading to get the maximum throughput, but penalizes those who use a lot of upload bandwidth (as those are running p2p apps or servers).

Usually, f(x) is a smooth function which is close to C1 for most of the range of x, and drops off sharply at the upper limits of x (the send limit).

One footnote to the previous post.

For symmetric connections (modems, T1 lines, etc..) the following equation holds:

r + s = C

where C is the total speed of the connection.