Network Latency

Understanding Network Latency

Network latency, also known as the time it takes for a data packet to travel from one point to another, can be measured in absolute or relative time depending on the timing of the request. It encompasses both the physical distance the data needs to travel and the processing time it requires. For example, let’s say you’re streaming a movie on Netflix. Even though the movie is stored on a server in California, your request goes through multiple servers before reaching its destination. Once the server receives your request, it needs to process it before sending the movie back to you. All of these steps take time. A high latency results in a longer delay between pressing the play button and the video actually playing.

The acceptable level of latency depends on the online activity you’re engaged in. Gaming and video chatting require higher latency thresholds compared to email and web browsing.

Experts in information technology suggest that the human brain can handle approximately 50 milliseconds, which is one-tenth of a second, of lag. While this may be sufficient for most individuals, gamers often prefer lower latencies. Professional gamers consider anything over 100 milliseconds, or one-tenth of a second, to be too much lag for an optimal gaming experience.

A lower displayed latency is desirable as it indicates better performance. High latency can be caused by a low bandwidth connection, overloaded servers, or full router queues.

Network latency is typically measured in milliseconds (ms). For example, 200 ms translates to 200 milliseconds, or 0.2 seconds, while 300 ms equals 0.3 seconds.

The impact of network latency is particularly significant in the context of blockchain and cryptocurrencies. This is because it directly affects the time required for a transaction to be confirmed.

Blockchains operate on a consensus mechanism, where miners rely on speed to earn rewards. Every second that passes without finding and adding a new block to the blockchain results in potential revenue loss.

The Relationship Between Latency and Throughput

Latency measures the time it takes for a transaction to be completed, while throughput quantifies the amount of work in terms of transactions per second.

Attempting to increase the throughput of HTTP requests without considering latency can lead to performance issues. The goal should be to enhance throughput while maintaining low latency.

The most effective optimization strategies involve reducing the number of HTTP requests, minimizing response time from servers, consolidating database calls when possible, and maximizing data caching.