eD2k/G2 upload bandwith ratio - proposed 50/50

[ocexyz]

In Shareaza installer default settings is that eD2k uploads got wider bandwidth then G2 sources sagnificantly. Could this be set about 50ed2k/50G2%?

[ailurophobe]

Why? I can see why someone might want to edit it later, but what is wrong with the default? I always set ED2K upload bigger because ED2k has credit system, so setting upload higher in theory improves performance. Also with low bandwidths it is possible get hit by upload/download ratio problems which G2 also doesn't have.

[old_death]

[ocexyz]

I just would like to use G2 benefits that is why. eD2k sources are waitng waitng and waitng. I vave realised that there are G2 sources but with so f...n small bandwith for upload, but this is effect of artificial limiting it in ques. In fact we are feeding eD2k and hesitating G2 support. e2Dk sources are always a few KB but they are many. G2 sources could be much quicker if would not be artificially limited. I have set 80% for G2 and 20% for eD2k and there were the same stream from eD2k in longer period of time. I suggest only to set it 50/50 bby default, at last try in debug builds, and we would see practical effects.
In practise we limit G2 uploads, so support G2 - this is not wise in longer time.
Either this could run indipendently and use just free bandwidth dynamicly.

[ailurophobe]

[ocexyz]

Perhaps this good idea, however requires coding-manpower what is very rare good here. I wanted to suggest to change default setting in installer as simplest and as most of users are afraid of this and do not change it at all, ever.

[ailurophobe]

The problem is that the default setting is default for a reason. But you are right the queue management is kind of intimidating. Most users probably have no idea of what is actually does and what it can do. Most p2p applications offer a small fraction of the features and user control. Only real missing feature is that since Shareaza does not persistently keep track of uploads and downloads per user, you can't duplicate a credit system. And you can't filter by country. (No idea why anyone would want to.)

Maybe somebody (no developer needed) could write an in depth tutorial of how the queue system works and then this could be added directly to the UI. Basically giving major windows/panels/dialogs all a wiki page and adding a link to the correct page to the UI either in the context menu or as a help button. Help button would probably be better. A small circle with a question mark in it doesn't take much space or confuse anyone. Would need to key the wiki pages by version though. And somebody would still need to write and edit the content. But this would help users and take very little developer resources. Maybe an idea for 2.6?

[lostcowboy]

Hi in my opinion the queue default settings should be put back to the way they were in the 2.0 version. Back then the G2 network was the fastest network. The G2 network has slowed down over the years. I believe there are two reasons for this. One is that many people have become so scared that they are not sharing what they download.

The other reason is the queue settings that have been changed. The large file Queue size should be changed from 10 back to 20. This helps people get on the queue. Next the rotation time is set at 3600, this needs to go back to 600. 600 is enough time to get two chunks of the file, remember G2 has a much smaller chunk size than ed2k has.
3600 is the proper rotation time for the ed2k queues which are set at 300, which is way to short for their chunk size.
As far as the speed settings are concerned in V 2.0 all the queues had the same speed.

[kevogod]

There has never been a real analysis of what the best queue settings are for the networks. The default queue settings are not optimal since they are not based on observations, just pure conjecture. A good deal of Shareaza's default settings are far from optimal: number of downloads, number of uploads, connection speed, bandwidth limits, etc.

[lostcowboy]

Hi kevogod, from what I could see they were set pretty good in the 2.0 version.
My understanding of the G2 chunk size is 1024 KBs when you divide that by 300 seconds you get a upload speed of 3.4 KBs which is about the download speed of a good 58K modem. with the partial queue set at 300 you can upload 20 chunks a hour to 20 different clients one each, with the large file queue set to 600 you can upload 20 chunks a hour to 10 different clients two each. The way I remember it the partial queue length was set at 10 and the large queue length was set at 20. Myself always set both to 64 and never had any problems. It used to be that when ever I had to get a file off the ED2K network, very shortly I would have one or more G2 network buddies show up to give me a hand. Now they never show up and I have to do all my downloading from the ED2K clients. Boy do I miss my G2 buddies!

PS: on the ED2K network a 9.3 MB chunk can be downloaded in roughly a hour (3600 sec.) at a download speed of 2.6 KBs, which a 28K modem can do.

[old_death]

I've requested a queue for very small files (smaller than 1MB, so text files and pictures = files that need only a single transfer to be finished) for a long time to reduce the number of these files filling up positions of the other queues...

[mojo85]

[old_death]

As I've pointed out, a queue for the very small files would be handy. Also, that many queues result in a big split of the bandwidth...
Therefore I'd suggest to have a partial queue, one queue for files up to 1MB (to keep those out of the other queues), a queue for medium sized files (up to 100MB) and a queue for files that are larger than this.