Client side monitoring - Revision history

Justincc: /* Active Objects */

2013-11-13T22:48:23Z

‎Active Objects

2013-11-13T22:47:17Z

‎Simulator

2013-11-13T22:39:21Z

2013-11-13T22:01:16Z

2013-10-31T20:12:24Z

‎Packet Loss

2013-10-31T20:11:53Z

‎Viewer statistics

2013-10-23T23:54:45Z

‎Ping Sim

2013-10-23T23:40:49Z

‎Ping Sim

2013-10-23T23:17:20Z

‎Ping Sim

2013-10-23T23:14:37Z

‎Viewer statistics

@@ Line 33: / Line 33: @@
 In OpenSimulator, this is currently the total number of prims that are subject to physics (i.e. two prims in a link set count as two active objects).
-On the Linden Lab grid, by contrast, this appears to be the number of linksets that are actively being physics simulated (i.e. an object that is flagged as physics but is completely at rest will not be counted).
+On the Linden Lab grid, by contrast, this appears to be the number of linksets that are actively being physics simulated (i.e. an object that is flagged as physics but is completely at rest will not be counted).  At least as of 2013-11-13, the Linden wiki page links that state this statistic records the number of objects containing scripts appears to be wrong.
 ==Time (ms)==

@@ Line 29: / Line 29: @@
 ===Objects===
 The total number of prims in the region (not linksets).
 ==Time (ms)==

@@ Line 25: / Line 25: @@
 ===Packet Loss===
 This is the percentage of all UDP packets sent from the viewer to the simulator that were not acknowledged by the simulator, indicating that they were lost.  Any packet loss is not good - a packet loss of over 10% indicates serious problems.  A high packet loss may be due to a bad network connection between your viewer and the server, problems with the viewer or overloading of the server, amongst other things.
 ==Time (ms)==

@@ Line 13: / Line 13: @@
 See also http://community.secondlife.com/t5/English-Knowledge-Base/How-to-improve-Viewer-performance/ta-p/1316923
-==Ping Sim==
+== Basic ==
 A typical viewer will send a ping UDP packet (StartPingCheck) to the root region every 5 seconds.
@@ Line 22: / Line 23: @@
 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).
-==Packet Loss==
+===Packet Loss===
 This is the percentage of all UDP packets sent from the viewer to the simulator that were not acknowledged by the simulator, indicating that they were lost.  Any packet loss is not good - a packet loss of over 10% indicates serious problems.  A high packet loss may be due to a bad network connection between your viewer and the server, problems with the viewer or overloading of the server, amongst other things.
 = Texture Console =

@@ Line 23: / Line 23: @@
 ==Packet Loss==
-This is the percentage of all UDP packets sent that were not acknowledged by the server, indicating that they were lost.  Any packet loss is not good - a packet loss of over 10% indicates serious problems.  A high packet loss may be due to a bad network connection between your viewer and the server, problems with the viewer or overloading of the server, amongst other things.
+This is the percentage of all UDP packets sent from the viewer to the simulator that were not acknowledged by the simulator, indicating that they were lost.  Any packet loss is not good - a packet loss of over 10% indicates serious problems.  A high packet loss may be due to a bad network connection between your viewer and the server, problems with the viewer or overloading of the server, amongst other things.
 = Texture Console =

← Older revision		Revision as of 20:11, 31 October 2013
Line 21:		Line 21:

	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).		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).
		+
		+	==Packet Loss==
		+	This is the percentage of all UDP packets sent that were not acknowledged by the server, indicating that they were lost. Any packet loss is not good - a packet loss of over 10% indicates serious problems. A high packet loss may be due to a bad network connection between your viewer and the server, problems with the viewer or overloading of the server, amongst other things.

	= Texture Console =		= Texture Console =

@@ Line 16: / Line 16: @@
 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.  The viewer measures the round-trip time and displays this as the Ping Sim statistic.
+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.

@@ Line 9: / Line 9: @@
 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.
-If Ping Sim time is very high or occasionally peaks, then this can indicate a poor viewer to simulator network connection.
+Information about a few of these measures is broken out below.
-See http://community.secondlife.com/t5/English-Knowledge-Base/How-to-improve-Viewer-performance/ta-p/1316923 for much more information.
+See also http://community.secondlife.com/t5/English-Knowledge-Base/How-to-improve-Viewer-performance/ta-p/1316923
 = Texture Console =