Outline · [ Standard ] · Linear+ I love this!, zz's uploads

Take a look:



ZZ, you are the man.. This is the best thing since sliced bread...the best thing I have seen since my switch from eDonkey to eMule
Now all we need is EVERYONE on the eMule/eDonkey network to have this same feature. I planned on making my next release to the network in a few weeks...I don't think I can wait that long..I have to try out your system..

BTW I think we need a new sub-forum...for general eMule chit chat...what do you think? This post sure as hell don't fit in this forum or any other..

I guess I'm the only one who likes ZZ's upload system.. lol

Most of the team like it... and most users but will take some time until all of them get accustom to it.

I agree, it a very good system but yes it does take abit of getting use to after so long with low slot speeds

i think it a good idea to seems to work for me to

works for me

at first i was kinda shocked and freaked out by it. but after studying how it works i realised what was going on and how incredibally efficent a system it is.


i like emule plus because they only add usefull things to the client. no bs.

Thank you for your kind words.

I'm very happy that the patch has finally been included in one of the popular mods.

/zz

The one to thanks is you zz, you made a beautiful piece of code. Some details are being corrected by obaldin but is performing quite good now.

Yes, there's still a lot of potential for tweaking. Some things should perhaps be exposed to the prefs, even.

If you make any changes, please send me diffs in a PM.

/zz

ZZ Upload Rocks!!

I've released many bluegrass albums over the last couple of months. All the files have about the same amount of popularity and are about the same size. I always use release upload priority for my release files. ZZ upload has spread the file well through the edonkey network in about 3 days where it used to take 1-2 weeks for the files to become well spread.

ZZ, you've done a great thing here.

sak64

I'm very happy to hear that it actually works for releasing files. Before, I had a theoretical reasoning that it should be better, but I didn't really know. Now I've heard from enough people that says it's making a difference, that I'm actually starting to believe it does

If you are a releaser, you should also check out the überpriority patch I'm currently working on. It enhances the release priority so that it exclusively uploads files with release priority if there's enough demand for these files to fill the bandwidth completely. This means a releaser won't have to unshare his other stuff, and he can still download files normally while releasing.

An early version is available at:

http://www.lava.se/emule/dynamicul/

It is based on the official eMule 0.26d, but perhaps the eMule Plus team will consider includeing it in Plus, when I've tested it and gotten some feedback.

/zz - release prioriority über alle

This post has been edited by Mr zz: Mar 4 2003, 20:47

Gollum... my statistical chart looks exactly like yours (except at 40k)... and when I first saw it... my jaw dropped.

I went through mod after mod... (sivka, mortillo, lovelace, fusion, etc...).. all had vicious drops when switching clients.

I never seen a smooth line like that until ZZ's work. And at 40kb/s!

@sak64 - I'm glad to hear your input on the distribution of files over the network. I was coming to the same conclusions... however i need a bit more testing to see the effect. However, i'll be looking for those albums. I've been wanting to get my feet wet in some bluegrass.

thank you ZZ
thanks emule team!

QUOTE (Mr zz @ Mar 4 2003, 08:45 PM)

If you are a releaser, you should also check out the überpriority patch I'm currently working on.

Did you open a thread on some forum maybe about it, or posted some explanation? I still think that one of the best things (besides the brilliant code of course ) about your dynamic slots patch was that thread on the official forum that with all its clever arguments was able to prove to many people that your (rather unconventional) system is really superior.

This is how the überprioritizing works:

How it picks the client to upload to:
- it sorts the clients in queue by three things (where first is most important): 1) is it a friend with a friend slot; 2) does it request a file that has release priority, 3) credit score
- when it's time to open a new ul slot, it gives the slot to the client rated highest according to the above sorting. That is, 1) if there's a friend, it picks that, no matter what file or credits. 2) If there's no friend, but a client that wants a release file, it picks that client. If there's no friend, but several clients that want release files, it picks the one of those that has the highest credit score. 3) If there are no friends, and no clients that want release files, it picks the client with highest credit score.

How it prioritizes clients in the ul slots (higher priority will mean a client can take bandwidth from a client with lower priority, lowest priority slots will propably be put in trickle mode):
- friends have highest priority, sorted by time in ul slot (longer time than another client = higher priority than that client)
- then comes clients downloading release files, sorted by time in ul slot
- normal clients, sorted by time in ul slot

What happens when a client completes a chunk:
- if there's just one friend slot, it will continue downloading. If there are several friend slots, the client will have it's priority reset, that is, it will get the lowest priority of all friend slots.
- clients downloading a release file - system will check if there's another client on queue that wants a release file. In that case the first client will be kicked, and the other client will get a slot. If there's no other client that want's a release file, the client will have it's priority reset, that is, it will get the lowest priority of all clients currently downloading a release file. But it will continue downloading. This means the next highest client that downloads a release file will get all available bandwidth (unless there's a friend. Friends have higher priority than any other client).
- normal clients will be kicked, unless the queue is empty (which almost never happens). If the queue is empty, the client's priority will be reset, and it will most likely be turned into a trickle slot.

So clients will rotate in the slots, sometimes getting full bandwidth, sometimes being trickled, even if they continue transfering. They raise in priority until they complete the chunk, then they are lowered.

Also, once every three seconds, the system checks the last ul slot (client with lowest priority) and sees if there's a client in the queue that outranks it. If there is an outranking client, the last client is kicked out and replaced with the outranking client. That is, if last client is a normal client, and there's a client in the queue that wants a release file. Or if the last client wants a release file, but doesn't have a friend slot, and a client with a friend slot is in the queue. However, a normal client can never kick another normal client, a relese client can never kick another release client, and a friend can never kick another friend.

That's it!

Currently when file priority are changed back to normal from release, or a friend slot is turned off, it may take until the client finishes it's chunk (and is kicked out) before the ul slot sorting takes full effect. I plan to fix this in the next release.

I'll have to copy this explanation and insert it on the info page.

/zz

Here's the newly posted thread in the eMule developer forum. But remember, you read it here first!

http://www.emule-project.net/board/index.p...=ST&f=4&t=11097

/zz