All,
I used to write pieces of code for emule some time ago (almost like 2 years, and under a different nickname), but I had to leave the scene for professional reasons. I only recently moved over to a *nix solution here @ home (my old pc gracefully promoted to firewall/gateway). Now, I am a bit disappointed by the performance I get out of it, albeit that might be due to more heavy serverloads (notable razorback2), server policies, and the sheer complexity of clients.
I installed both amule (rc5) and mldonkey (latest cvs) on the system and compiled it with default options. both programs are setuid to a mldonkey user which I use to tag packets using iptables and traffic shape afterwards (so same bandwidth allocation). I let both programs run (but not together) for a few days I came to the conclusion that
- aMule is much faster then mldonkey
- aMule is more bandwidth efficient, that is, less "overloading" its traffic class
- aMule is more CPU hungry
Nevertheless, the result is mediocre. I get an average dl of 8kB/s (the line spec is 3.3Mbit/192Kbit), upload is set at 5kB/s. pretty low, and it will take days-weeks to get specific files. to compare, I used to run eMule on a machine that was on a 10BaseT switch very "close" to a non-firewalled 155Mbit/s pipe to the internet, and basically my dl was capped by the local ethernet, making me achieve dl rates 300-450kB/s, whilst uploading maybe 50kB/s. I expected to get more out of the dsl line at home.
It makes me wonder if anyone tried to run a recent eMule within a VmWare virtual machine on linux and compare this to the *nix solutions?
B
