Shareaza

I've to say I love Shareaza, but I'm very unhappy how it utilizes the available bandwidth.

So I've the 25/25 FIOS, about 7000 files share, and lots of people want to download. I increases all the queues to many slots, but still most of the time downloaders are stuck in queue mode or next mode. Then once every 20+ seconds the client gets some data uploaded for a few seconds, just to wait another 20sec. So basically 90% of the time I'm uploading nothing. What a waste.

Now, when I put shareaza in hub mode it gets even worse. While I've no problems handling the 300 leafs, my upload gets neutered to 5-10kb/s. Make the queue fill up fast.

So what can I do that I can constantly upload to 20 people at 100kb/s? My emule has no problem handling 50 clients and using 20mbit... but I'd prefer Shareaza to server G2 and Emule.

Why not to use eMule and Shareaza(with turned off ed2k) ?

Set Shareaza properly.
1) Download from G2 (and share then) "Shareaza Install Guide" by oldDeath - lots of tips, tricks and how to do it.
2) make connection test, if not passed set firewall and router. See Shareaza wiki about them. Make portforward according to indications described for your router on portforward.com. Also set static IP, described at portforward.com also. Without pass connection test rest will not work. So first make it.
3) In Shareaza>menu'>settings>Internet:sending check if "limit" is corresponding to bandwidth you want to use and set "mode" from default "average" to "maximal"
4) In the same place after you will connect to networks you will see how "ques" are set, you can set more bandwidth to the net you want to promote. Together, in total, they cover bandwidth set for uploads. I set G2 and eD2k both 50% and turn off G1. But this is your choice.
5) In Shareaza>menu'>settings>Internet: connection - options: set "I can accept incoming connections" from default "auto" to "yes"
6) this is not necessary but I would change there port from default 6346 to higher, what any, as sometimes ISP could discriminate connection from port of this number. Perhaps 23145? What any. But remember this MUST be taken under consideration when you forward port - you must pass connection test, or we are back in point 2) above.
7) Read wiki and understand how Shareaza work so it will become powerful tool in your hands. Don't be afraid to make some experiments with settings, this way you will find most appropriate for your purposes and your hardware. Then pleaselet us know effects and what those settings are.

ok, I'm not sure if its any different...

in hub mode I still get 5kb/s


in leaf mode I still get 50+% of the clients in "next", then bursting some data, waiting in "next" again...

This is about ques, you can set more bandwidth to large files in this example. Changes are visible in a few seconds so you can make some experiments to see what is most appropriate for your purposes. This picture shows that about 5KB is set to serve large files in G2. Click this que in settings and set more. Note that total of all ques will be equal to bandwidth OF UPLOADS that you have set in settings. And if you want to use your browser together or other programs it should take 70-90% of aviable connection upload. See settings again, I thin you haven't set them as wanted they to be set. You must understand relations between them: 100% connection upload > 70-90% Shareaza uploads (in setting) = total of ques (% for G2 + % for eDonkey + % for G1). And G2 = % large files + % small files + % partials, and eD2k = % EDonkey core files + % eDonkey partials files I your example on picture % large files is set about 5KB and this friction of bandwidth is divided on every user downloading from you that large file.
This you can set in Shareaz>menu>tools>settings>Internet>ques. This is simple when you understand above, how it works together. Don't be afraid make some experiments.

Hub mode uses some bandwidth... Also, there is an option to limit sharing in Hub mode, which also limits the used bandwidth. To use the total amount of bandwidth in Hub mode, you will need to turn that option off...

BTW, are you talking about kb/s (bit) or KB/s? (Byte) There's a difference of a factor x8 between them...

There is also one additional factor: speed accepted by remote client... When client got download set on certain value then you can't offer him anything more then he accepts...

Could you tell what is your connection max upload and max download provided by ISP? What download and upload have you set in Shareaza settings:Innternet:connection? What upload is set in settings:Internet:upload:> limit & mode? What are your ques, there also, and what % and what KB each one is? Settings are settings this is simplest mathematics. And hub mode do not promote uploading or downloading - am I right? So still you are to find where in your settings is "narrow throttle"? Or perhaps this is any other software interfering with Shareaza or limit set in router?

My standart experience with Shareaza's ed2k support:

1.
I share only 2 files
Run eMule, wait 1-10 minutes and eMule uploading at 1Mb/sec, upload que is full

2.
I share only 2 files (same as in eMule)
Run shareaza, wait 1-10 hours and shareaza may start uploading to ed2k at 1Kb/sec to one user in que.

