PingPlotter Pro allows you to graph jitter correlated with the time graph. High jitter can lead to slow response times, poor voice quality (in Voice over IP) and other connection problems. A low jitter number is usually an indicator of a good connection. Jitter is a number that represents how stable the latency responses have been. 30% seems to work great for highlighting just the right of loss in most cases, but you’re certainly going to run into cases where you want to change this to something lower (as low as 1) or higher (any number is valid – even over 100). Most often, graphing the packet loss is a handy, easy way to see lost samples. Depending on the number of samples included in the timeline graph, all timeouts may show 100%. The red number on the right of the timeline graph is the scale of the packet loss numbers. You can change to a fixed scale in the options screen. If a fixed scale is being used, this number will always equal that scale. The "Automatically scale to individual graph sample times" will also adjust the graphs automatically - but will scale each graph individually based on the maximum response time for that hop only. This number can change (and WILL change) as new samples are received. If the "Automatically scale to last visible time graph's sample times" option is being used, then this number is the maximum response time of only the final destination's sample set. The number shown here indicates the graph scale, in milliseconds (1/1000th of a second). As you increase your window, though, a single bad sample can make this line stretch the scale of the graph. When showing just a few samples, this can be really handy to see the range of latencies. It may be distance (ie: speed of light latency), or it may be a problem with one router, or the connection between those routers. This line can be useful to understand how a specific hop is responding - for example, if hop 8's minimum point is significantly greater than hop 7's maximum point, then you may need to investigate what's happening between hops 7 and 8. Hide this line to keep the scale of the upper graph in better range. For a modem, 200 ms might be quite good, while for a T1, it could be considered bad. This is dependent on your expected performance. If you have a modem, you probably want to crank these numbers up a bit.Ĭhanging these values sets the Green / Yellow / Red threshold for the graphs. If you've got a T1 or a cable modem, the listed numbers are probably pretty good (you might move them down a little if you're tracing to a fast site). You'll probably want to change the numbers based on your internet connection speed. In addition, the legend on the graph screen will be updated with these number. These numbers apply to both the HOP column and the graph background. From 201 to 500 will paint yellow, and over 500 will paint red. By default, all response 200 ms and below will paint green. These boxes control the point at which the colors change. | "Display" settings control the general display format of PingPlotter’s graphs, including scaling, coloring, and other general values. This is a example of what mine looks like The best part is when you do a speed test from the Routers GUI i get a nice 160 MS ping to the speed server on ATT side.Īs for normal usage it takes a nice 5 mins to load a youtube video lol Yay for fiber Dallas has the same thing but mine is 9pm - 11PM CST i go from having a 2ms ping to google to having over 150, a trace route to Overwatch blizzard server shows a 4k ping on 3rd hop always the same hop same path same everything but if im lucky the 3rd hop latency might go back and forth between 4k and 800, it just started recently this month was solid for the last few months with no problems.
0 Comments
Leave a Reply. |