Revision as of 13:50, 23 January 2008

Network speed: what you should know before asking questions

Preface

The purpose of this document is to clarify issues regarding network speed that arise from time to time in the aMule forum. Generally speaking, there are several reasons for questions about "aMule network":

• the speed reported by aMule doesn't match your provider's given rate;
• poor performance of aMule itself or another network application on the same computer; or
• the key factors influencing network performance while aMule is running.

The intended audience for this document is users who want to gain a better understanding of network functionality in general, and, in particular, its implications for aMule functionality.

However, this page is not a comprehensive, general purpose "Network FAQ". If you were expecting something else, you might be interested in the aMule is slow FAQ.

Network speed - how fast is it?

When talking about network speed, people use the unit "bps", which means "bits per second". The reason that a bit is used rather than a byte is mostly historical, but also arises from the engineering behind the system, specifically, the fact that not all networks in the world transfer their traffic in bytes.

There is a convention to use a capital "B" in "Bps" when speed is marked in "bytes per second". However, this convention is not widely accepted. In particular, organizations like the IETF and IEEE have stuck to the original "bps".

Prefixes

Since their invention, networks have made a lot of progress. Today we have networks that transfer billions of bits per second. For measuring these speeds, we use prefixes such as "kilo", "mega", "giga", "tera".

It is a common mistake to think that values with those prefixes are the same as in computer science, i.e., powers of 2. The truth is that, for historical reasons, prefixes in networking have a decimal, not a binary base.

As you can see from the table above, the error in calculation is about 5% when the prefix is incorrectly interpreted. Please note that the speed your provider quotes you is the "speed in network units"; i.e., calculated on a decimal basis. For example when your provider tells you that your link is "ADSL 256/128", they mean 256000/128000 bps (bits per second). This means that the speed of your connection is 32000/16000 bps (bytes per second), since there are eight bits to a byte.

Protocol overhead - what is it about?

When aMule is running, it constantly "talks" with other clients and servers. This data exchange is needed to perform such tasks as identifying itself, requesting information about available sources and files, and performing searches.

Since this information has no direct use to the user itself, it is called "overhead"; i.e., a necessary addition to the data you want to upload or download.

aMule calls this "connection overhead". However the number that aMule presents includes only the size of the actual data that aMule itself sends to the network stack. Later, these data are sent out on the network with even more overhead - that of the network protocols. How much is it? - let's see that in the next section.

Network overhead

First of all - we're talking about the IPv4 network. Once upon a time, there was only one type of IP network. Now there are two - IP version 4, the old protocol that we all know; and IP version 6 - the new protocol made to fix the limitations of IPv4.

ED2K protocol by design, is unable to talk over IPv6 network, so users who have it (in Japan and China for example) will not be able to connect "as is". Using IPv4 means, that each packet (TCP, UDP, ICMP) will have an IPv4 header.

The minimum size of this header is 20 bytes. The header can have optional parts (each of 4 bytes) and that is up to your provider - for example, mine adds an optional [dword].

When talking to other clients and servers on ed2k network, aMule uses the widely known TCP protocol. UDP is also used, but on a much smaller scale. As you may already know, TCP is a reliable protocol, i.e. it guarantees that data that is sent from one side will arrive on the other or an error will be reported.

To achieve this, TCP sends its own data in addition to the actual "payload" data being transferred. These data include TCP client initial negotiation, checksums, sequence numbers and acknowledgments. All of this is in the TCP header that is added to each packet sent. The size of this header is a minimum of 20 bytes.

While being only a small overhead for a large bulk transfer, it can take significant part of bandwidth when small amounts of data are being exchanged. This is exactly what happens on source discovery part of aMule.

Our client is trying to establish a connection and negotiate with a large number of other clients. Doing this, aMule opens new TCP connections all the time. The number of connections opened is controlled by the "Maximum number of connections in 5 seconds" setting in the preferences.

A typical number is about 100. Each TCP connection results in at least three packets traveling on the net - one is a SYN packet, i.e. connection request, and one an ACK or a RST when the connection is accepted or refused, and SYN+ACK to establish the session.

There's more overhead of DNS queries when an address is resolved, retries when a host doesn't reply and so on.

At low level

After passing TCP and IP layers packets go down to the network interface driver. What kind of driver this is depends on the way your computer is connected to the internet. For the sake of simplicity, we will assume that this computer is connected to the ISP directly; i.e., that you have no LAN (or switch or router) between.

Common setups include:

• an analog modem, connected to a telephone line (ISDN modem falls in this category too);
• a cable modem, connected through ethernet, ISP gives you an IP address through DHCP;
• a cable modem, connected through ethernet, ISP requires you to configure PPPoE or PPTP tunnel;
• an ADSL modem, connected through ethernet. You must have a PPPoE or PPTP tunnel;
• a variation on these, e.g., a modem connected to a computer via USB.

In each of the these setups there are different protocols in use, and different headers are added to transmitted packets. There's one important thing to note: ethernet frames travel between cable/ADSL modem and computer, and don't reach the ISP. Consequently, they're not counted in rate calculations. PPPoE; in constrast, PPTP headers do reach the ISP. In this respect, your particular provider may or may not choose to include them in their rate calculations. For this reason, we have excluded those headers from our calculations.

If you think that your ISP includes it, add 4 bytes to the size of each packet.

Example

Let's see how much network overhead we have on a typical network. Our connection is a cable modem connected via an ethernet link to a PC directly (no router between them).

In this setup we have IPv4 packets sent over ethernet.

Lets say we have 10 new connections opened each second, and all are being accepted (successfully established TCP session). This alone sums up to (I'm counting data going up - from my computer to the net):

10 connection * 2 packets * (20 bytes of TCP + 20 bytes of IPv4) = 800 bytes of overhead.

This means that we are starting with 1.16*8 Kbps of "invisible" overhead caused by the very way the network works. Now, let's assume that after each connection is established our amule sends something to the other side and waits to receive an answer.

Total of 800 bytes + 800 bytes = 1600 bytes per second = 6400 bps = 6.4 Kbps

What we have here is 6.4 Kbps of network overhead alone. Taking into account that amule has other data to send (uploads) and it is not the only network application running we will have the following picture:

Most likely the link to your provider is not that fast. aMule will try to open 10 connections per second and will try to upload on the specified speed.

Your operating system will share all available bandwidth between those and between aMule and other network applications (browser for example). Actual results will vary depending on specific OS settings.

ACK bottleneck

In all calculations above there was one assumption - zero download. But downloading is what amule was built for. So let's examine how the overhead above affects your downloading speed. The answer is in TCP protocol.

When TCP is sending data, it requires that the other side acknowledge the reception. So if client A is sending data to client B by TCP, B has to send a special ACK packets to A which tells B "ok, I got it". If, however, A doesn't receive the ACK packets in time, he will assume that either packet is lost.

So, without going deeply into TCP specification: if B fails to send ACK to A, as a result A will transmit slower.

Now let's see the situation in aMule. We saw in the previous chapter, that the uplink stream is congested by connection requests and uploads. As a result, there's a good chance that ACK packets for a file we are downloading will not be sent on time.

The remote party will notice this and slow down. This is one more reason why the upstream should better not be too congested.

Is there anything I can do?

OK, now that you understood why your network is so slow while aMule is running you will maybe look for a way to fix this. The answer in 2 words: "rate limit".

The first thing you should do is to assign realistic rate limits in aMule itself. If you have a uplink rate of 128 Kbps don't set aMule's upload limit to 16 (kilobytes per second) just because 128/8 = 16.

A better, but far more complicated solution is to use the QoS and packet scheduling services of your OS. For example, you can give a higher priority to ACK packets to solve the above mentioned "ACK bottleneck" problem.

The QoS topic, however, is beyond the scope of this article.

Router (switch, home network): is there any difference?

When the cable coming from your ISP is connected to some switching or routing device, which in turn is connected to several PC's, bandwidth is shared between them.

So, having N computers connected, an ideal device would simply provide each one of them with 1/N of the total bandwidth. The situation may vary in real life, and your particular device may have different idea about fairness.

Since you're not going to have the hardware specs of your router chipset the only advice here is "try and see yourself".

Multiple links

Until now, we talked about computers that are connected to the network through single interface. While being most frequent, this is not mandatory. A user may choose to connect via 2 (or more links) provided by different ISP's. There're 2 reasons for this decision that I know about: link redundancy and load balancing.

Link redundancy

In a case of link redundancy second link becomes operational when primary link fails. This can be done automatically, or by explicit user command. When this setup used, aMule along with other network applications must be restarted when links are being switched. This will allow to bind new address, reconnect to server and receive new ID. If aMule is connected via  NAT] enabled router (it doesn't matter if you have low or high ID), and links are switched on the router, restart not needed.

Load balancing

This is a far more complicated case. Both (all) links are simultaneously active, and traffic is being distributed between them. The problem is that aMule binds to all interfaces on the system i.e. 0.0.0.0. But, on ed2k your ID is your IP address, and you can not have two.
So the problem is that aMule does not explicitly choose the source address for outgoing TCP connections. Note, that it doesn't matter on which interface it listens. This is exactly opposite to server applications like FTP or HTTP. When a client tries to connect to a server it discovers its IP address by resolving DNS. Resolver replies will contain all IP addresses of the specified host and a client should try them all. The server, in turn, may choose not to listen on one of them and thus prevent the client from using this interface. In our case aMule is a client, and the ed2k server discovers its address from the source IP in the connection request. That's where the ed2k server will try to connect. If the connection succeeds the client is client assigned a high ID, if it doesn't the client gets a Low ID. The only solution in this situation (until aMule will have an ability to bind to specific address) is to use aMule on your "primary" link.
You can, however, cause Linux to send packet through interface of your choice. But, most probably they will be dropped by your ISP's router as "spoofed" because the source IP address doesn't match the address the ISP assigned to that interface.

Version

Created by "Unknown User" on 27.02.05 at 15:21
Updated by Vollstrecker on 23.01.08 at 13:51