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 10351 times)

Guest

  • Guest
Re: CPU high usage due to always hashing and rehashing shared
« Reply #15 on: December 01, 2003, 03:01:41 AM »
still, anyone worked out why the CPU usage on aMule is so massive ?
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 #16 on: December 01, 2003, 06:40:18 AM »
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.
Logged

superstoned

  • Jr. Member
  • **
  • Karma: 0
  • Offline Offline
  • Posts: 80
Re: CPU high usage due to always hashing and rehashing shared
« Reply #17 on: December 01, 2003, 12:54:19 PM »
hmmmm, sounds good... 1.2.0 is the first release which doesnt work for me, so I hope 1.2.1 fixes that ;-)
Logged

knecht666

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 24
    • http://knecht.homelinux.net
aMule 1.2.1
« Reply #18 on: December 02, 2003, 06:34:40 PM »
I am full of desire . . . thanks for good work

Sebastian
Logged
---------------------------------------
fiat veritas pereat mundus

madman

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2
Re: CPU high usage due to always hashing and rehashing shared
« Reply #19 on: January 03, 2004, 07:19:01 PM »
Quote
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...
Logged
Pages: 1 [2]
« previous next »