Print

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

[CrystalKaeru]

After starting aMule, maybe other eMule clients as well, it takes almost an hour before enough peers have started requesting files from you again so that you can upload efficiently. At least using KAD only. Normally there is more than 20 peers in my queue, but now, an hour after start, there is only two peers downloading from me (0 in queue) and they does not even use my whole upload capacity. And it is always the same.

This is very bad for the performance of the network, since during this hour you could have uploaded much more. Some days I can only run aMule for say three hours, which means only two hours (67% of the time) with full upload speed. I also think that this might be relevant to the fact that it takes quite some time before my node finds newly connected (to the network, not me) peers to download from if they are not downloading the file themselves too, since they won't contact me or anyone else transferring that file.

Isn't there a way to save the list of peers in your upload queue on shutdown and when you start aMule again, they are contacted and informed that you are online and then can request the file again. Also maybe a possibility to get the same spot in the queue as they were in on shutdown, if they request the file immediately when you informed them you are online again.

[Kry]

There are eMule mods with similar capacities, and while I don't necessarily agree with the feature as set in stone, we can implement it in a simialr way to what source seeds do (i.e., with some time limit, etc).

We'll see about that.

[gav616]

Also maybe a possibility to get the same spot in the queue as they were in on shutdown, if they request the file immediately when you informed them you are online again.

SUQWT

[Kry]

Except I'm not a big fan of that implementation.

[CrystalKaeru]

Also maybe a possibility to get the same spot in the queue as they were in on shutdown, if they request the file immediately when you informed them you are online again.

SUQWT

Except I'm not a big fan of that implementation.

What is wrong with that. I did some searching but couldn't find anything. Just curious.

But that was not the important part, if it's not wanted, ignore it.
The thing I wanted solved is the fact that it takes a long time before enough peers have connected to my client for it to be able to upload efficiently/fair at the full capacity I got (rather low by the way).

[Stu Redman]

Can't see what your problem is. I get full upload speed like a minute or so after startup, even with only a few file shared. Are you sharing extremely rare stuff only?

[^marcell^]

You also have to take into consideration that uploads start a lot slower if you have been offline for a longer period - don't know the exact time frame for this. Might this have been the case in your situation?

[CrystalKaeru]

If I just shut down aMule and then start it again, all peers who was in my queue would try to contact me again and hence no problem. Also uploading to them who are currently downloading the same files I am also start within minutes, since my client contacts them so they know that I am online.

What I described happen when I have been offline for more than 12 hours, and for files I am only sharing. Yes, I share almost only rare files, like less than 5 sources, and am only downloading a few files at once, them being rare as well. But if my client have been running for a few hours my full upload capacity is utilized and there is usually more than 15 peers in the queue as well, all the time.

And remember I'm running KAD only, no servers. I don't know if that makes any difference. But it seems as as soon my ip is spread using peer exchange instead of DHT, all peers downloading that specific file will connect to me. It is the DHT thing that may take up to an hour to happen for enough many files.

[Stu Redman]

You've been dropped as valid source after that time. It takes a while for your published information to reach the clients.
I don't find this serious:
- You should be able to fill your upload capability easily with your ongoing downloads (which start uploading at once) until the shares kick in.
- aMule is supposed to run for longer times anyway, so the slow start doesn't matter much. It's much more you who is "hurting the network" by turning it off in the first place.  If you don't have a flat rate (I remember my good old 100h/month DSL contract...) better spend it in fewer larger chunks.

[CrystalKaeru]

Ok.

I know it's bad repeatly leaving the network each day, leaving many rare files without sources. It's just that I think most people do this. When I download a file certain peers seems to be online during a few hours, then disappearing and appearing again the next day. Only a few peers seems to be online all the time, most don't. I never leave my computer on during night and when not home.

I thought it would be nice if uploading started sooner, expecially for rare files, since in that case I would be able to contribute more. But if this feature is not feasible or wanted, I guess I can live without it.
(but I really really like to upload, so I really wanted this)

[Kry]

You realize that SUQWT won't help you at all, as your problem is with peers finding you in the first place?

[Stu Redman]

What would be required here is to search for sources for shares too, contact these and ask for the file you are sharing. Then they will ask you too. Could be done, but I don't think it's worth the effort.

[GonoszTopi]

search for sources for shares too, contact these and ask for the file you are sharing. Then they will ask you too. Could be done

No.

[Stu Redman]

No, wouldn't work, no, should not be done or no, too stupid to comment? 

[GonoszTopi]

no, should not be done

You're right, I need to express myself using a bit more words.