Terry Slattery
Terry Slattery, is a senior network engineer with decades of experience in the internetworking industry. Prior to joining Chesapeake NetCraftsmen as...
Read Full Bio >>

Terry Slattery | June 21, 2017 |


Why's My Network So Slow?

Why's My Network So Slow? There are several approaches to diagnosing whether a problem exists on the network or the application.

There are several approaches to diagnosing whether a problem exists on the network or the application.

We have had several customer cases at NetCraftsmen that involved slow applications as of late. The first step in determining the cause is to identify and isolate the factors that contribute to slow applications. In each case, we started by trying to determine if the application slowness is caused by something in the network or by something in the application.

Is It the Network?
Network causes include obvious things like interface errors and less obvious things like network congestion, which also results in packet loss. Interestingly, packet loss has a significant detrimental effect on applications that rely on TCP. A small amount of packet loss will reduce a 10ms, 1Gbps path to a path with only 200Mbps of goodput. Goodput is the volume of delivered application data, excluding packet retransmissions. How much is small in terms of packet loss? Loss of 0.0001% is the threshold in this case. Learn more about the impact of packet loss on TCP by reading about the Mathis Equation.

Real-time voice and video (UC) applications use UDP for transport and are able to handle up to 1% packet loss as long as the lost packets are random. The codecs in use are able to interpolate between adjacent samples, allowing the audio or video systems to cover up for an occasional lost packet. However, they do not work well with burst loss. In this case, the codecs do not have the necessary samples from which to perform the interpolation to recover lost packets.

Interface congestion occurs at two places in networks. The first is at speed mismatch points, such as data from a LAN that needs to transit a lower speed WAN link to a remote site. The router that connects the LAN segment to the WAN link contains a small number of buffers in which received packets can be stored while the WAN link transmits a previous packet. But this buffering is limited. Using too many buffers causes problems with transport protocols like TCP, so it is better to drop packets when the router buffers fill and let TCP handle the retransmission. The packet loss tells TCP that the path bandwidth has been filled and that it should slow down. This is normal. It is high volumes of packet loss that are an indication of network congestion. We've found that more than about 100,000 drops per day is an indication of significant network congestion warranting investigation.

Another source of network-induced problems is due to high latency paths, sometimes known as long fat pipes if the path is high bandwidth. In this case, an application that uses many small packets in a back-and-forth interaction between the client and the server will seem slow, simply due to the length of time that it takes for all the packets to transit the high latency link.

Let's examine the worst case scenario: a client that needs to exchange 1,000 packets with an application server to display a complex graphical interface. The typical round-trip latency across the continental U.S. is 60 milliseconds. If the application waits for the client to acknowledge each packet before sending the subsequent packet, we're talking about 1,000 * 60ms = 60,000ms, or 60 seconds. An application like this would likely run well in a local LAN environment where the latency is 2ms (2 seconds to refresh the display).

Is this a network problem or is it an application problem? Well, it is some of both. There isn't anything that can be done about latency -- it is due to the speed of light of the electrical or optical pulses over a path that's 6,000 miles long. We sometimes find strange routing path selection will create a long path when a much shorter and faster path is available. The solution in these cases is to route the traffic over the shorter path.

A packet capture of an application can tell us whether the application is sending a lot of small packets and whether it is waiting for each packet to be acknowledged. We also use packet captures to identify packet loss, which appears as a significant volume of retransmissions and duplicate ACKs. In one customer case, we found that there was insufficient bandwidth between two local facilities for the types of applications that were running over them. The packet captures showed hundreds of thousands of retransmitted packets per day. The routers that connected each site were showing high packet discard rates on their metro Ethernet connections.

Is It the Application?
An Application Performance Management (APM) system makes it easy to differentiate between network causes and application-specific causes. I think of these systems as super-smart packet capture and analysis systems. A good system can identify when server responses are slow, indicating an application problem instead of a network problem.

On the network side, they can identify packet retransmissions that indicate packet loss within the network or high latency in network transactions, both of which indicate network problems. Since an APM also sees all the packets, it can identify a poorly designed application that uses many small packets instead of fewer, larger packets. However, not many customers have an APM installed, so we often have to resort to other approaches.

