View Single Post
  #10 (permalink)  
Old December 10th, 2001
Posts: n/a

I'm going to break down what Adam is saying for the people who really dont know what he is talking about. (I'm trying to be helpful not sarcastic.)

Originally posted by afisk
When you connect to an UltraPeer, you do automatically drop the rest of your connections. This is the desired behavior, as the peer is acting as your proxy and is shielding you from all of the traffic on the network, except for queries for files that you have, which are forwarded to you.
This means you are connected to ONE peer that handles queries that would overwise pass through and consume network bandwidth. That peer caches what you are sharing so when someone searches for something (sends a query our on the network) that would go to that ONE peer and stop and if there is a match of something you are sharing it sends the information back so that host can see that you're sharing that file. Then of course after that he can connect to you and download the file.


Also, I should mention that being a client peer or an UltraPeer does not necessarily reflect the power of your machine or your bandwidth -- most users who have plenty powerul enough machines and plenty of bandwidth will remain client peers most of the time.


I admit that the switch to becoming a client peer seems a little bit wierd at first, as your connectivity (and hence network reach) appears to have dropped. Once there are more UltraPeers on the network, however, it should not matter at all. This is because each forwarding of a query to another layer out on the network will become much more significant, as each "hop" will effectively query a larger number of hosts/files than before. This is because a hop to an UltraPeer could mean searching through 50 hosts connected directly to that UltraPeer, which means your searching far more files that a hop to an old peer who might only have 4 hosts connected to it, and therefore far less files.
This means now with Ultrapeers the network will look like this.

XXXX (Host X = Ultrapeer)
/ | \
A B C (Hosts A, B, and C = Clientpeers)

meaning one Ultrapeer could have 50 hosts connected to it instead of the old design

\ /
/ \

where the max number of hosts connected are 4 and they produce X amount of traffic for a specifc query. As where when connected to an Ultrapeer it produces the same X amount of traffic with 100 times more clients connected to it for a specific query.

So in other simplier terms when connecting to an Ultrapeer its like that ONE peer is sharing all files of those 50 hosts instead of 50 individual hosts sharing their own files. Because you query Host Z for X and Host Z replies telling you he has X available for download. So you query Ultrapeer and it replies telling you Host Z has X available for download. Essentially cutting down extremely on Gnutella network traffic. Hope that paints a picture.


I hope that makes some sense. So, there is a timing issue here. As more LimeWire 1.9 and aboves get out there, you should see better search results even as the total messages past are far fewer than before.
Gnutella is really going to kick *** when LimeWire 1.9 is released full stream and Bearshare does the same (I think Vinnie was or is going to implement Supernodes or at least the new "Query Routing Protocol")

One last question....Adam what is the LimeWire's comments on the Network History Size graph on About its up and downs?

oh yeah and I love networking (just felt like saying that :P).