Quote:
Originally posted by Guest488
The Status column always says "Outgoing" and the Protocol column always says "Ultrapeer" whether the servent is in Leaf mode or in Ultrapeer mode. |
In recent versions, the limewire network has a higher percentage of ultrapeers, hence the many ultrapeers. when running as a leaf, you connect to ultrapeers exclusively, when running as leaf, I usually have around 30-50% 'normal' hosts, the rest are ultrapeers.
Quote:
| What is the "Dropped I/O" column and why is it only the LimeWire servents that seem to have such high percentages? |
I know this is irritating. Limewire has a misleading interface. The point is that the messages are
supposed to be dropped. In recent versions, limewire ultrapeers filter out search requests for stuff that their leaves don't have, so, if somebody searches for, say, popular artist X, and you don't share any such file, the ultrapeer doesn't forward that search request to you, and limewire reports it as 'dropped'. this keeps more bandwidth free for more useful stuff.
Quote:
| I am running LimeWire 2.9.11 on Mandrake 9.1 with a cable modem connection. When I first connect, I connect as a Leaf node. LimeWire maintains a minimum of three connections -- very seldom more. And so I starve for fruitful search results and downloads. |
Again, one of these things where limewire does a real bad job at making the user feel things are running smoothly. things actually
are running smoothly. as a leaf, you should not have more than 3 connections and having more would not drastically improve your search results but waste bandwidth.
Quote:
| After a while the servent automatically switches to Ultrapeer mode, and then I am flooded with connections. So many that my poor, little 200MHz processor just can't handle it, and everything slows to a crawl. I have to use short-cut keys to activate the File menu and Disconnect. I should add that these connections are more aptly described as connection attempts; very few of them "stick" and thus new connections are constantly being attempted. |
As an ultrapeer, limewire should mainly function as a router of messages, hence the many connections. However, you machine just seems to be too slow for that task. I suggest disabling the ultrapeer feature in options/speed, your machine is no good to the network if it can't keep its connections.
Quote:
|
It seems that most of my uploads have occurred during Ultrapeer mode, and I would rather not disable Ultrapeer capabilities as there may be some who could use at least some of my bandwidth.
|
I had the opposite experience. More uploads as a leaf as more bandwidth is awailable. If you keep sharing the same files and have a static IP, you should very soon be passed around as an alt-loc for the files you're serving and from then on, you will have uploads without even getting hits.
Quote:
How can I change the minimum number of connections for Leaf mode and the maximum number of connections for Ultrapeer mode? Is this buried in the code somewhere? |
IMHO, Considering you use a 200 mhz machine, I suggest running as a leaf. There's plenty of ultrapeers out there lately, and you won't really lose any functionality, if anything, you will contribute more to the network.
Hope that helps somewhat
May 27th, 2003
Re: Leaf vs. Ultrapeer & connection flooding 
Similar Threads 
Threaded Mode