Modern, multi-tiered applications can often have internal problems that cause an application be sluggish. At another customer, we found that a poorly written SQL query between two tiers of an application caused slowness that was initially attributed to a network problem. In this case the customer had an APM and was able to diagnose the problem within an hour. Similarly, an SQL query that works well in software development may not work well in production when the debase grows, so look for those queries as well. A packet capture will show whether the server is sending updates to the endpoints in a timely manner (an application problem) or if it is encountering packet loss that requires retransmission (a network problem).

We've also seen misconfigured applications cause problems that make applications perform poorly. An interesting case involving video conferencing systems took several months to diagnose. There were constant reports of the video being garbled, unclear audio, and long call establishment times. Of course, the network was accused of being the problem ... and at first, it sure looked that way. Packet loss was high, as reported by the UC video systems.

But separate tests between the video conference systems showed no problems. We finally looked over the system configurations in great detail and found that some of them were configured to use a Multipoint Control Unit (MCU) on the Internet instead of the MCU within the organization for internal calls. The volume of video traffic, combined with data traffic, overwhelmed the Internet links, causing packet loss. Our testing had been directly between the internal subnets, not realizing that the traffic was being routed out to the Internet.

The application server staff can also be of great assistance by reporting if the servers are taxing their memory, storage system, or CPU during the reported times of slow applications. They can also report on TCP stats that indicate significant packet loss, helping everyone understand which components are likely candidates for further investigation.

It can sometimes seem impossible to determine why an application runs slowly. Looking for packet loss is an easy indicator of whether it might be a network problem or an application problem. And as we saw in the above examples, it might be an incorrect configuration that sends traffic over unexpected paths that either increase latency or encounter packet loss.

Make sure you are testing over the path that the traffic is actually using. Finally, get the server and application teams involved to provide additional data. Everyone has to work together to resolve the more challenging cases.


October 24, 2018

With disparate workplaces and ever-expanding volumes of information to manage, the challenges for collaborating effectively are only intensifying. Many critical applications are not integrated, and

October 10, 2018

Businesses are growing across international borders quicker than ever, but scaling operations to follow suit can be a harder, longer process.

This webinar focuses on scaling your next-generat

September 26, 2018

Join Kevin Kieller, Microsoft UC&C expert, along with Ribbon Communications and Polycom, for an update on Microsoft Ignite, and a focus on critical things you need to know about your voice deployme

