{"id":82482,"date":"2026-09-23T09:32:03","date_gmt":"2026-09-23T12:32:03","guid":{"rendered":"https:\/\/a3aengenharia.com\/?post_type=articles&p=82482"},"modified":"2026-09-23T09:32:03","modified_gmt":"2026-09-23T12:32:03","slug":"computer-network-performance-latency-jitter-loss-throughput-capacity","status":"publish","type":"articles","link":"https:\/\/a3aengenharia.com\/en-us\/content\/technical-articles\/computer-network-performance-latency-jitter-loss-throughput-capacity\/","title":{"rendered":"Computer Network Performance: Latency, Jitter, Loss, Throughput, and Capacity"},"content":{"rendered":"\n

Computer network performance is the ability of the infrastructure to carry the required traffic flows with useful data rate, delay, delay variation, loss, and availability compatible with application requirements<\/strong>. It is not enough for an interface to operate at 1, 10, or 100 Gb\/s: the actual experience depends on the complete path, queues, concurrent load, packet size, physical and logical architecture, hosts, and protocol behavior.<\/p>\n\n\n\n

A network can have high nominal bandwidth and still exhibit low throughput, retransmissions, jitter, or increasing latency under load. Performance should therefore be treated as an engineering discipline: requirements need to be defined before design, measured with a reproducible methodology, and verified during operation and acceptance.<\/p>\n\n\n\n

The purpose of this article is to establish that foundation: what to measure, why the metrics are interrelated, how architecture affects the result, and how to turn performance into a verifiable requirement<\/strong>. Diagnosing a network that already exhibits slowness or instability is a complementary but distinct problem.<\/p>\n\n\n\n\n

What Defines Network Performance?<\/h2>\n\n\n\n

The performance perceived by an application results from the interaction among the source, destination, and every element along the path. Between two hosts there may be switches, routers, firewalls, Wi-Fi controllers, WAN links, tunnels, load balancers, cloud services, and independent queues. Each element can add delay, impose a maximum capacity, drop packets, or change how flows compete for resources.<\/p>\n\n\n\n

For this reason, the analysis should not be reduced to the question \u201cwhat is the link speed?\u201d. It is necessary to distinguish nominal capacity<\/strong>, utilization<\/strong>, throughput<\/strong>, goodput<\/strong>, lat\u00eancia<\/strong>, jitter<\/strong>, perda<\/strong>, retransmissions<\/strong> and availability<\/strong>.<\/p>\n\n\n\n

The architecture should also consider the behavior of Network Traffic: flows, load, broadcast, multicast, and capacity<\/a>, because a link rarely carries only one isolated service.<\/p>\n\n\n\n

Relationship among demand, capacity, queues, and application-perceived performance<\/title>