aMule Forum
English => en_Bugs => Topic started by: benjaprud on June 27, 2006, 02:37:17 AM
-
Hi all !
I used MLdonkey for quite a long time now and I tried aMule for the first time a few months ago... It was version 2.1.0 on MacOS X.4.3... When I launched it, the icon bounced in the Dock during one minute before it told me "It's the first time you launch aMule, etc...". The interface was extremely slow and it was absolutely unusable... I gave up using aMule and thought I'll give it another try later...
Yesterday I saw there was a new 2.1.3 version so I tried it (on OS X.4.6), hoping that the bug would be corrected, but it's the same... Everything is extremely slow... I tried compiling amule 2.1.0 from source with Fink but the problem remains... I searched the forum to see if anybody have had that bug before but I haven't found anything...
So if anybody here has an idea on how to make it work properly or to help me reporting the bug to the dev team, that would be great... I joined my logfile for those who can read it...
Thanks...
-
Hi benjaprud!
Do you use any other applications which consume a lot of CPU like SETI@home? Please try to start aMule without any other applications in background and tell us whether it works smooth then.
Salut
-
Ah, I'm using dnetc... I'll try without but if the problem comes from dnetc, I'll continue using MLdonkey... Perhaps if I raise the priority of aMule it'll work better ?
Thanks for your help...
-
what about your i/o wait? is it maybe high or smth alike?
in linux htere is a util called "top" to see what consumes cpu times, and also how high the i/o wait is...
-
Yeah, there is top on OSX too but I don't know about how reading the i/o wait... However there shouldn't be any problem with it, all applications run smooth and amule is the only one having this problem...
I haven't tried without dnetc yet... I'll tell you when it'll be done...
-
aMule works well without dnetc running in the background... That's the only application i know that cannot run properly with dnetc, what's the problem with aMule ? dnetc priority is 0, is there a way to make them run together ? Perhaps with the renice command ?
-
As you already posted in the other thread about that problem, please annoy the Mac-guys there to find a solution. ;)
I hope you can give them some more information to solve this problem.
-
Ok, but as dnetc and aMule are both multiplatform and linux users are more geeky and more keen on the command line, I hope more answers on this thread that on the other... Mac users seems to be silent for now...
-
We don't have Mac users only, but also Mac developers, maybe they can help (If you're lucky and they have time) ;)
-
The problem is (afaik) Mac-only thus we need the Mac-guys for help. ;)
-
Well, it's good to know that aMule works well when dnetc is not running. I would try renicing dnetc:
In the Terminal, do "ps aux | grep dnetc". You should see something like:
myUser 1341 9.1 -6.3 514080 131280 ?? S Sat03AM 67:24.67 /somePath/dnetc
The first number (here: 1341) is the process id (pid) of the app.
Then type "renice 10 1341" (where 1341 is the pid of dnetc that you figured out in the previous step). This will lower dnetc's priority from 0 to 10 (-20 is max priority and 20 in min priority in renice). See if that helps.
-
Sorry, i didn't know much about priorities before trying to renice aMule... dnetc priority is 20 not 0, so i tried renicing aMule to -20 (using BeNicer (http://www.versiontracker.com/dyn/moreinfo/macosx/16534))... The result is little better (sometimes the spinning wheel disapears) but it's still very slow...
dnetc and aMule can work at the same time on linux ? I've got a Debian dual-boot, I'll give it a try tomorrow...