Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[gav616]

Seperate tab for verbose logging (instead using "aMule Log" for everything).

Files tree view in "Shared Files" (makes seeing whats were at a easyer glance).

Complete  removal of  "Source Dropping" (is completely pointless and has no advantages to the user, only disadvantages to the network  i.e. massive reask overheads).

abit controversial but, complete removal of changeable slot speed (why is this nesecessary? i can only see the disadvantages of the common user setting it wrong thus having a unrealiable upload, my view is to just hard code the 3kb from eMule, i just feel that having too many options can hinder this top notch "all-platform" client.

SVN is running smoooth!

thanks for your time.


 

[wuischke]

Files tree view in "Shared Files" (makes seeing whats were at a easyer glance).

Many users (i.e. I) have only two locations for shared files: Incoming and Temp. A treeview makes little sense here, but something like a side bar with a filtering mechanism would be nice.

Complete  removal of  "Source Dropping" (is completely pointless and has no advantages to the user, only disadvantages to the network  i.e. massive reask overheads).

I completely agree. (bug #1079)

abit controversial but, complete removal of changeable slot speed (why is this nesecessary? i can only see the disadvantages of the common user setting it wrong thus having a unrealiable upload, my view is to just hard code the 3kb from eMule, i just feel that having too many options can hinder this top notch "all-platform" client.

I disagree. I prefer to upload to 5 clients concurrently at a higher rate opposed to uploading to 14 clients at 3kb/s each.

[gav616]

Many users (i.e. I) have only two locations for shared files: Incoming and Temp. A treeview makes little sense here, but something like a side bar with a filtering mechanism would be nice.

Well since i have been using Mule (4-5 years) ive always categorized my downloads into folders on my backup HDD for easy viewing of 'collections'. 

I completely agree. (bug #1079)

I disagree. I prefer to upload to 5 clients concurrently at a higher rate opposed to uploading to 14 clients at 3kb/s each.

sorry have to disagree, i personally see no advantage to this, i feel that eMule had a good idear of this (i.e. many upload slots isen't a bad thing, opportunity to spread more files to more people, anyways.... i feel my views on this are clear;

abit controversial but, complete removal of changeable slot speed (why is this nesecessary? i can only see the disadvantages of the common user setting it wrong thus having a unrealiable upload, my view is to just hard code the 3kb from eMule, i just feel that having too many options can hinder this top notch "all-platform" client.

lets agree to disagree 

Seperate tab for verbose logging (instead using "aMule Log" for everything).

opinions on this?

[wuischke]

Seperate tab for verbose logging (instead using "aMule Log" for everything).

Dunno, sounds reasonable to use a "everything" and a "only important things" log window.

Regarding the upload slots: There's no real advantage, except for new releases, where getting chunks of one file to many seeds fast is more important than spreading many files to many users.

I upload with 8KB/s each to 5 users, so it takes about 20 minutes for one chunk to be uploaded. Now I can upload again to new 5 users AND these 5 "old" users can upload as well. So after 40 minutes, I've uploaded 10 chunks to 10 users, which can spread them already, and IF the 5 first uploaders upload the same I do, my chunk has been uploaded 10 times by me and 5 times by each of my 5 first downloaders, equals 35 times in total dring these 40 minutes. (This is purely theoretical!)

If I upload at 3KB/s, I have about 14 upload slots and uploading one chunk takes about 52minutes. It takes longer for my chunk to spread, but it will be more widespread.

The end result is about the same (I upload the same number of chunks to the same number of people), but if I disconnect after 50 minutes there's less harm done (unfinished chunks) when I upload with a higher speed per slot.

I personally see an advantages if you download few files as well, but that depends on too many ifs and whens, that it's more of a personal preference thing.

[eisa01]

If anything, the max value for the slots should be increased. 30K is nothing.

Agree on your other requests though

edit: The behaviour should be changed though, atm my aMule doesn't open new slots if the clients can't fill their slot allotment. Had my upload set to 90K, and 30K for each slot. 3 clients downloading at a total of 5K... Now it's 10K each, and 9 clients. They finally manage to max it out. Why does so many ed2k'ers have so crappy downspeed?

[gav616]

If anything, the max value for the slots should be increased. 30K is nothing.

Agree on your other requests though

edit: The behaviour should be changed though, atm my aMule doesn't open new slots if the clients can't fill their slot allotment. Had my upload set to 90K, and 30K for each slot. 3 clients downloading at a total of 5K... Now it's 10K each, and 9 clients. They finally manage to max it out. Why does so many ed2k'ers have so crappy downspeed?

i had a rant about this couple of months ago.. IMHO slot focus from ZZUL eMule mod just is the best way of slot control,
but for now i firmly stick by hard coding 3kb.

bit of info on SlotFocus;

ZZ SlotFocus: Focus the upload bandwidth to as few upload slots as possible!
(only one, if the top slot wants it all). Transfers files to fewer people at a time, but faster to each. Faster transfers makes chunks complete sooner, making it possible for other clients to share the chunks sooner. This gives more sources in shorter time, sharing the upload demands on several computers sooner. At 76 Kbytes/s ZZUL opens ca 6-10 slots, when official eMule opens 24 slots. ZZUL only opens new slots if necessary to use the configured bandwidth. Upload slot focusing version 2 is available in this patch. Version 1 is used in eMule Plus (and others?). You can see which upload that has the highest priority by checking the number in the "Slot #" column. Slot #1 get all bandwidth it can handle. Slot #2 gets any leftovers after slot #1 has taken what it wants, etc.

When you download a file, it is good for you to give all chunks you already have of that file to other clients as soon as possible. As soon as you have spread your chunks, the other clients will actually help you to download the chunks you are missing. Then you can get those chunks from them (and fast, since you now have good credits with them). It will also be easier for you to get the chunks from the original source, now that is no longer busy uploading chunks that you already have, to other clients. So set your upload speed as high as possible!

but TBO it will be very hard to implement, because of other factors from emule