Print

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

[KenD]

Having migrated from PC to Mac, I'm trying to get aMule (the latest CVS from the front page) up and running, but I'm having real problems with network speed (please don't give up on me after reading that - I know everyone moans about speed problems, but read on ...  :] )

I get a HighID no problem - firewall is configured correctly, I'm convinced of that, as my Mac is on the same (private) IP address that the PC used to be. aMule starts fine, connects fine, and even downloads fine, but I'm getting very poor performance - 7-10k/s if I'm lucky. eMule on the PC used to get 100-150k/s on high-availability files.

I've turned on verbose logging, and I've noticed more than a few errors. Here's a sample:

1/24/04 11:02:41: Client 'bbear [ePlus]' (IP:82.2.27.11) caused a socket blocking error. Retries: 0. Trying to reconnect... (retries left: 2)
11/24/04 11:02:41: Client 'Richard Gere' (IP:80.186.18.214) caused a socket blocking error. Retries: 0. Trying to reconnect... (retries left: 2)
11/24/04 11:02:41: An unnamed client (IP:81.133.245.149) caused a socket blocking error. Retries: 0. Trying to reconnect... (retries left: 2)
11/24/04 11:02:42: Client 'Dragon' (IP:172.203.21.4) caused a socket blocking error. Retries: 0. Trying to reconnect... (retries left: 2)
11/24/04 11:02:42: Client 'http://emule-project.net' (IP:82.16.120.58 ) caused a socket blocking error. Retries: 0. Trying to reconnect... (retries left: 2)
11/24/04 11:02:43: Packet received from 81.86.249.182
11/24/04 11:02:43: SUIS: IS_KEYANDSIGNEEDED
11/24/04 11:02:43: YO happened for client: darklight
11/24/04 11:02:43: An unnamed client (IP:81.133.245.149) caused a socket blocking error. Retries: 0. Trying to reconnect... (retries left: 2)
11/24/04 11:02:43: Packet received from 24.163.46.121
11/24/04 11:02:44: Packet received from 81.86.249.182
11/24/04 11:02:44: Packet received from 24.163.46.121
11/24/04 11:02:44: Packet received from 83.73.94.223
11/24/04 11:02:44: Packet received from 82.35.138.211
11/24/04 11:02:44: Packet received from 83.73.94.223
11/24/04 11:02:44: An unnamed client (IP:81.133.245.149) caused a socket blocking error. Retries: 0. Trying to reconnect... (retries left: 2)
11/24/04 11:02:44: Client 'http://www.aMule.org' (IP:62.57.202.147) caused a socket blocking error. Retries: 0. Trying to reconnect... (retries left: 2)
11/24/04 11:02:44: Packet received from 81.86.249.182
11/24/04 11:02:45: Client 'BingLiu [JackTL] [ARC]' (IP:85.76.70.239) caused a socket blocking error. Retries: 0. Trying to reconnect... (retries left: 2)
11/24/04 11:02:45: Packet received from 81.86.249.182
11/24/04 11:02:45: Packet received from 213.73.128.188
11/24/04 11:02:45: Packet received from 81.86.249.182
11/24/04 11:02:45: Packet received from 81.86.249.182

Are these normal errors, or do the continual "socket blocking" messages explain why my downloads aren't ramping up?

Settings: Download 150kB/s, Upload 15kB/s, Slot Allocation 3kB/s. Running on port 5563, 20 new connections / 5 secs.

[skolnick]

You seem to have the verbose log enabled. Disable it, as some of it messages look really serious, when in fact are just info for the developers. Regarding your speed problem, I just ask if your upload speed is contiuous, or if it goes up and down. Also, if continuous, it just reaches the max you specify? you get disconnected from the server frequently, or never?

Regards.

[KenD]

I'd turned on verbose logging deliberately - I knew something was up, so I figured it was the best place to start.

My upload speed is limited to 15k/s, and it stays pretty constant at that. I only rarely get disconnected from servers; certainly no more often that I did with eMule.

You say the messages are serious; any idea what's causing them and (more importantly) how to fix them?  ;(

[skolnick]

hi!

no, I never meant to say your messages were serious. I meant that the log sometimes throws messages which, for untrained eyes, may look serious, but in fact are not. I just said that the best way to live happy with amule (also with emule) is disable the verbose log. It will give lots of confusing information (for normal users, this info is worthy for developers) and messages may be misunderstood.  But your amule seems to be working normally...uplolad is OK, and your connection seems OK.  Can you post your amule settings please?

Regards.

[KenD]

OK - just that snippet of log showed lots of "socket blocked" messages, and that was only over 3 seconds  ;(

Not sure how many of my setting you need, so here's what I think is relevant:

Connection:

Download 150 kB/s
Upload 15kB/s
Slot Allocation 3 kb?s

Line Capacities:
Download 250 kB/s
Upload 32kB/s

Client TCP port 5663
Client UDP port 4672

Max Sources per File
Hard Limit 500
Connection Limits 800

Core tweaks:
Max connections / 5 secs 20

File buffer size 224000
Upload queue size 5000
Server connection refresh interval Disabled


Nothing else has been changed/touched, apart from shared files.

Current upload:download ratio is 7:1
No sign of max'ing out connections.

Anything else relevant I can give you?

[skolnick]

Only thing I see, is that your max connections is pretty high. use a lower value (250 works for me) and try again. Maybe you are overstressing your connection, and that makes you unable to download.

Regards.

[KenD]

Ran aMule overnight with 250 max connections, but it still struggled to get to 10k/s.

Could you do me a favour - enable verbose logging for a minute or so, and see if you get the "socket blocked" messages in your log? I get several every other second...

[Jacobo221]

yes it is normal. i have them a lot and everybody has them a lot. It's the connection line that's been roken. either the client disconneced or it was closed or it's connection went down, or....

aMule connects to hundreds of clietns every second. it gets a list of clients with the files you want to download/upload between the time it gets the list and the time it tries to conect to them, there's a lag, and in tht lag (which might be up to several large seconds), sometimes connection is broken with that client. having three disconnectiosn per second when connecting to hundreds of clietns each second, is not much. Anyway tehre's nothing that can be done about that. ppl are free to close their ed2k client or internet connectino whenever they feel like

Greetings!

[KenD]

Damn those other users  

Just for kicks, I fired up my old PC (on a seperate public IP, going through the same router) and tried to use eMule to download 5 of the files I'm trying to grab from a aMule. Within 15 minutes or so I was getting 50-80k/s, and it's still going strong. Both PC and Mac have pretty much the same settings, with a similar number of files shared out and using the same DSL connection.

I know there's nothing I can really do, and I'm not blaming aMule, but can anyone think of a reason why I'm seeing great performance with eMule and not aMule? I thought credits might have something to do with it in part, but both devices are now on different clientids...

BTW, I get the same problem with mlNet  

[Jacobo221]

aMule and eMule use the same network code since aMule ports it into linux/mac. So, i have no idea why you're experiencing such a difference :-/

[GonoszTopi]

I thought credits might have something to do with it in part, but both devices are now on different clientids...

You might be right, (considering aMule and mlNet has the same problem), if you used that eMule installation a lot before, so it could earn credits. Btw, credits have nothing to do with client ID, they are given to userhashes.
So, to keep old credits you earned, copy preferences.dat to ~/.aMule, and to keep old credits *others* have, copy clients.met aswell.

I hope this can solve your problem, and I also hope I was right in what I said :rolleyes: