Discussion Locked

Bandwith vs latancy in an office network

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I would like to know what would be better in a office network environment of about 50-75 users. Is it better to have a network with low latancy and low bandwith or one with high bandwith and high latancy.
I also would like to know how latancy correlates to bandwith.
How would one optimize bandwith while minimizing latency.

3 replies

by oldefar

You need to differentiate between bit latency and packet latency.

Bit latency is impacted by distance traveled, the media used, and to a small degree the communication devices. Distance is most apparent with satellite - adding 40,000 miles to the distance adds almost a quarter second of bit delay, half second on round trips. Media used is most apparent with fiber versus copper segments. Here we are looking at speed of light versus speed of electrical pulse over copper.

The devices in the path will add at least 4 clock times at whatever the internal clock of the device is. It is negligible when looking at total performance.

Bit latency is constant for a given path between two point.

Packet latency is reflected in the processing time of communications, congestion, and bandwidth. The processing time involves the protocol used, the routing methods used, and the efficiency of the device (clock, OS, memory). This is all constant for a given path. Most routers will add between 2 and 10 msec of latency each. Switches add no more than 5 msec, and a cut through switch will add less. Bridges add about 1 msec. Added functions like stateful inspections at a firewall and packet compression add to the latency.

The impact of bandwidth on latency to follow.

by oldefar

Bandwidth adds latency equal to the packet size times the bit rate. Bit rate is 1/xbps. As a factor, only the lowest bandwidth in the total path is considered. A 64 Kbps circuit has 24 times the packet latency of a T1 for example. A full packet of 1500 bytes takes 187 msec on a 64 Kbps circuit, and 7.8 msec on a T1.

While it may seem that bandwidth will result in improved performance from the user perspective, this may not be the case. Consider the T1 over satellite and the 64 Kbps circuit a land line. The bit and packet latency approximates to:
T1 - 500+ msec
64 Kbps - 190+ msec

In most cases, I have found bandwidth above 256 Kbps to offer very little performance gain in most applications. At 768 Kbps, performance appears flat as bandwidth increases.

Now this is without any consideration of load. In terms of total traffic, bandwidth acts like the lanes of a highway. If your network is congested no one can achieve full legal speed, so adding lanes will help to relieve congestion. My experience with interactive traffic has been that a consistent average utilization of 80% and below on the smallest segment will have no noticable impact to the users.

by oldefar

I talked about bit and packet latency in my other two posts.

The efficiency of the communications piece is also impacted by packet size. Every packet has overhead - essentially the packet header. This is nothing more than the envelope for the application data. If you are on dialup, you want small packets so that the amount of retransmissions from line errors is kept to a minimum. However, if the lines are clean, each packet is adding overhead so a larger packet size is preferred.

Tasks are really how users perceive performance, and the best way to optimize is to measure task performance. Script the user keystrokes, and measure the whole task completion on a single LAN segment. This will give the task completion time as a factor of client, server, database, and communications. The communication piece measured will exist even if you move to a WAN environment. Now what part of the task completion was communication? This is the only part you will impact with bandwidth and latency. If the time is already unacceptable, focus on changes to the application, the database, or the client first before leasing more bandwidth.

There are a couple of programs that will handle projecting how bandwidth, load, and latency will impact the total time. Application Expert from CompUSA does a good job. Opnet IT Decision Guru will give you a more precise analysis. Etherpeek will also breakdown the times for you.

This discussion is closed to new replies.