

This is an important point: Throughput is how much actual traffic is flowing when you do a real-time measurement or the rate of data delivery over a specific period of time. Throughput is the actual amount of traffic flowing from a specific individual source or group of sources to a specific destination or group of destinations at a specific point in time. So bandwidth and throughput are two very different things.

But their throughput was down to about 1Mbps because of the bad NIC card causing congestion.

The client was right: they had plenty of bandwidth (100Mbps) for what they were doing. It was spewing broadcast packets across the network and causing network congestion.īut this scenario above perfectly illustrates the difference between network throughput and bandwidth. In this case, it didn’t take long to discover there was a server with a bad NIC card. The client says, “Why is this slow? I have plenty of bandwidth.” They’re going through a good switch onto a 1Gbps link. They had a few servers, and several dozen workstations, running at about 100Mbps (which was more than enough at that time). I’d been asked to look into the problem and help them solve it. Imagine this scenario from many years ago: I was working with a client and they had a strange problem with a very slow response on their network. And while we’re at it, let’s cover the fundamentals of throughput and how to measure it, so you can keep your network flowing efficiently and cleanly. Namely, let’s look at the key differences between network throughput and bandwidth. So let’s see where we get these mixed up. Have you used them interchangeably? Most likely. Have you ever used the term network throughput? Maybe. Have you ever used the term bandwidth? Probably.
