152 gnutella neighbours....

[PornMaster]

hey, i left shareaza on all night and when i woke up, it was connected to 152 gnutella neighbours!!. my computer probably would of crashed but since windows xp is alot stable, i guess it held it out but my computer is was slow and i see why... is this a known bug? or all my setting messed up?... has anyone else had this problem?

[CrAzYMaNiAk54]

My friend left his computer on for a couple days while running shareaza and when I came over his house he was connected to 168 gnutella neighbors!!!!! i was like WTF! Than i just exited shareaza and got back on it and everything was fine.. I dont know if its a bug?

[Anenga2]

This is probably because Shareaza promoted you to a Hub. If your computer is in idle, you have a good connection, aren't excessivly sharing a large amount of files and have a stable system then Shareaza will promote you to a Hub.

Shareaza promotes you to a Hub if you've been online for a while, and pass certain conditionals. As do every client I believe.

While being a Hub, you can have up to around 400 Leafs (though, you can go as high as 800 or so and still be okay).

If your computer is unable to handle it, then I'd get out of Hub mode and uncheck it in the settings. Running as a hub takes a lot of computer processing, and a great deal of bandwidth (though, it's significantly less than running as an Ultrapeer in G1).

So, it isn't a bug. It's normal healthy function. Serving as a Hub is a privlage, and helps the network tremendously.

[Chamma]

Originally posted by PornMaster
hey, i left shareaza on all night and when i woke up, it was connected to 152 gnutella neighbours!!. my computer probably would of crashed but since windows xp is alot stable, i guess it held it out but my computer is was slow and i see why... is this a known bug? or all my setting messed up?... has anyone else had this problem?

it's enugh with 5 neigbourse. 10 is TOOOOO muchy and you where connected to 152...., strange..

[Sephiroth]

Looks like shareaza's promotion logic or the connection logic is flawed, its a bug there is no way that a home broadband user could handle that many connections.

Because to have that many host connections is wasteful and only creates bottlenecks. Unless the people are running backbone servers which i doubt they are.

[Anenga2]

Originally posted by Sephiroth
Looks like shareaza's promotion logic or the connection logic is flawed, its a bug there is no way that a home broadband user could handle that many connections.

Because to have that many host connections is wasteful and only creates bottlenecks. Unless the people are running backbone servers which i doubt they are.
What?

[Sephiroth]

Originally posted by Anenga2
What?

You see problems or things that shouldnt happen in software are called "bugs." Which got its name in the early days of computing when a moth got into the componets of one of the early computers.

Having 152 host connections as well as leaves or whatever term you invented it sounds like a bug because even with host compression it is will too much for any broadband user to handle assumeing that they are not running it as a server which in the cases here they arent..

SInce host/leaves are more RAM dependant/intensive with "g2" having that much is likely to eat up all avaible RAM which would explain why their computers slowed to a crawl which was instantly fixed by shutting shareaza down.

Which isnt ideal because Shareaza shouldnt assume that people are going to run just it in a server, that it will not be ran as a "server" on a continual basis, and should not use up all CPU, RAM and etc. Else its just going to have even worse problems than Gnutella as it is now and not really be an improvement because it sounds like to me based on this problem that shareaza saved some bandwidth with its new features but increased the load too by too much that it pushes the "hubs" too much that they cant handle it which is why threads like this get started.

[CrAzYMaNiAk54]

Nice explaination seph...I too think that it's a bug

[alanshemper]

Grace Murray Hopper, working in a temporary World War I building at Harvard University on the Mark II computer, found the first computer bug beaten to death in the jaws of a relay. She glued it into the logbook of the computer and thereafter when the machine stops (frequently) they tell Howard Aiken that they are "debugging" the computer. The very first bug still exists in the National Museum of American History of the Smithsonian Institution. Edison had used the word bug and the concept of debugging previously but this was probably the first verification that the concept applied to computers.

[pinku]

but higher leaf density leads to greater search results....

Coz for same no. of ultrapeers/hubs u search far more users....the only problem is that users running as hubs take a lot of heat but if one has lot of ram, with a fast processror and good bandwidth i dont see why it is a bug....

[Anenga2]

Originally posted by Sephiroth
You see problems or things that shouldnt happen in software are called "bugs." Which got its name in the early days of computing when a moth got into the componets of one of the early computers.

Having 152 host connections as well as leaves or whatever term you invented it sounds like a bug because even with host compression it is will too much for any broadband user to handle assumeing that they are not running it as a server which in the cases here they arent..

SInce host/leaves are more RAM dependant/intensive with "g2" having that much is likely to eat up all avaible RAM which would explain why their computers slowed to a crawl which was instantly fixed by shutting shareaza down.

Which isnt ideal because Shareaza shouldnt assume that people are going to run just it in a server, that it will not be ran as a "server" on a continual basis, and should not use up all CPU, RAM and etc. Else its just going to have even worse problems than Gnutella as it is now and not really be an improvement because it sounds like to me based on this problem that shareaza saved some bandwidth with its new features but increased the load too by too much that it pushes the "hubs" too much that they cant handle it which is why threads like this get started.

The problem with Gnutella1 is that it eats up too much bandwidth. If you actually look at your search monitor, you'll notice your computer is being queried for files that you don't have, this is because of Gnutella1's poor searching. Shareaza adds more processing to limit dead/bogus queries. This does require more RAM, but a standard computer user can handle this who is on a cable modem.

I don't quite understand what your saying. Your saying that a Hub can't handle 152 connections? What about all the Ultrapeers on Gnutella1? They have over 200 connections? And I highly doubt every Ultrapeer is a T1 user or anything. The 152 connections I'm talking about are "leaves". Did you think I meant "Peers" (fellow Hubs)?

Rest assured that G2 Hubs can handle the RAM and Bandwidth loads accordingly. I run as a Hub on my computer at times, and I can handle it just fine. Shareaza has built-in conditionals that make sure the node can handle the RAM and Bandwidth requirements to be a Hub before they are actually elected.

[Anenga2]

Originally posted by pinku
but higher leaf density leads to greater search results....

Coz for same no. of ultrapeers/hubs u search far more users....the only problem is that users running as hubs take a lot of heat but if one has lot of ram, with a fast processror and good bandwidth i dont see why it is a bug....
You are correct that a higher leaf density leads to greater results.

G2 Hubs *can* handle the RAM and Bandwidth requirements, as you suggest. It is not a bug, it's normal function.