Print

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

[RRM]

Would you like to test sweet aMule on XP for comparison? 

Of course.
Will try to do that when i come back from work.

[RRM]

Phew, hashing 700 GB always takes a long time,
isnt there a shortcut?
like copying and pasting a file from aMule/eMule under WinE/Ubuntu to this new aMule (under XP)?

[Stu Redman]

Running aMule using eMule's known.met should do the trick.

[RRM]

Running aMule using eMule's known.met should do the trick.

Great, but how do i do that?
I found a known.met file in eMule/config/
,but where to copy & paste it to, because i cannot find a config folder in aMule...

[skolnick]

Hi!

aMule's folder should be in /home/<username>/.aMule folder under linux/UNIX. Under Windows XP I would hope the path to be c:\documents and settings\<username>\local settings\.aMule or something similar. No idea about OS X so I better shut up there

Regards.

[GonoszTopi]

aMule's folder should be in /home/<username>/.aMule folder under linux/UNIX. Under Windows XP I would hope the path to be c:\documents and settings\<username>\local settings\.aMule or something similar. No idea about OS X so I better shut up there

http://wiki.amule.org/index.php/Getting_Started#Where_Are_The_Files.3F

[RRM]

Thank you for your help,
but i still cannot find it in XP....
Luckily im done hashing.

[RRM]

Hey, i didnt expect this...
XP/aMule didnt start up as fast as Ubuntu/aMule or WinE/eMule,
but faster than XP/eMule, and...
after a while it actually starts running almost equally fast as those fast 2!!

Ofcourse, the "waited" is screwed,
and clients get reallocated after every 10MB (despite 0 clients in queue)
but now im really curious as to if/how fast it will crash....

[RRM]

Anyone any idea as to how i can trace memory consumption under XP?

[GonoszTopi]

IIRC the Task Manager can tell you memory usage.

[RRM]

Thank you!
XP/aMule is still running, and apparently,
there is no memory leak here.

XP/aMule runs smoothly, but utilizes about 90% of total uploadcapacity.
So, a little less effectively then Ubuntu/aMule and WinE/eMule,
but much better than XP/eMule.
I will test XP/eMule once again; maybe there was something else going on.

[RRM]

  hmmm
Yes, there was something else going on, coincidentally,
because this time XP/eMule did perform well;
almost as good as XP/aMule.
It starts up a little slower, and eventually maximally utilizes about 80% of my total uploadcapacity.

So, my end results are:
Ubuntu/aMule 100%
WinE/eMule 100%
XP/aMule 90%
XP/eMule 80%

Im curious whether other people have similar results.

[Stu Redman]

XP/aMule is still running, and apparently, there is no memory leak here.

Funny. So it's probably the Unix version of wx's networking code, everything else doesn't show the problem. However, there have been reports from eMule users of less memory consumption with the patch too.

this time XP/eMule did perform well

Yeah, measuring performance in the mule network can sometimes be a bitch. 

Some Support (eMule dev) has found an explanation what was the intention behind the botched line of code:

Code: [Select]

Index: EMSocket.cpp
===================================================================
--- EMSocket.cpp (revision 9905)
+++ EMSocket.cpp (working copy)
@@ -527,7 +527,8 @@
     uint32 sentStandardPacketBytesThisCall = 0;
     uint32 sentControlPacketBytesThisCall = 0;
 
-    if(byConnected == ES_CONNECTED && IsEncryptionLayerReady() && !(m_bBusy && onlyAllowedToSendControlPacket)) {
+    if(byConnected == ES_CONNECTED && IsEncryptionLayerReady() && (!m_bBusy || onlyAllowedToSendControlPacket)) {
 
  //printf("* Internal attemptto send on %p\n", this);So the busy logic is disabled for control packets instead of data packets. Now that would make sense. RRM, can you try this out (on Linux)?

[RRM]

RRM, can you try this out (on Linux)?

Sure.
So, on line 531 in the EMSocket.cpp
, i have to replace this:

Code: [Select]

if(byConnected == ES_CONNECTED && IsEncryptionLayerReady() && !m_bBusy) {
by this:

Code: [Select]

if(byConnected == ES_CONNECTED && IsEncryptionLayerReady() && (!m_bBusy || onlyAllowedToSendControlPacket)) {

right?
and then configure and make.
Im running it now... (rev. 9928, because i called git first)

[GonoszTopi]

RRM, you're learning fast.

But beware, after getting used to the taste of bleeding-edge, you won't be able to go without it ... it's addictive