The initial purpose of this project was to provide an aMule repository (including dependencies) that is ready to build and update the dependent libraries when possible. This branch specifically focuses on providing a build that is better suited to address nowadays file sizes and broadband availability. Default hard-coded parameters of aMule were better suited for small-files/slow-connections, leading to very low per-client transfer rates by nowadays standards.
The focus here is to maximise throughput for broadband users, to optimize seeding.
The focus is as well to introduce the least amount of changes to preserve the original quality and stability of the client.

tags:

• arm64
• amd64

https://hub.docker.com/r/mercu/builder-amule

Docker for build: https://github.com/mercu01/docker-amule-broadband

The upload slot algorithm is broken. Amule generates infinite upload slots, each slot of a few kb/s.

Amule does not get credits, the download is penalized.

• Feature: Alternative Rate Limits, more info

• Feature: Advanced Upload Manager, more info

• Fix Default upload rate = 0 for broadband branch, 1 slot = 1 mb/s upload rate

• Fix Slot Allocation = upload slots (min 5 slots, recomended: 10/20)
• The client upload has 200 shipments with warning (< 50kb/s), before removing it from the queue, 200 shipments = 1 minute
• Infinite POWERSHARE Clients
• Zip compression disabled (Reduce CPU usage)
• Change size upload package: from 10 kilobytes to 100 kilobytes (Reduce number loops to upload)

• Configure 20 slots allocation, (1 slot = 500 Kb's, 20 slots = 10 Mb's approximate)
• Max upload 10000
• Max download 0

• Configure 20 slots allocation, (1 slot = 500 Kb's, 20 slots = 10 Mb's approximate)
• Max upload 0
• Max download 0

The system will handle the slots, you'll get a steady load. If your load queue is big, the system will kick slow client. When everyone is fast, it will be deactivated

Basically, we will try to find the maximum upload depending on the amount of clients that are waiting.

• SOFT KICK Example: 10 upload slots and >10 waiting in queue: kick slow clients, but slowly. (1 kick every 1 min) *(I don't have many customers waiting, I can run out of customers in the queue)

• HARD KICK Example: 10 upload slots and >30 waiting in queue: kick slow clients, but more aggressive. (1 kick every 30s) *(I can afford to look for quality clients)

• Very few customers in the queue, Example: 10 upload slots and <10 waiting in queue: none, no kick clients *(this state occurs at night)
• The total speed is over than 85%.
• The slowest client is not very slow, at least 75% compared to the fastest client.
• New clients, they can't be kicked. (It is considered a new client, when it takes less than 1 minute).
• New clients is over 25% of the slots

Schedule the use of alternative rate limits

• itlezy/eMule

aMule is an eMule-like client for the eDonkey and Kademlia networks.

Forum | Wiki | FAQ

aMule is a multi-platform client for the ED2K file sharing network and based on the windows client eMule. aMule started in August 2003, as a fork of xMule, which is a fork of lMule.

aMule currently supports Linux, FreeBSD, OpenBSD, Windows, MacOS X and X-Box on both 32 and 64 bit computers.

aMule is intended to be as user friendly and feature rich as eMule and to remain faithful to the look and feel of eMule so users familiar with either aMule or eMule will be able switch between the two easily.

Since aMule is based upon the eMule codebase, new features in eMule tend to find their way into aMule soon after their inclusion into eMule so users of aMule can expect to ride the cutting-edge of ED2k clients.

• an all-in-one app called amule.
• a daemon app called amuled. It's amule but with no interface.
• a client for the server called amulegui to connect to a local or distant amuled.
• amuleweb to access amule from a web browser.
• amulecmd to access amule from the command line.

In general, compiling aMule should be as easy as running configure and make. There are detailed instructions on the wiki for compiling on a number of different platforms, though they may be outdated a bit... (updates are welcome).

aMule comes with reasonable default settings and should be usable as-is. However, to receive a HighID you need to open aMule's ports on your firewall and/or forward them on your router. Again, you'll find detailed articles on the wiki helping you get HighID and setting up firewall rules for aMule.

We aren't perfect and so aMule isn't perfect, too. We know that. If you find a bug or miss a feature you can report/request it either on the forum, the bug tracker or on GitHub.

Contributions are always welcome!

You can contribute to aMule several ways:

• Contributing code. You can fix some bugs, implement new features, or whatever you want. The preferred way is opening a pull request on GitHub, but you can also post your patch on the forum.
• Translating. You can translate aMule, translate the wiki or translate aMule's documentation to your language.
• Fixing the wiki. aMule's wiki contains a lot of old, outdated information, that is simply not true anymore. One should read through the pages, update manuals and references and remove obsolate information.