You are here: Visualware > MCS Home > Bandwidth, Capacity & Performance

Bandwidth, Capacity & Performance

Data Quality
VoIP & Streaming
Bandwidth & Capacity
Secure Architecture
Network Service Assessment
Pre-qualification
Publishing

Network Performance is Essential to the Success of Business Applications

Everyone wants to measure bandwidth, yet bandwidth is not a performance measure, it's a rate.

Saying the speed of a connection is 100Mpbs is like saying the speed limit of a freeway is 300 cars per hour. When planning a time critical journey, like catching a flight, knowing the rate of the road is of little use. Packets traveling across a network are all time-critical in determining network performance, so why accept a rate of 100Mbps as a valid assessment of network performance?

That being said bandwidth is still an important measure, it defines capacity. Having more lanes on the freeway doesn't make cars go faster, it just means more cars can utilize the freeway. Bandwidth is a business parameter.

So, what does this mean for network measurement...?

To understand the user experience a speed test must measure the equilibrium throughput of the connection. Why?

Equilibrium not only measures the speed but also measures that the data arrives on time, which allows the test to detect when a connection is slow.

Equilibrium therefore defines the true performance of the application using the connection and with it the user experience.

So, why do most speed tests fail?

Nearly all speed tests fail because the test combines multiple sessions of data and divides by the time of the test to report the Mbps result. Seems reasonable except this approach implies that 10 cars doing 1mph delivers the same performance as 1 car doing 10mph. This is not true, consider driving 10 miles to catch a flight that departs in 2 hours, the 10mph vehicle arrives in 1 hour, the 1mph vehicles arrive in 10 hours. Supposedly the same result, 10 miles in one hour, is the user experience the same?