Client side monitoring
From OpenSimulator
(→Ping Sim) |
(→Ping Sim) |
||
| Line 20: | Line 20: | ||
If the simulator is on the same computer as the viewer, then you would expect to see a ping time of approximately 10-25 ms. If the simulator is remote, then ping times will be a lot longer as the packet traverses the network. | If the simulator is on the same computer as the viewer, then you would expect to see a ping time of approximately 10-25 ms. If the simulator is remote, then ping times will be a lot longer as the packet traverses the network. | ||
| − | If ping time varies significantly (e.g. by 100s of ms) or is consistently higher than one would expect then this may indicate an extremely over-loaded simulator or network problems/high latency between the viewer and the simulator. | + | If ping time varies significantly (e.g. by 100s of ms) or is consistently higher than one would expect then this may indicate an extremely over-loaded simulator or network problems/high latency between the viewer and the simulator. However, ping can sometimes also leap up if the viewer is overloaded (and hence taking more time than usual to process incoming data). |
= Texture Console = | = Texture Console = | ||
Revision as of 15:54, 23 October 2013
Contents |
Introduction
This page refers to monitoring facilities that are typically present on a viewer. These are not directly connected with OpenSimulator.
Please add more detail as necessary.
Viewer statistics
The short cut to display this window is CTRL + SHIFT + 1. This shows measures such as viewer frames per second (FPS), Total Frame Time, etc.
Information about a few of these measures is broken out below.
Ping Sim
A typical viewer will send a ping UDP packet (StartPingCheck) to the root region every 5 seconds.
The simulator will respond immediately with a CompletePingCheckPacket without going through the main packet queueing mechanism. The viewer measures the round-trip time and displays this as the Ping Sim statistic.
If the simulator is on the same computer as the viewer, then you would expect to see a ping time of approximately 10-25 ms. If the simulator is remote, then ping times will be a lot longer as the packet traverses the network.
If ping time varies significantly (e.g. by 100s of ms) or is consistently higher than one would expect then this may indicate an extremely over-loaded simulator or network problems/high latency between the viewer and the simulator. However, ping can sometimes also leap up if the viewer is overloaded (and hence taking more time than usual to process incoming data).
Texture Console
The short cut to display this is CTRL + SHIFT + 3. This will overlay a display on the viewer which details the textures being downloaded and thedownload progress. The number of textures present on the region is the number after the "Textures:" text on the third line of the display. The higher this is, the more graphics memory is required from the viewer and lower performance will be.
See http://wiki.secondlife.com/wiki/Texture_Console for more details.
References
- http://community.secondlife.com/t5/English-Knowledge-Base/How-to-improve-Viewer-performance/ta-p/1316923 - more information on how to improve performance on the viewer-side.
