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: Very big files make amule very unresponsive  (Read 8880 times)

reise

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 28
Re: Very big files make amule very unresponsive
« Reply #15 on: July 02, 2007, 11:12:31 PM »

amuled (2007-05-21) running on a ext3 filesystem. Do you think it could be a filesystem issue?

Is there a possibility to track the issue down with gdb? Any commands I should use?
Me too, but i'm running cvs 2007-07-02.
Logged

reise

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 28
Re: Very big files make amule very unresponsive
« Reply #16 on: July 03, 2007, 10:50:15 PM »

I inserted my gdb output in here, hope it helps.
Is there a way to be sure that my amuled was compiled with debug?
Logged

reise

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 28
Re: Very big files make amule very unresponsive
« Reply #17 on: July 08, 2007, 01:09:59 AM »

No one?
This problem is very anoying... :(
Logged

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
Re: Very big files make amule very unresponsive
« Reply #18 on: July 08, 2007, 08:31:54 AM »

It is very hard to solve a problem you can't reproduce and you don't know what it is causing.
Frankly, I have never used a profiler, but this would be my tool of choice for further research.
Logged

reise

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 28
Re: Very big files make amule very unresponsive
« Reply #19 on: July 08, 2007, 11:16:32 PM »

I know how to program but I'm not very familiar with the linux environment. Can you give me hints on what/how can I do to track the place where the amuled is consuming all the processor?
Logged

reise

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 28
Re: Very big files make amule very unresponsive
« Reply #20 on: July 12, 2007, 12:13:12 AM »

I'm using aMule-CVS-20070710.tar.bz2 and it seems that the problem is somewhat fixed.
Amuled still jumps in %CPU between 30 and 80% but it's now possible to use amulecmd to add files and control the daemon.

I don't know what changed in this last days but is now a lot better. Someone with better knowledge of the cvs can do a diff list of this version with the one from aMule-CVS-20070702.tar.bz2?
Or tell me how can I compare all the files and see the diffs?
Thanks
Logged

skolnick

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 24
  • Offline Offline
  • Posts: 1188
  • CentOS 6 User
Re: Very big files make amule very unresponsive
« Reply #21 on: July 12, 2007, 12:24:53 AM »

Or tell me how can I compare all the files and see the diffs?
Thanks
Download both files, uncompress them to separate folders, and use the diff command to view the differences. Use something like this:

Code: [Select]
diff -ur <oldCVSfolder> <newCVSfolder>
Regards.
Logged

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
Re: Very big files make amule very unresponsive
« Reply #22 on: July 12, 2007, 05:41:43 AM »

There were only little changes and probably not related changes: (I hope I didn't forget anything)
- fixed building against external libcrypto
- fixed UPnP library unloading
- fixed Ctrl+A in mulelistctrl
- replaced flex / lex by $(LEX) in Makefile.am files
Logged

reise

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 28
Re: Very big files make amule very unresponsive
« Reply #23 on: July 12, 2007, 11:34:29 AM »

Nothing that should impact, but the true is that now the machine is usable even when downloading big files.
Logged

reise

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 28
Re: Very big files make amule very unresponsive
« Reply #24 on: July 12, 2007, 08:57:18 PM »

Correction: If I put the BCF847313425002ED602CA8E931C15E4 file downloading it still uses 100% cpu. I have another big file in the list confused me.

It's possible to use some debugger or profiler to see if I can find where it is using the processor?
Logged
Pages: 1 [2]