aMule Forum
English => aMule Help => Topic started by: Guest on November 19, 2003, 02:22:14 AM
-
Helo all,
I can't find out why, but my High CPU usage (80-90%) is due to an always hashing and rehashing shared files....
I share Gigs of data over the mule and aMule always rehash in loop, and it restart hashing everything every time I lauch it :cry:
On every launch, it says "Found xx know files, hashing yyy new files now"
xx correspond to the currents download (it doesn't rehash them again)
yyy correspond to my shared files, and rehash it on everylaunch :cry:
I was hopping that the hashing process have to end on time completly to do no it again, but unfortunatly for me it restart again hashing Gigs of data (nearly 40-50 Go ... can be up to 60-70Go) (due apparently to the category directory, which are the same that the share directory!)
I precise that only gtk1 is installed (no gtk2 so can't be that)
I precise also that I launch aMule whit : "export LANG=C ..."
but i've got the following message on aMule launch : "Gdk-WARNING **: locale not supported by C library"
Last point, my partition is FAT32 because it came from an "old" :lol: win box and I don't have enought space to store everything of this while reformating to reiserfs or ext
Pleaz, where is the "big" mistake that make the hashing never stops??
May I wait for many days before it end, but if it's again like that on every launch of aMule.... :?
PS : sorry for my "frenchy" english
Sad
-
I do not really know if it's the same reason.
I started up freshly to aMule, so I have no files in share (for now).
I only download several files.
So it can't be hashing shared files, but my cpu (Athlon 2200+) goes to 50% usage for amule frequently. Peaks are 100% , lowest usage 25%
The amule task is up now for 24h and the CPU consumption is 442:36.00, so averaging to 31%, which is - as I feel - a awfull lot for a p2p client.
Some hints?
-
Original von Anonymous
I do not really know if it's the same reason.
I started up freshly to aMule, so I have no files in share (for now).
I only download several files.
So it can't be hashing shared files, but my cpu (Athlon 2200+) goes to 50% usage for amule frequently. Peaks are 100% , lowest usage 25%
The amule task is up now for 24h and the CPU consumption is 442:36.00, so averaging to 31%, which is - as I feel - a awfull lot for a p2p client.
Some hints?
try to compile wxGTK by yourself (howto here in forum) ..
@Sad - why u share 50 +gb ?? u know the server doesn't read/allow all your files ?!?
-
Well, no i don't know that :lol: 8)
I hate leechers and I always try to keep what I've downloaded accessible to others users :lol:
So, how many files/size does servers allow me to share?!?
(aMule is still running since I wrote the first post, can see it on the shell windows saying Sharing /xxxxx/xxx/xx or something like that :lol: )
I'll try to lower the amont of shared file, but why does aMule always restart hashing, and doesn't consider file already hashed as known???
Thanks for all, aMule is still great and you really do great job!! 8)
Sad
-
By the way, i've forgot this : I've compiled everything whith the README configure options for wxGTK
Sad
-
How many files do you share?
-
Not so much in number of files (nearly 250) but in Size, this make nearly 40Go
Sad
-
See on the stat page :
Number of Shared Files : 218
Total size of Shared Files : 48,21 GB
Average filesize : 226,44 MB
Hope it'll help
Sad
-
Another point, which is maybe the cause of always restarting hashing shared files.... how did am I supposed to stop aMule??? maybe the pb is here!
Sad
-
Well... due to a needed restart of the system, i've restart aMule....
And once again, it says me that it founds "Found 19 known shared files, hashing 412 new files now" ... :cry:
So ... once again... it restart ALL :oops:
Why?????!!!!????
Should I see any kind of message saying "Hashing shared files done" or something like that?!??? :?:
I'm gonna share nothing, in order to see if it works better....
Sad
-
Well... after hashing the incoming files, the CPU usage drop down under 20%, which is good in my view (CPU is Atlhon 1Ghz)
But why my shared files are always "new" and needs hashing...??? :?
I'd really like to know!!!!
Sad
-
I really don't understand.... After adding a little bit amont of files (160MB), the CPU usage go up while hashing then go down when hash end. So I restart aMule "just for see" and even if aMule says "Found 23 know shared files, hashing 9 new files now" the hash process was done in only 1sec... so it doesn't really hash (it need 5 good minutes to hash this when I first add the share)
So ... what is the maximum "allowed"??
Sad
-
-
Maybe this has something to do with the configuration of your system.
On Linux, you can configure you filesystem to keep the date of the last modification of a file or the date of the last opening of a file. If amule does rely on the date of last opening, then the files are re-hashed at every startup if the file has been send at least once in the previous session.
You can change the configuration of your filesystem, but I can't remember the command. Maybe something like "hdparm"... Anyone knows ?
-
I've seach on the net, and this option is not in hdparm!
It's in the /etc/fstab .... the option is noatime (no acces time)
"Additionally, entire partitions can be mounted with no access time updating (...) The syntax to do this automagically is to edit the /etc/fstab, adding in the noatime option to the options column, separated by a comma. e.g.:
# device mount point type options dump frequency fsck pass number
/dev/sdb1 /var/spool/news ext2 defaults,noatime 1 2"
So I'll try it on the next reboot :lol: :lol:
Thanks for all
Sad
-
still, anyone worked out why the CPU usage on aMule is so massive ?
-
Well, I fixed some CPU usage on CVS so it dropped a lot on systems that are d/l at high rate, and it also seemed to make the mule dl faster... maybe 'cos we were losing packets because amule was unable to process them due to cpu usage.
Right now, amule d/l at my line full speed (35 kb/s) in... less than 15 min!
Can be luck, but it's 3 days of luck right now.
So wait for amule 1.2.1 that will be one of the bests releases ever.
-
hmmmm, sounds good... 1.2.0 is the first release which doesnt work for me, so I hope 1.2.1 fixes that ;-)
-
I am full of desire . . . thanks for good work
Sebastian
-
Original von superstoned
for me, it doesnt rehash everyting now. my files are on a reiserFS with noatime...
yes, i can confirm it.
also, it's better to use the noatime option - with this option the OS
doesn't need to reread the directory structure/file contents every
'ls' issue for example
What i've observed is that BOTH aMule and xMule are constantly rehashing
the files if they're on a FAT32 partition. (tried this on my friend's box with aMule 1.2.1)
Hopefully this FAT32 issue is probably fixed with the 1.2.3 release
(the changelog says, that chmod is ommited for fat32, maybe it's enough for it to work)
Please somebody confirm if the new version works well with fat32...