Upload Slot Limit -- no more 200 opened slots --
#1
Posted 05 February 2006 - 11:05 AM
reading in the forums one of the most popular requests is to lower the number of opened slots because for high speed lines it's *extremely* annoying to upload to 50+ Clients at a low speed, increasing the concurrent connections...
So I want to ask the devs to put in one/all of the following:
Slot focus:
Concentrate upload on as few clients as possible, automatically lowering the number of opened slots
Adjustable/automatically adjusting Clientdatarate:
This is a *very* small change and easy to code but it's pretty effective.
Raising the datarate from the default 3kB to e.g. 10kB for higher speed lines will save 2/3 of their opened slots and no bandwidth will be lost because if the upload isn't saturated more slots can still be opened
Also possible to add some kind of automatic detection, e.g.
3kB for <= 10kB UL ~ 3-4 Slots
5kB for <= 20kB UL ~ 4 Slots
9kB for <= 30kB UL ~ 3-4 Slots
and so on... so no one could "misconfigure" his client
Timelimit before opening a new slot:
It's *pretty* annoying that eMule currently opens a new slot if you get below the set uploadlimit for a very short time. I suggest adding a "open slot blocker" for ~5-15 seconds - if the upload is still not saturated then a new slot is opened
All features are already available in some mods and more or less usable so there would only be some testing required... it would really help the highspeed clients because having 250 active connections of which 200 are upload slots isn't a funny thing at all
#2
Posted 05 February 2006 - 09:34 PM
tHeWiZaRdOfDoS, on Feb 5 2006, 11:05 AM, said:
reading in the forums one of the most popular requests is to lower the number of opened slots because for high speed lines it's *extremely* annoying to upload to 50+ Clients at a low speed, increasing the concurrent connections...
So I want to ask the devs to put in one/all of the following:
Slot focus:
Concentrate upload on as few clients as possible, automatically lowering the number of opened slots
Adjustable/automatically adjusting Clientdatarate:
This is a *very* small change and easy to code but it's pretty effective.
Raising the datarate from the default 3kB to e.g. 10kB for higher speed lines will save 2/3 of their opened slots and no bandwidth will be lost because if the upload isn't saturated more slots can still be opened
Also possible to add some kind of automatic detection, e.g.
3kB for <= 10kB UL ~ 3-4 Slots
5kB for <= 20kB UL ~ 4 Slots
9kB for <= 30kB UL ~ 3-4 Slots
and so on... so no one could "misconfigure" his client
Timelimit before opening a new slot:
It's *pretty* annoying that eMule currently opens a new slot if you get below the set uploadlimit for a very short time. I suggest adding a "open slot blocker" for ~5-15 seconds - if the upload is still not saturated then a new slot is opened
All features are already available in some mods and more or less usable so there would only be some testing required... it would really help the highspeed clients because having 250 active connections of which 200 are upload slots isn't a funny thing at all
Probably we should have number of upload slot configurable as any other connection parameter. Estimated upload speed can be calculated from requested number of upload slots and upload limit. First-time run wizard can configure eMule as you propose.
In this case each eMule-er () can configure favorite pet without needs to re-compile it.
What you think about?
#3
Posted 05 February 2006 - 09:55 PM
The official client can already be used to leech easily, don't make it any easier...
For example: Your upload capacity is 100kB - now you want to spread very fast and set a max of 2 slots.
This *might* work if you have some clients in your upload who can take it but take a worst-case scenario, e.g. 2 modem/ISDN users who are ALREADY downloading from someone else... they will take ~1-2kB each - that's 2-4kB in total and the remaining 96kB are wasted because no more slots are opened.
That's why I proposed to put in an adjustable datarate - this will try to upload the amount you enter per client but if it fails, it will open another slot.
#4
Posted 05 February 2006 - 10:43 PM
tHeWiZaRdOfDoS, on Feb 5 2006, 12:05 PM, said:
It's *pretty* annoying that eMule currently opens a new slot if you get below the set uploadlimit for a very short time. I suggest adding a "open slot blocker" for ~5-15 seconds - if the upload is still not saturated then a new slot is opened
I quote this particulary.
#5
Posted 06 February 2006 - 11:59 AM
Its fun to watch the statistics window... U never see the the line for total upload in the connections window... it goes only to one hundred clients...
#6
Posted 06 February 2006 - 12:46 PM
P2P is not piracy, it's marketing.
In fact, if your music or movie is NOT being downloaded, you should be WORRIED !
If you can't even give it away for free, how do you expect to sell it, stupid ?
#7
Posted 16 February 2006 - 04:41 PM
Bored??? Release your inner mule and get involved with your favorite file sharing program, EMULE!!!!!! Check out my feature request.
Modifications!!!....................Speed Up eMule!!! Partly Done
On Queue 2........................Individual Max Sources/File Partly Done
Advanced Sorting.................Slot for Small Files
Easy Switching.Partly Done....Advanced Priority System
To accomplish great things, we must not only act, but also dream; not only plan, but also believe
#8
Posted 16 February 2006 - 08:42 PM
Quote
Set a minimum hardlimit for slots, 4 or 5 slots.
Then open slots every 3sec untill it reachs the max speed limit.
a little simulation, max upload 100kBps
open 4 slots.
3sec latter, 30kBps, open another slots (5)
3sec latter, 55kBps, open another (6)
3sec latter, 95kBps, open another (7)
3sec latter, 100kBps, it's ok.
#9
Posted 17 February 2006 - 04:20 AM
This post has been edited by slowsilver: 17 February 2006 - 04:21 AM
* * *
eMule has enough anti-corruption measures.
-- SF, Oct 30 2005, 07:08 PM
#10
Posted 18 February 2006 - 09:56 AM
To sum my needs, i'd prefer to give e.g. 8 to less over 3 to many......but same time no desire to call on a big rewrite if its not practical for the net-management.
EDIT TO MY ORIGNAL POST FEB.18.06, DONE ON MAR.03.06
I happen to stumble on an setting in Expanded/Advance Settings (translation from Dutch). Down the bottom of the 50 or so options there's a line "Lowest Allowed Sending Speed" of the Upload Sensory section...you can do the sums on the total upload speed you allow eMule, divided by the desired minimum speed of each upload slot. E.G. if you want the max total to be 16 and the maximum slots 4, set lowest upload speed to 4. If the total of the 4 dont acquire 16, further slots will be opened to maximise the total available upload speed, but that i think is fine.
This post has been edited by RobertosEmule: 02 March 2006 - 08:39 PM
#11
Posted 18 February 2006 - 10:48 AM
tHeWiZaRdOfDoS, on Feb 5 2006, 11:05 AM, said:
Concentrate upload on as few clients as possible, automatically lowering the number of opened slots
Adjustable/automatically adjusting Clientdatarate:
This is a *very* small change and easy to code but it's pretty effective.
Timelimit before opening a new slot:
It's *pretty* annoying that eMule currently opens a new slot if you get below the set uploadlimit for a very short time. I suggest adding a "open slot blocker" for ~5-15 seconds - if the upload is still not saturated then a new slot is opened
the first seems nice but I think that the second and third suffice (and looks quite esier&simpler to implement ).
Another important think to consider is that p2p is causing great problmes to ISPs not only for data traffic(bandwith used) but great number of opened connections seems another issue for them to handle with.
These features 'll diminuish the overall connections (by half or more) by giving a emule's fairer behaviour (ISP's oriented ;-) ).
Cheers
#12
Posted 19 February 2006 - 09:38 AM
#13
Posted 19 February 2006 - 10:15 AM
Ah btw: I also pledge for a static "1 chunk" upload - this would reduce CPU usage, overhead and would help files to spread faster.
#14
Posted 01 March 2006 - 06:45 AM
Allow the user to modify the threshold of unused bandwidth. That is, if your upload limit is 100kB, a new slot is created if the bandwidth falls below 100kB... by how much?
The number could be set, either in absolute kBs, or as a percentage of the current upload limit.
This post has been edited by dodo4lurk: 01 March 2006 - 06:47 AM
#15
Posted 29 October 2006 - 05:49 PM
Screenshot of ZZUL Bastard mod v0.47a (19 open slots)
56 kB / 19 slots equals 2.9 kB/slot. You can see that SlotFocus in this case provides no benefit over the fixed 3-4 kB bandwidth upload slot. Instead of sophisticated speed sensing algorithms I need a simple "MaxSlots" option. I don't mind having periods with only a few very slow peers connected as the machine is running 24/7 and serving also for other purposes besides ed2k.
fatbar said:
If you suspect the presence of "maxslots" value will aid leeching:
1) Don't use maxslots yourself.
2) Make the smallest allowed value equal 3. 3*4 kB > 10 kB – the lowest upload speed w/o restrictions to download bandwidth.
This post has been edited by j7n: 29 October 2006 - 06:00 PM
#16
Posted 31 October 2006 - 10:49 PM
fatbar said:
Upload speed 695 KB, opened slot 92, max speed 11 KB, total mess.
same situation at the very end of a file, too often Emule leave a fast client and get stuck with a slow one forever.
Hey, with obfuscation now we have lot's of bandwidth on symmetric connections.......
-m
#17
Posted 03 November 2006 - 10:06 PM
tHeWiZaRdOfDoS, on Feb 5 2006, 12:05 PM, said:
reading in the forums one of the most popular requests is to lower the number of opened slots because for high speed lines it's *extremely* annoying to upload to 50+ Clients at a low speed, increasing the concurrent connections...
So I want to ask the devs to put in one/all of the following:
Slot focus:
Concentrate upload on as few clients as possible, automatically lowering the number of opened slots
Adjustable/automatically adjusting Clientdatarate:
This is a *very* small change and easy to code but it's pretty effective.
Raising the datarate from the default 3kB to e.g. 10kB for higher speed lines will save 2/3 of their opened slots and no bandwidth will be lost because if the upload isn't saturated more slots can still be opened
Also possible to add some kind of automatic detection, e.g.
3kB for <= 10kB UL ~ 3-4 Slots
5kB for <= 20kB UL ~ 4 Slots
9kB for <= 30kB UL ~ 3-4 Slots
and so on... so no one could "misconfigure" his client
Timelimit before opening a new slot:
It's *pretty* annoying that eMule currently opens a new slot if you get below the set uploadlimit for a very short time. I suggest adding a "open slot blocker" for ~5-15 seconds - if the upload is still not saturated then a new slot is opened
All features are already available in some mods and more or less usable so there would only be some testing required... it would really help the highspeed clients because having 250 active connections of which 200 are upload slots isn't a funny thing at all
Hi!
Do you plan to implement this in a mod, I'd like to try it
Aide officielle eMule Tutoriels, Aides diverses et liens utiles >>TADELU<<
Les règles du forum
Ce serait sympa de lire "A lire avant de poster" AVANT de poster, il sert à ça ce post
LENTEUR DES TELECHARGEMENTS : LES RAISONS
#18
Posted 04 November 2006 - 12:37 AM
j7n, on Oct 29 2006, 06:49 PM, said:
56 kB / 19 slots equals 2.9 kB/slot. You can see that SlotFocus in this case provides no benefit over the fixed 3-4 kB bandwidth upload slot. Instead of sophisticated speed sensing algorithms I need a simple "MaxSlots" option. I don't mind having periods with only a few very slow peers connected as the machine is running 24/7 and serving also for other purposes besides ed2k.
Maybe setting USS correctly may help you:
/edit: WTF, photobucket now automatically rescales big images!
This post has been edited by CiccioBastardo: 04 November 2006 - 12:41 AM
#19
Posted 04 November 2006 - 01:06 AM
CiccioBastardo, on Nov 4 2006, 01:37 AM, said:
Quote
Hence the word 'smaller' in the text I quoted from their homepage..
#20
Posted 13 June 2022 - 12:46 PM
Made a small patch to update those limits and apply them in the latest Community version
https://github.com/i...c118ab954f2f52d
Given the size of files shared these days, and the much higher bandwidth common available, it is not practical to have tenths of files being upload which cause lots of I/O contention and overhead. It's much better to have few slots at max speed uploading for as long as needed. Specifically SESSIONMAXTRANS was too low, disconnecting clients in the upload queue every 9Mb
Ideally these params should be put in config file, so to be tuned based on the need.
--
The key values that should be configurable are
SESSIONMAXTRANS SESSIONMAXTIME MAX_UP_CLIENTS_ALLOWED UPLOAD_CLIENT_MAXDATARATE
This post has been edited by brand33d: 13 June 2022 - 02:20 PM