Simple question about ultrapeers
 

Could you tell me how many (or the range of) ultrapeer connections should have a ultrapeer. And the same for a leaf node. I didn't see a clear recomendation about that issue in the docs.

thanks in advance.

I am sorry. I do not understand your question.

Well, then i explain it in more detail. I am talking about gnutella conections between nodes. For example a ultrapeer would be connected to other five ultrapeer, and have 50 connected leaf nodes. So, my question is: what is the recommended number of connections to ultrapeers? (in my example 5).

I leaf node also have connetions to various ultrapeers. I wish to know the number of connections recomended in this case also.

If I were you I would message a Gnutella official and ask them to look at this thread :)

What do you mean with "gnutella official"?

Ask one of the guys that already have a client released or an Administrator.

t2p2p:
Look here you might find some handy infos:
http://groups.yahoo.com/group/the_gd...als/Ultrapeer/

nice site :)

The question remains
 

Yes, i readed that documentation but it only say that a ultrapeer should have <10 connetions to others ultrapeers (it don't say if is recommened you should have 3, 5 of 9 connections, and it will be quite different between having 9 instead of 3 ultrapeer conections). Also say that a ultrapeer should have 10-100 leaves connected, but it don't say anything about how many ultrapeers should have a leaf.

So, could someone say me if exist a recommendation for that. Or what is the regular numbers of connections (by default) used by most of the implementations.

Thanks.

I think the general rule now is 3 ultrapeers. Ultrapeers should also allow 'regular' nodes to connect instead of just ultrapeers and leafs.

in ultrapeer mode set 3 ultrapeers and 100 childs/leafs. In Child/leaf mode have 7 ultrapeers.That's the perfect way to go!

Thanks, that is exactly what I wished to know. I have hear something about 3 ultrapeers, but I didn't see it clearly since doc only say <10 (which could be a lot). And I didn't see nothing about leaf connections. So, I think that this is a closed issue. Thanks again.

Not quite closed
 

It is absolutely essential that leaves be limited to acquiring no more than 3 Ultrapeers.

BearShare 4.0.0 unfortunately ships with the maximum set to 10. Although I didn't realize it at the time, this puts an unbelievable burden on the network and creates a massive shortage of leaf slots.

Thank god Morpheus Ultrapeers are under-utilized, and our Hosts View is hidden from sight by default.

We will be correcting this defect ASAP.

On a related note, it really is beneficial to the network to allow as many leaves as possible per Ultrapeers. This allows queries to do more work at each step, and shields leaves from the bulk of traffic.

It is also very important to make sure that Wi*** and Win98 systems NEVER become Ultrapeers.

Additionally, Ultrapeers should meet certain minimum bandwidth, CPU, and memory requirements as well.

Re: Not quite closed
 

Those 3 Ultrapeers would have to be better than 99% of the ones I've connected to. In the last two weeks I've seen ONE, I repeat, ONE Ultrapeer that claimed to have more than a couple hundred hosts connected. Disregarding the potentially erroneous host count, I've still seen about 50% of the Ultrapeers to which I connect have almost no traffic at all. Either they're doing a very, very good job of shielding me from network traffic, or they're very poorly connected.

If all those broken Morpheus Ultrapeers could be removed overnight, I'd have no problem with a limit of 3, but until those bad Ultrapeers are gone, a limit of 3 would be death to the network, at least as a viable entity for finding files.

Re: Re: Not quite closed
 

I have to agree. When Morpheus introduced ultrapeer support (updated to a newer version of Gnucleus :rolleyes: ), the # of query hits received, on average - per search, dropped dramatically for ultrapeer enabled clients. It has been my experience that 5 regular peer connections produce the same amount of query hits as 7 to 10 connections to ultrapeers (as a leaf node). With most clients having such a low # of ultrapeer connections by default, I suspect that most users are having the same experience.

Remember, gnutella Ultrapeers aren't nearly as effective as those in the KaZaa/FastTrack network. 3 Ultrapeers is completely unreasonable if you expect a user to find anything other than "Britney's latest hit"...