ContactSupportNewsBlog
Left Menu CurveCustomersDivider LineProductsDivider LineSolutionsDivider LineServicesDivider LineResourcesDivider LineNewsDivider LinePartnersDivider LineCompanyRight Menu Curve
NetQoS / Resource Room / Technical Articles
 
Articles
 

Bandwidth versus Distance Latency
Bill Alderson, Technology Consulting Officer, NetQoS, Inc.

The first step in evaluating an application to be used across long-distance circuits is to determine if the application is bandwidth or distance sensitive. The difference between these two types of latency is the size of the packets and the ability for the transport protocol to send bursts of packets. Determine the amount of time to transmit a packet on a link with this equation:

(Packet Size in Bytes * 8)/(Link Speed in Bits per Second)

The result is the number of seconds required to transmit this packet onto the link. This number will vary depending on the speed of the link between the two sites. If the application uses a few large packets that can be sent one after another without waiting for acknowledgements from the other end, an increase in bandwidth will reduce the application response time.

Distance latency is the time it takes to propagate the signal from one point to another. This time is fixed, depending on the medium used to transport the data. An increase in bandwidth will NOT reduce this time. If an application sends a packet and must wait for an acknowledgement before sending the next packet, the response time increases as the link between the server and client increases. In our application analysis, we see client/server applications that execute one SQL call and then execute another based on the data returned by the first. When you place processes serially, increasing bandwidth has little impact on improving response times.

By developing applications that allow transport protocols such as TCP/IP and IPX Burst Mode to do their jobs, you can deploy applications across the nation and the world with somewhat consistent response times. Increasing bandwidth is a cost you must pay each month, whereas a network application written with WAN circuits in mind is a one-time cost that results in monthly savings. Keeping Distance latency and Bandwidth latency in mind when developing, implementing, and analyzing WAN applications leads to WAN Friendly Applications and reduced monthly expenditures.

 
 
resource room ::

Whitepapers
Case Studies
Datasheets
Webinars
bulletPodcasts
Industry Initiatives
bulletTechnical Articles

Do:
Print Page
Request A Demo
Refer A Friend

Send To:
Del.icio.us
Digg
Slashdot
Reddit


sitemap :: legal :: request info :: contact us

 
     
 

NetQoS - The Industry's Fastest Growing Network Performance Management Company
© 2001-2008 NetQoS, Inc. All rights reserved.

IT Solutions:
VoIP Performance
| MPLS Management | WAN Troubleshooting | Network Capacity Planning | Service Level Reporting | Network Monitoring | QoS Policy Management | WAN Optimization | ITIL and ITSM | NetFlow | Application Delivery | Bandwidth Utilization | Cisco WAAS | Cisco NetFlow | NetFlow Monitoring | Passive Network Monitoring | Packet Forensics | Cisco IP SLA Reporting | SNMP Polling | Application Performance Monitoring | Network Performance Monitoring | Network Performance Software | Network Management Software


Products:
NetQoS Performance Center - Network Monitoring
| NetQoS SuperAgent - Service Level Reporting | NetQoS ReporterAnalyzer - Network Traffic Analyzer | NetQoS NetVoyant - SNMP Polling | NetQoS VoIP Monitor - VoIP Performance Monitoring | NetQoS GigaStor - Network Analysis | NetQoS Allocate - IT Cost Accounting


Resource Room:
Network Performance Monitoring Whitepapers | Network Problems | Case Studies | Data Sheets | Networking Webinars | Networking Podcasts | Industry Initiatives | The B2B Lead | Network Performance Daily Blog | Network Management News | Network Performance Management Articles


Services:
NetQoS Product Implementation
| NetAnalyst Training | Network Consulting Services | VoIP Readiness | Network Certification Training