- Small Business Trends - http://smallbiztrends.com -
What Makes My Application Slow: The Pipe or the Packet?
Posted By Craig Sutton On September 19, 2013 @ 11:00 am In Technology Trends | 13 Comments
It’s a common problem. Whether you are using your company’s VPN (virtual private network) or you’re having trouble with your IP telephone, or some other reason — the application you are using seems to be slow and sluggish.
It frustrates end users, because the speed of these applications also changes at a pace that may seem random and is hard to predict. All your end users really care about is using the tools they need. And they want them to be fast, not sluggish.
To be able to fix the problem, it helps to first understand what is causing it. So let’s dive in and take a look.
Information, whether it is provided over the Internet or your own business network is all broken down into smaller pieces of data known as “packets.” These data packets carry information about many things, including its destination (where its supposed to be going, such as your company database) and even error checking to be sure the packet made it in one piece. The speed, or amount of time it takes for a packet to cross the network from a device that created the packet (such as your laptop computer) to the destination device (such as your central business server) is called network latency.
In other words, when you see the word latency in this context, think “delayed speed.”
There are a few factors that create latency issues. Network routers typically create the most latency of any device on the end-to-end path. Packet queuing due to link congestion is most often the culprit for large amounts of latency through a router. Some types of network technology such as satellite communications add large amounts of latency because of the time it takes for a packet to travel across the link. Since latency is cumulative, the more links and router hops (passes between multiple devices such as your computer, routers, Internet provider equipment and the equipment on the destination side) there are, the larger the end-to-end latency will be.
The amount of available bandwidth also has a place in network and application speeds. Your available bandwidth is determined by the direction and destination of your information.
I like to think about bandwidth from the context of plumbing. Sure enough, people often refer to bandwidth as “the size of the pipe.” So why not carry that analogy further?
The pipe size is determined by the amount of available bandwidth on your local network first, but then by the size of your Internet pipe and the size of the destination pipe if the information is leaving your local network.
So if you’re on a gigabit network locally, but you have a 10MB Internet connection and your main office has a 100MB Internet connection you can see that the bottleneck may be your office Internet connection. But only if that pipe is full.
That pipe may be full if several users are trying to use high bandwidth resources over the Internet at the same time. Each VPN connection will have overhead, or video conferencing, ip telephony shared between offices, etc. The weakest point between the locations can cause the bottleneck, just as too many traffic hops can cause latency.
Some applications are more forgiving than others. Much of this revolves around whether an application will just send packets in one direction (User Datagram Protocol or UDP) or requires a connection to assure the data has arrived (Transmission Control Protocol or TCP). Both protocols have their upsides and downsides but every application uses one or the other based on the importance of the information
Well, now we know what causes slow network applications, so lets take a look at how we can fix some of these issues.
First, examine your latency. IT technicians perform a ping command between any computer having speed issues and the destination computer where you are trying to share resources, such as your server. This will show you the number of hops (or other network resources) your packet will take until it lands at its destination. Your goal is to take as many hops out of the equation as possible to shorten the trip.
If you are using multiple Internet connections, it may be difficult to remove some hops. This is where the choice of technology makes a difference. A technology such as Metro Ethernet can really help you reduce that overhead. It provides a network between multiple physical locations without having multiple Internet connections as it does not use routers, in general. It uses switches, which are faster because they are not opening the packets as they flow through the network … making it one network and reducing the number of hops.
Bandwidth is still important, however, for those who would be connecting outside of your office infrastructure. Be sure to carefully do the math on the needs of staff who will not work in your office and be sure to provide enough bandwidth for your current workload and theirs.
Ultimately, if handled correctly, you can actually save money using a combination of increased bandwidth at a source location and a Metro Ethernet provider who can share all of your resources with lower overhead between office locations.
* * * * *
More detail on Metro Ethernet can be found here  for those looking for deeper technical knowledge.
Speed  Photo via Shutterstock
Article printed from Small Business Trends: http://smallbiztrends.com
URL to article: http://smallbiztrends.com/2013/09/what-makes-my-application-slow.html
URLs in this post:
 detail on Metro Ethernet can be found here: http://business.comcast.com/enterprise/resources/details?NewsItemID=fddf8dac-4caf-4f7d-a49a-7a31b49e1955
 Speed: http://www.shutterstock.com/pic-101661526/stock-vector-slow-connection-speed-internet-download-vector.html