Another pet peeve bites the dust.

It turns out that MLDonkey works fine.
Several have complained of slow download rates with this software, but has anyone bothered to check the default settings?
I did and it shocked me. The damn thing was set to 10k per sec!!!
OMG!

I have 50mbit internet so I bumped the settings up and it now acts like a normal P2P program!

Check your max rate settings.

I'm sure there are quite some old threads on that

But here's a new tip: increase MBUF_CONF MAXMEM to 16384 in Prefs/Env-Archive/sys/net/NetStack.config (default setting might lead to MLDonkey crashing).

Without searching through all the old threads on the subject, is there a reason the default settings are set up the way they are and must be changed to run it optimally? Is it documented in the readme for MLDonkey?

I could never get the thing to work anyway

Thanks bash64, stevo,
I'll have to re-examine this program. I couldn't get it working either.

@Steveo

Memory reserved for mbufs should be dependent on the number of open connections and the size of the receive window. If the MorphOS stack supports window scaling, the size can vary. The number of connections varies, obviously, so we make a good guess at a maximum.

@bash64

I don't have MorphOS running at the moment, but assuming a default receive window size of 32768 bytes and no window scaling, you'd need latency below ~5 ms to achieve 50 Mbps. Of course, the magic of most P2P protocols allows you to aggregate many slower connections.

I've not had any issue getting it to work.
When I had an efika it simply ran too slow so I gave up on it.
Once installed you just run it, wait for it to say "core started" and then open a web browser to:
http://127.0.0.1:4080

You all know you have to install the MorphOS SDK to use MLDonkey, right?

@bash

You don't have to...but it helps

@amigadave et al

Most stuff is explained (quite clearly) in the readme (Read Me!) supplied with the archive. If you still can't get it to work, please post specific probs and I'm sure we'll figure it out

[ Edited by Stevo on 2010/12/15 23:28 ]

I have the netstack.config set as described above, and the max download rate set to 150.
Still I never had any good performance with this client.
Adding a new torrent usually ends up it starts with a few kb/s and counts upwards, but after a while it slows down to zero.
Copying the same torrent file to the OSX side of the MacMini makes the torrent usually download in full speed.

I experienced anywhere from 60k per second to 100k+ per second, but mostly about 60k/sec.
I think you can pass it a torrent. I just searched for torrents and selected from what mldonkey found.

I wonder if it could it be something with the port setting.
I know for the windows client it seem to be critical that the port for incoming connections is open. I think this is the only port settings you normally use in uTorrent.
But in MLDonkey webinteface - settings - ports, there is no port settings for incoming connections.
Does it use a default port for this, that might be closed on my router?

EDIT: Found it in the bittorrent.ini settings file. Seems to be port 6882 here, I will test it.

[ Edited by amyren on 2011/1/3 13:16 ]

It now works!
First I forwarded the ports 6881 and 6882 in my router, and it started to download more stable, but not so fast. I got a peak at 37 KB/s, then it settled for 19 KB/s.

Then something strange, I had hard download set to 150 KB/s and 25 for upload. Just to see if anything happened, I changed them to 180 and 30, and suddenly my download rate jumped to 156 KB/s - and stayed there. It was like my previous setting of 150 wasnt applied properly before.
Now I hope that this will be the way MLDonkey will operate from now on, everytime :)