aMule Forum
English => en_Bugs => Topic started by: jbouzane on April 05, 2004, 10:55:58 AM
-
aMule is really doing a number on my hard drive. I've got about two dozen files queued up for transfer and four are being transferred at a total speed of 40 KB/s or so. However, despite the small number of actual downloads and the moderate speed, my hard drive has a full time job trying to keep up with it.
I know it's aMule because a) quitting aMule causes the hard drive to be silent, and b) opening up aMule's Temp directory in konqueror shows that the *.met and *.met.bak files are in some type of juggling act. IOW, they are constantly being updated, perhaps on the order of once per second or more. Multiply this by a dozen files or so and you've got a lot of work.
This problem doesn't occur until after aMule has been running for a while. This is probably because it takes a while to get more than one or two files transferring, although I can't be certain the *.met and *.met.bak files belonged only to the files that were currently downloading. It seems like there were more being updated than downloaded, actually.
That said, is there any way to reduce the frequency at which these updates are written to disk? The load this is putting on my hard drive is ridiculous. Currently, I'm trying out xMule to see if it has the same problem.
-
Ah, it's too late at night.
I forgot to mention that I'm trying 2.0.0rc1 on a Linux 2.6 kernel, I have no files shared other than those that I'm downloading, and this is a clean install, not an upgrade.
Sorry about leaving that out of the original post.
-
hey,
I think searching the forum would have helped ;)
try to unset all auto priorities to non auto
for the files you share and for the files you are currently downloading
it helped for most people...
this bug will be fixed in rc2 don't worry :)
stefanero
-
Yeah, sorry. I noticed that shortly after I posted and I'm trying it now.
-
That fixed the problem. I did actually look through the bugs forum, but I stopped reading that other thread when the problem was blamed on rehashing files.
-
So, after haveing an rc2 experience, are you suffering from the same bug?
Thanx for keeping reporting the problems you find in aMule ;-)