Print

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

[Mr Faber]

After exactly 2 days my connection limit was reached and never goes down again so I decided to compile the new CVS aMule and not the daemon.
The connection seems after over 13 hours stable but this has nothing to say since the daemon acts equal at this time. But I found another interesting thing.
With the daemon I have had only and average upload time of 10-20 mins in most cases (I have made no long tests so it may only happens some times). With normal aMule I have 41:30 minutes which seems quite stable. The total failed upload sessions are with 13 very low vs 225 total successful upload sessions.

cu
Mr Faber

[lfroen]

Please test following patch to amule cvs code. I would like to know if it changes things.

[Xaignar]

Code: [Select]

+ if ( idle_count > 360000 ) {Shouldn't the 360000 be 12000, otherwise you'll wait for 360000 * 50ms, which would be 300 minutes, whereas 12000 * 50ms is 10 minutes exactly.

[lfroen]

Point taken. Patch corrected.

Code: [Select]

if ( m_socket->WaitForRead(0, 100) ) {
if ( m_socket->RecievePending() ) {
Sleep(50);
idle_count++;
This will take from 50 to 150 ms depending how match time WaitForRead took. So, 10000 translates to range 10000*(50ms ... 150ms) => 500sec ... 1500sec. I think it's enough time.

[Mr Faber]

Is this patch for aMuled or aMule? At first I will check aMule for at least 2 days to confirm that this has something to do with the daemon and not the monlith.

cu
Mr Faber

[lfroen]

Patch have nothing to do with monolitic amule. It affects only daemon code.

[Mr Faber]

Since aMule crashes without user interaction I can't confirm definatly that aMule hasn't the problem but after over 20 hours the connection graph was still stable.
After that I have downloaded CVS 20050508 and compiled the daemon with your patch.

cu
Mr Faber

[yoyoio]

I can confirm that aMule hasn't the problem.

Now, I have compiled amule & amuled with wxGTK 2.6, amule is very stable and works very fine, but amuled don't upload neither donwload anything, or only 1 client uploading a few seconds a few bytes and nobody in queue.

amule: active connections 60 more or less.

aMule CVS using wxGTK2 v2.6.0 (Unicoded) (Snapshot: Sat May  7 07:01:19 CEST 2005) (OS: Linux)

aMule Daemon CVS using wxGTK2 v2.6.0 (Unicoded) (Snapshot: Sat May  7 07:01:19 CEST 2005) (OS: Linux)

[BeFalou]

amuled is unable to run for a long time, it crashes, so I can't reproduce this. I've posted the BT here: http://forum.amule.org/thread.php?threadid=6080&sid=

It's with today's CVS and lfroen's patch.

[BeFalou]

I'm sorry to say that the patch is not working. The image attached is the connection graph after 1D 3h. It hasn't reached the top yet but it's a lot more compared to amule monolithic graphs (posted before).

[lfroen]

Hmmmm ... I will check uploading code as well, but this code is shared between amule and amuled, so I would be very surprized to find a difference

[BeFalou]

Another point that makes me think it is an upload thing is that all established connections are from my amuled port to others, while when we download from others this connections are made with other ports.

Maybe this thinking is stupid but I had to say it  :rolleyes:

[lfroen]

amuled network code has been reworked. Please feel free to test cvs versions !

[Kry - Edit (fill free?)]

[BeFalou]

Thanks for the hard work, but by now I can't test it for long, it crashes. BT -> http://forum.amule.org/thread.php?threadid=6347&sid=

Regards.