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.