[Mldonkey-bugs] [ 100930 ] hd goes crazy

[nobody]

Support Request #100930, was updated on Sun 05/19/2002 at 16: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: mtiihone
Date: Wed 05/14/2003 at 19:30
Logged In: NO 
Browser: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030509

My main problem is not mldonkey using all CPU time (it never
uses more than 2%), nor does it harm me that my very slow
NFS server runs busy.

The problem is that while waiting for the data to md4
process, over the slow link I can not do anything about, the
mldonkey halts all other processing. This includes the
network traffic and the gtk/web/telnet interfaces.

This makes mldonkey completely useless for file sharing
during this time, which I will still last 2-3 days in my
setup. I don't think this is an acceptable delay for the new
user of the software before it can actually be used.

The only possible solutions to this i can think of are:
1. copy files to local hard drive so mldonkey can read them
faster (i don't have enough free space to do this)

2. make mldonkey md4 processing a separate thread that does
not block normal file sharing processes

3. provide an external tool that does the md4 processing and
stores the results in the correct format and after
processing restart mldonkey to read the information

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

By: noon
Date: Wed 05/14/2003 at 18: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

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