Well your case is simple to solve, upload to more clients thus bringing down the overall bandwidth for each and allowing them to download from you for a longer period of time. Rule of thumb is to be able to download to each person on a full queue at the speed of 6-10KB/s. This way you have more downloading from you and allowing your queue to build up as well so that a new connection is ready the moment one finishes. Also increase the rotation time for each queue, default is a bit too short for your speeds, so increase the timing by a factor of 1.5, doubling is too much I think so 1.5 is ok. Maximum queue for the http downloads also needs to be altered so as to allow the queue to fill up but also not have a big impact on your bandwidth (http queues are active and drain resources). Lastly make sure the max upload queue is properly set by you, make sure it is 2000KB/s not k[b] it makes a big difference, I tend to use the Maximum mode, as the averaging within Shareaza is not good enough and speeds tend to fluctuate greatly.

You have to understand the default queue was designed for people with limited uploads and even for those people it isn't that optimized.

I created this queue which should be suited to your needs ... I hope it work in saturating your line, but always keep the above guidelines in mind when tweaking the uploads queue.

Yea, that's right. More Leaf-to-Hub connections means YOUR files will be found quicker. It can somewhat make your queues full quicker, but as said above, it's just waste of resources. In G2 you can find a single file located anywhere on the network, even if all clients in the network have one Leaf-To-Hub connection.

He want "to make Shareaza a powerful UPLOAD client" right? In this context to allow quicker finding of file is better right? And I think it would make network more comfortable when files could be found quicker right? "Waste" of resources on old machine with win2k is less then 1% of CPU and a 1 or few KB RAM - I think this can be sacrificed to make network faster, especially on nowadays machines, and this is reasonable when searching is subject of many complaints. So in theory this is unnecessary, and for uploading it can give positive effect. And when it is not disturbing why not to do this?

All I want is to share my collection with the world... the demand seems to be there (see emule quickly fills my bandwidth), now the G2 world does not seem to have the right client for just pumping out files. I see plenty of interest, its just not served.

Resource wise I dont mind Shareaza, so far its being nice to my CPU/RAM, but again emule handles about 100x what Shareaza does. I guess I'll just keep it open since its not really harming, and the clients waiting getting their data, just takes hours instead of minutes.You cant have everything...

Current ques settings are:

1 eDonkey partial - rotation 600s, rewarded senders
2 eDonkey core - rotation 600s, rewarded senders
3 G2 partial - rotation 300s, reward senders
4 G2 small - rotation 300s, DO NOT reward senders, why?
5 G2 big - rotation 3600s, DO NOT reward senders, why?

Does this mean that eDonkey if get connection then it will last 2 times longer then G2 on small and partial?
Why not make default G2 small "reward senders" and G2 big "1200s" and "reward senders" like ed2k is? Can due to 1200s happen that there will be more sources, however in partials, but in the end total download would be faster, from more sources, to one user?

And also change order from above to following:
1 G2 partial
2 eDk partial
3 G2 small
4 G2 big
4 edk core?

Do we have any predictions about such changes?? Can they work better?? And what are experiences of those who have made any experiments with changes in practise?

alleskacke

Did you try my upload queue? I think that should fulfill your requirement of maximizing your upload bandwidth. Shareaza is able to serve out files just as well as emule. The difference is that emule as a network is configured for such transfers as a default ... even the upload rules are bandwidth based, and it scales better than Shareaza. Our upload queue system only scales as high as 100KB/s transfer on default. We need more rules for higher upload speeds. With Shareaza you have to configure your upload queue, and play with some network settings. eD2k as a network transfers on average bigger files resulting in bigger chunks/ parts also the population of the network was significantly greater than Shareaza last I remember (like 2-3 years ago).

Again try out the queue I uploaded for your case and see if it maximizes your upload.

No instructions needed, just dropped it into the Shareaza\Data folder and all is a go. This is customized for the OP, so I don't think it is useful for the everyday user who doesn't have upload speeds in excess of 10MBit's.

Question:
It is very often Shareaza uploads to another Shareaza as eD2k instead of G2. Practically, if order of queues would be changed to following as below, then would it made that uploader would offer to remote client G2 upload first? eD2k clients would just ignore G2 packets, so no problem. But for G2 users benefit would be obvious.

So proposed order of queues:
1 G2 partial
2 G2 small
3 G2 big
4 eDonkey partial
5 eDonkey core

How do you think?