I'm noticing upload connections to aMule users seem to be short-lived from my eMule client. Is that a common problem? Is there a way to improve it?
Page 1 of 1
Short Lived Connections Between Emule And Amule Users?
#2
Posted 29 May 2023 - 02:57 PM
What does short-lived connection mean exactly?
Maybe it's an aMule specific behavior, do you notice any difference between versions?
They just had a recent release 2.3.3 and their forum is pretty active I think.
Maybe it's an aMule specific behavior, do you notice any difference between versions?
They just had a recent release 2.3.3 and their forum is pretty active I think.
#3
Posted 30 May 2023 - 05:12 AM
Usually connections to uploaders are steady or fast, either downloading the whole file quickly or steadily getting large chunks over time.
But the one aMule client I noted trying to download one of my files would connect at a fast speed, then quick get cut off after maybe a few seconds. It would then take a very long time for them to reconnect. They were making progress, but very very slowly.
Of course this could be just a problem with that one aMule user, but I thought I'd ask in case it's common.
But the one aMule client I noted trying to download one of my files would connect at a fast speed, then quick get cut off after maybe a few seconds. It would then take a very long time for them to reconnect. They were making progress, but very very slowly.
Of course this could be just a problem with that one aMule user, but I thought I'd ask in case it's common.
#4
Posted 30 May 2023 - 07:40 AM
Hmm, do you know which aMule version the client reported?
I was using aMule myself for quite some time, I don't like the client that much.
But on non-windows there weren't/aren't much other choices.
I was using aMule myself for quite some time, I don't like the client that much.
But on non-windows there weren't/aren't much other choices.
#5
Posted 30 May 2023 - 04:19 PM
I didn't think to check the version of the connecting client at the time, and they're done downloading the file (judging by the file upload stats).
I've seen another aMule client somewhat struggling to maintain a constant speed (speed goes down to zero every 5 to 10 seconds or so), but they're doing way better than that one really slow user and are able to maintain a connection. They're using the latest version (2.3.3)
I've seen another aMule client somewhat struggling to maintain a constant speed (speed goes down to zero every 5 to 10 seconds or so), but they're doing way better than that one really slow user and are able to maintain a connection. They're using the latest version (2.3.3)
This post has been edited by jenkin: 30 May 2023 - 04:21 PM
#6
Posted 02 June 2023 - 12:25 PM
You are seeing things from your perspective, but on the other end they may be having issues with congestion, packet routing, session overload, multiple P2P software running, and hardware performance issues such as page thrashing, or a slow or dying hard drive. Just do your bit and share, and the design of self-repair and error checking should take care of the rest.
Example: Just last week I had an elusive file that had been queued for weeks for download with three sources. One source would report a error and then another source would be used to download the same portion, and that would report an error, and so the circle would repeat over and over. Eventually the bad source must of given up or disappeared off the internet and the relevant portions were completed from the other two sources and the intact file finally downloaded. Fortunately I have un-metered internet, so it wasn't an expensive exercise, but I am sure many megabytes were wasted just to get two faulty 9.28Mb segments over and over from the same bad source. It hasn't repeated with other downloads, so I am confident the other end had drastic issues.
Example: Just last week I had an elusive file that had been queued for weeks for download with three sources. One source would report a error and then another source would be used to download the same portion, and that would report an error, and so the circle would repeat over and over. Eventually the bad source must of given up or disappeared off the internet and the relevant portions were completed from the other two sources and the intact file finally downloaded. Fortunately I have un-metered internet, so it wasn't an expensive exercise, but I am sure many megabytes were wasted just to get two faulty 9.28Mb segments over and over from the same bad source. It hasn't repeated with other downloads, so I am confident the other end had drastic issues.
Page 1 of 1