aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Pages: [1] 2

Author Topic: CPU high usage due to always hashing and rehashing shared  (Read 10349 times)

Guest

  • Guest
CPU high usage due to always hashing and rehashing shared
« 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
Logged

Guest

  • Guest
Re: CPU high usage due to always hashing and rehashing shared
« Reply #1 on: November 19, 2003, 07:30:39 AM »

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?
Logged

deltaHF

  • Evil Admin
  • Former Developer
  • Hero Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 3920
  • .. Legends may sleep, but they never die ..
    • http://www.amule.org
Re: CPU high usage due to always hashing and rehashing shared
« Reply #2 on: November 19, 2003, 10:04:54 AM »

Quote
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 ?!?

Guest

  • Guest
Re: CPU high usage due to always hashing and rehashing shared
« Reply #3 on: November 19, 2003, 03:55:29 PM »

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
Logged

Guest

  • Guest
Re: CPU high usage due to always hashing and rehashing shared
« Reply #4 on: November 19, 2003, 03:58:02 PM »

By the way, i've forgot this : I've compiled everything whith the README configure options for wxGTK

Sad
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: CPU high usage due to always hashing and rehashing shared
« Reply #5 on: November 19, 2003, 05:16:04 PM »

How many files do you share?
Logged

Guest

  • Guest
Re: CPU high usage due to always hashing and rehashing shared
« Reply #6 on: November 19, 2003, 05:21:58 PM »

Not so much in number of files (nearly 250) but in Size, this make nearly 40Go

Sad
Logged

Guest

  • Guest
Re: CPU high usage due to always hashing and rehashing shared
« Reply #7 on: November 19, 2003, 05:53:48 PM »

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
Logged

Guest

  • Guest
Re: CPU high usage due to always hashing and rehashing shared
« Reply #8 on: November 19, 2003, 06:14:14 PM »

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
Logged

Guest

  • Guest
Re: CPU high usage due to always hashing and rehashing shared
« Reply #9 on: November 20, 2003, 07:20:23 AM »

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
Logged

Guest

  • Guest
Re: CPU high usage due to always hashing and rehashing shared
« Reply #10 on: November 20, 2003, 07:49:16 AM »

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
Logged

Guest

  • Guest
Re: CPU high usage due to always hashing and rehashing shared
« Reply #11 on: November 20, 2003, 08:08:36 AM »

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
Logged

romv

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 20
Re: CPU high usage due to always hashing and rehashing shared
« Reply #12 on: November 20, 2003, 02:56:14 PM »

Logged

romv

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 20
Re: CPU high usage due to always hashing and rehashing shared
« Reply #13 on: November 20, 2003, 02:59:40 PM »

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 ?
Logged

Guest

  • Guest
Re: CPU high usage due to always hashing and rehashing shared
« Reply #14 on: November 20, 2003, 06:45:09 PM »

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
Logged
Pages: [1] 2