During the network analysis, I found that the roundtrip latency time between station 1 and server FS2 is almost twice the delay of other similar communications. I have examined the communications further to find that station 1's data is taking a less direct route to FS2's network. However, when a new application is rolled out on the network, IT must be able to predict how it will perform for the business, and one of the key performance metrics for application performance is latency. Furthermore, existing mission-critical applications must not be negatively impacted by new applications. This type of high-resolution forensic analysis can help to detect latency problems at the highest level and drill down quickly for a closer look. Ideally, network latency and application latency measurements can be graphed together over time. What is critical is that you are monitoring that latency so that you can identify what is typical and respond to issues quickly. The guidelines for acceptable latency on your local network are: 1  A round trip latency of 30ms or less is healthy. 2  Round trip latency between 30ms and 50ms should be monitored closely. 3  Round trip latency over 50ms quires immediate attention to determine the cause of the latency and potential remedied. Analyzing latency due to networking and server location can be achieved by performing a traceroute from to your server. You can also perform a traceroute between your website and a variety of worldwide nodes at gomeznetworks.com – useful when you are not in the same location as your users. Integrators regularly want to know what is acceptable network performance and what can be done to improve things when performance is sub-par. The unfortunate answer is that there is no Silver Bullet to all network issues. But it’s very important to understand the causes of network latency and how to reduce it. It’s important that network engineers are able to assess things like latency, both from the network and the application itself, and provide immediate feedback on how new applications behave on the network. Here are three keys to determine whether latency is caused by the network or the applications in your environment. If the network admin runs periodic checks in the background to the application host, it can provide an ongoing baseline of the performance of the network between users and the host. If the baseline increases, alarms are used to notify that the network latency is becoming an issue. 3.
http://support.novell.com/techcenter/articles/nc2000_02b.html http://blog.wildpackets.com/2011/03/29/three-keys-to-breaking-down-network-and-application-latency.html http://blog.wildpackets.com/2011/03/29/three-keys-to-breaking-down-network-and-application-latency.html http://www.cepro.com/article/network_latency_analyzing_the_negative_effects http://blog.iweb.com/en/2014/02/understanding-analyzing-reducing-latency/13176.html http://www.cepro.com/article/network_latency_analyzing_the_negative_effects http://blog.wildpackets.com/2011/03/29/three-keys-to-breaking-down-network-and-application-latency.html http://blog.wildpackets.com/2011/03/29/three-keys-to-breaking-down-network-and-application-latency.html
how to analyze network latency