[Mldonkey-bugs] [ 100930 ] hd goes crazy

[nobody]

Support Request #100930, was updated on Sun 05/19/02 at 20:59
You can respond by visiting: 
http://savannah.nongnu.org/support/?func=detailsupport&support_id=100930&group_id=1409

Category: None
Status: Open
Priority: 5
Summary: hd goes crazy

By: noon
Date: Wed 05/14/03 at 22:41
Logged In: YES 
user_id=901
Browser: Mozilla/5.0 (X11; U; Linux i686) Gecko/20030430 Galeon/1.3.4 
Debian/1.3.4.20030503-1

The first time I started mldonkey, I set the shared folder
up and it worked for about 2 days, I guess it was scanning
the 40GiB for md4sums.  The time could be explained by the
fact that my hd was not set up correctly (no DMA at all) (I
used hdparm later on and it is hopefully faster now).

My system was very slow while mldonkey did this md4
processing.  I don't know if there is a way to optimize it.
 40 GiB of share is quite a lot, but my unoptimized HD
transferred data at about 3-5 MiB/s -> It should have taken
less than 4 hours if all went well.  It took much more than
that.  I don't know where the problem is...

Maybe a solution to the problem is to renice mldonkey as
long as it hasn't finished computing most of the md4sums.  I
didn't think about it back then, but maybe it will make the
system more usable for new users when first starting mldonkey.

On some systems, such as GNU/Linux, the command "renice 20
`ps -C mlnet -o %p --no-heading`" might prove useful.

Hope this helps

----------------------------------------------------------------------

By: mtiihone
Date: Wed 05/14/03 at 20:20
Logged In: NO 
Browser: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030509

In my setup the shared files are on a slow NFS drive and
while the scannin is ongoing (now already for 6 hours) the
software is essentially unusable. 

Watching the ltrace of the program shows that it seems to
read 10 megabytes in one go of one file which takes about
1,5 minutes. During this time the mldonkey does not respond
to or process any commands. After the 10MB has been read
there is a 30s time during which the software runs normally
before a next batch of reads occurs.

Could it be possible to make the md4summing a nonblocking
operation?

----------------------------------------------------------------------
You can respond by visiting: 
http://savannah.nongnu.org/support/?func=detailsupport&support_id=100930&group_id=1409