Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[SunX]

HELP !

I try to make amule work but it's very hard. It's a shame cause when it works, it brings me some rare files. Maybe that's why I try hard to make it work.

I have to say I had the same problem with 2.0.3 version. I was so much annoyed, I stoped using amule for a few months. When the 2.1.0 came up, I got some new hope.
I first trashed the known and known2 files.

Actually I was sharing 6000 files and it was too much I think, cause amule was getting stuck for a few days, hashing every file at every start, rewriting the known.met file. So I gave up and now, I share only 150 files. Anyway, amule takes at least 20 minutes to start.

OK, I use a G3 400Mhz 1Gb RAM. I can't buy anything better for now (and maybe that's why I use P2P...).
And if the CPU is the problem, why isn't there any "minimum requirement" for amule? Or at least some advice about the number of shared files?


Anyway, my problem is that when amule has finally finished starting, the log is finally displayed and I can get the hand. But if I don't go fast, the color wheel starts spinning and I have to wait a few seconds before getting the hand back. But only for seconds and my mouse clicks don't have any effect, or very rarely, and the wheel restart its spinning for a few seconds. etc...

Meanwhile, I can see some amule files (in the library/applications support/amule folder) are modified. The log file from time to time. But the more recent changes are for the amule.conf.
Why? I didn't change the settings and I'm not even connected. Why my CPU is so much used for the conf file?

NB. I set amule to do these at startup :
- not searching a new version
- not searching the last ipfilter
- not connecting to a server
What's the point to do these if the app isn't finished working and taking a lot of my CPU already?

Finally, amule gets completely stuck, the color wheel spinning all the time.
I have to force quit.
Note: When amule is on (2.0.3 or 2.1.0), even when it isn't stuck, its icon in the dock isn't the same as the original. It's a little donkey surrounded by black concentric squares. When I force quit, this wrong icon disappears and is replaced by the original for a few seconds. Then, the app quits.

Any ideas, advices or suggestions would be welcome and really appreciated !
I already read the FAQ (english and french versions) but it was 2 months ago. Maybe there are some big changes?

Thanks for reading the whole text.

[lionel77]

Originally posted by SunX
Actually I was sharing 6000 files and it was too much I think, cause amule was getting stuck for a few days, hashing every file at every start, rewriting the known.met file. So I gave up and now, I share only 150 files. Anyway, amule takes at least 20 minutes to start.

OK, I use a G3 400Mhz 1Gb RAM. I can't buy anything better for now (and maybe that's why I use P2P...).
And if the CPU is the problem, why isn't there any "minimum requirement" for amule? Or at least some advice about the number of shared files?

Boy, sharing 6000 files with an ed2k client is insane!
Seriously, the edonkey network is designed for sharing a smaller number of larger files rather than thousands of smaller files.
Given your relatively slow CPU you might even want to limit yourself to a smaller number than 150. It's hard to give specific recommendations for the max number of files you should be sharing or downloading because the load produced really depends to a large degree on the popularity of a file. For instance, with a rare file you might have 10 clients asking for it and with a popular file it's 500.

Anyway, my problem is that when amule has finally finished starting, the log is finally displayed and I can get the hand. But if I don't go fast, the color wheel starts spinning and I have to wait a few seconds before getting the hand back. But only for seconds and my mouse clicks don't have any effect, or very rarely, and the wheel restart its spinning for a few seconds. etc...

Meanwhile, I can see some amule files (in the library/applications support/amule folder) are modified. The log file from time to time. But the more recent changes are for the amule.conf.
Why? I didn't change the settings and I'm not even connected. Why my CPU is so much used for the conf file?

It is possible that there is so much load on the cpu because aMule needs to hash all your shared files. This has to happen only once per shared file but if not all files have been hashed then aMule starts to hash the remaining ones right after startup.
So why don't you try to start aMule without any shared files to see if the app is more snappier then. If it is, it means that your previous slowdowns were a consequence of aMule hashing shared files after startup. You would then want to add the files you want to share to your shared folder in chunks of 10 files or so at a time. And after you do that, I would not touch aMule until the files are hashed.

Good luck and let us know how it goes.

[ken]

Originally posted by SunX
Note: When amule is on (2.0.3 or 2.1.0), even when it isn't stuck, its icon in the dock isn't the same as the original. It's a little donkey surrounded by black concentric squares. When I force quit, this wrong icon disappears and is replaced by the original for a few seconds. Then, the app quits.

Turn off Tray Icon support in aMule's preferences.  You can do it through aMule's preferences dialog, or edit ~/Library/Application Support/aMule/amule.conf and set EnableTrayIcon to 0.

Your other problems might be related to poorly-configured preference settings, too.

You might try going into ~/Library/Application Support and renaming the aMule folder to something else, at least temporarily.  Then start aMule and see if it behaves better.

[SunX]

Thanks a lot for your contribution Lionel77 !  I've learned a lot.

Originally posted by lionel77
Boy, sharing 6000 files with an ed2k client is insane!
Seriously, the edonkey network is designed for sharing a smaller number of larger files rather than thousands of smaller files.
Given your relatively slow CPU you might even want to limit yourself to a smaller number than 150. It's hard to give specific recommendations for the max number of files you should be sharing or downloading because the load produced really depends to a large degree on the popularity of a file. For instance, with a rare file you might have 10 clients asking for it and with a popular file it's 500.

I didn't know ed2k wasn't meant to share a lot of files. I know it's less necessary because of the hashing system.
Isn't it a way to make the rare files even more rare? Cause people tend to share the same kind of files.

I suppose I don't care for the number of clients queuing for one file : I've set the upload limit way under my maximum bandwith.

Originally posted by lionel77
It is possible that there is so much load on the cpu because aMule needs to hash all your shared files. This has to happen only once per shared file but if not all files have been hashed then aMule starts to hash the remaining ones right after startup.
So why don't you try to start aMule without any shared files to see if the app is more snappier then. If it is, it means that your previous slowdowns were a consequence of aMule hashing shared files after startup. You would then want to add the files you want to share to your shared folder in chunks of 10 files or so at a time. And after you do that, I would not touch aMule until the files are hashed.

Good luck and let us know how it goes.

That's what I did when I gave up with the 6000 files. I started with 0, then 50, then 150.
Maybe I should start over and take more time to analyse the behaviour of amule with 10 files.

Since I created this thread, I noticed my hard drive was really fragmented. I used Techtool Pro 4 to defragment it, but I didn't have the opportunity to use amule since then. I'll try to give you feedback.

Thanks again.

[SunX]

Originally posted by ken
Turn off Tray Icon support in aMule's preferences.  You can do it through aMule's preferences dialog, or edit ~/Library/Application Support/aMule/amule.conf and set EnableTrayIcon to 0.

Your other problems might be related to poorly-configured preference settings, too.

You might try going into ~/Library/Application Support and renaming the aMule folder to something else, at least temporarily.  Then start aMule and see if it behaves better.

Thanks ken for the tips.
I'll change the icon setting next time I launch amule.

I had thought of restarting amule from scratch when 2.1.0 went out. But I wanted to try it, keeping my settings, so I only trashed the known.met files.
Maybe I'll do that if it keeps being sluggish.