March 12, 2018
An effective E-911 implementation doesn't just happen; it takes a solid strategy. Tune in for tips from IT expert Irwin Lazar, of Nemertes Research.
March 9, 2018
IT consultant Steve Leaden lays out the whys and how-tos of getting the green light for your convergence strategy.
March 7, 2018
In advance of his speech tech tutorial at EC18, communications analyst Jon Arnold explores what voice means in a post-PBX world.
February 28, 2018
Voice engagement isn't about a simple phone call any longer, but rather a conversational experience that crosses from one channel to the next, as Daniel Hong, a VP and research director with Forrester....
February 16, 2018
What trends and technologies should you be up on for your contact center? Sheila McGee-Smith, Contact Center & Customer Experience track chair for Enterprise Connect 2018, gives us the lowdown.
February 9, 2018
Melanie Turek, VP of connected work research at Frost & Sullivan, walks us through key components -- and sticking points -- of customer-oriented digital transformation projects.
February 2, 2018
UC consultant Marty Parker has crunched lots of numbers evaluating UC options; tune in for what he's learned and tips for your own analysis.
January 26, 2018
Don't miss out on the fun! Organizer Alan Quayle shares details of his pre-Enterprise Connect hackathon, TADHack-mini '18, showcasing programmable communications.
December 20, 2017
Kevin Kieller, partner with enableUC, provides advice on how to move forward with your Skype for Business and Teams deployments.
December 20, 2017
Zeus Kerravala, principal analyst with ZK Research, shares his perspective on artificial intelligence and the future of team collaboration.
December 20, 2017
Delanda Coleman, Microsoft senior marketing manager, explains the Teams vision and shares use case examples.
November 30, 2017
With a ruling on the FCC's proposed order to dismantle the Open Internet Order expected this month, communications technology attorney Martha Buyer walks us through what's at stake.
October 23, 2017
Wondering which Office 365 collaboration tool to use when? Get quick pointers from CBT Nuggets instructor Simona Millham.
September 22, 2017
In this podcast, we explore the future of work with Robert Brown, AVP of the Cognizant Center for the Future of Work, who helps us answer the question, "What do we do when machines do everything?"
September 8, 2017
Greg Collins, a technology analyst and strategist with Exact Ventures, delivers a status report on 5G implementation plans and tells enterprises why they shouldn't wait to move ahead on potential use ....
August 25, 2017
Find out what business considerations are driving the SIP trunking market today, and learn a bit about how satisfied enterprises are with their providers. We talk with John Malone, president of The Ea....
August 16, 2017
World Vision U.S. is finding lots of goodness in RingCentral's cloud communications service, but as Randy Boyd, infrastructure architect at the global humanitarian nonprofit, tells us, he and his team....
August 11, 2017
Alicia Gee, director of unified communications at Sutter Physician Services, oversees the technical team supporting a 1,000-agent contact center running on Genesys PureConnect. She catches us up on th....
August 4, 2017
Andrew Prokop, communications evangelist with Arrow Systems Integration, has lately been working on integrating enterprise communications into Internet of Things ecosystems. He shares examples and off....
July 27, 2017
Industry watcher Elka Popova, a Frost & Sullivan program director, shares her perspective on this acquisition, discussing Mitel's market positioning, why the move makes sense, and more.
July 14, 2017
Lantre Barr, founder and CEO of Blacc Spot Media, urges any enterprise that's been on the fence about integrating real-time communications into business workflows to jump off and get started. Tune and....
June 28, 2017
Communications expert Tsahi Levent-Levi, author of the popular blog, keeps a running tally and comprehensive overview of communications platform-as-a-service offerings in his "Choosing a W....
June 9, 2017
If you think telecom expense management applies to nothing more than business phone lines, think again. Hyoun Park, founder and principal investigator with technology advisory Amalgam Insights, tells ....
June 2, 2017
Enterprises strategizing on mobility today, including for internal collaboration, don't have the luxury of learning as they go. Tony Rizzo, enterprise mobility specialist with Blue Hill Research, expl....
May 24, 2017
Mark Winther, head of IDC's global telecom consulting practice, gives us his take on how CPaaS providers evolve beyond the basic building blocks and address maturing enterprise needs.
May 18, 2017
Diane Myers, senior research director at IHS Markit, walks us through her 2017 UC-as-a-service report... and shares what might be to come in 2018.
April 28, 2017
Change isn't easy, but it is necessary. Tune in for advice and perspective from Zeus Kerravala, co-author of a "Digital Transformation for Dummies" special edition.
April 20, 2017
Robin Gareiss, president of Nemertes Research, shares insight gleaned from the firm's 12th annual UCC Total Cost of Operations study.
March 23, 2017
Tim Banting, of Current Analysis, gives us a peek into what the next three years will bring in advance of his Enterprise Connect session exploring the question: Will there be a new model for enterpris....
March 15, 2017
Andrew Prokop, communications evangelist with Arrow Systems Integration, discusses the evolving role of the all-important session border controller.
March 9, 2017
Organizer Alan Quayle gives us the lowdown on programmable communications and all you need to know about participating in this pre-Enterprise Connect hackathon.
March 3, 2017
From protecting against new vulnerabilities to keeping security assessments up to date, security consultant Mark Collier shares tips on how best to protect your UC systems.
February 24, 2017
UC analyst Blair Pleasant sorts through the myriad cloud architectural models underlying UCaaS and CCaaS offerings, and explains why knowing the differences matter.
February 17, 2017
From the most basics of basics to the hidden gotchas, UC consultant Melissa Swartz helps demystify the complex world of SIP trunking.
February 7, 2017
UC&C consultant Kevin Kieller, a partner at enableUC, shares pointers for making the right architectural choices for your Skype for Business deployment.
February 1, 2017
Elka Popova, a Frost & Sullivan program director, shares a status report on the UCaaS market today and offers her perspective on what large enterprises need before committing to UC in the cloud.
January 26, 2017
Andrew Davis, co-founder of Wainhouse Research and chair of the Video track at Enterprise Connect 2017, sorts through the myriad cloud video service options and shares how to tell if your choice is en....
January 23, 2017
Sheila McGee-Smith, Contact Center/Customer Experience track chair for Enterprise Connect 2017, tells us what we need to know about the role cloud software is playing in contact centers today.