Difference between revisions of "Viewerhelp:Top Colliders and Top Scripts"

From Second Life Wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Help Article Ready for Review}}
{{Help Article Ready for Copy Edit}}


Shows potentially problematic {{xref|physics|physical}} or scripted objects. Many collisions and high script usage are causes of server-side {{xref|lag}}.
Shows potentially problematic {{xref|physics|physical}} or scripted objects. Many collisions and high script usage are causes of server-side {{xref|lag}}.
Line 5: Line 5:
* Normally, you don't have to worry about removing anything if performance ''feels'' fine and ''looks'' OK in the {{xref|Advanced menu|'''Advanced''' menu}}'s {{winlink|Lag Meter}}, and to a more detailed degree, {{winlink|Statistics}}.
* Normally, you don't have to worry about removing anything if performance ''feels'' fine and ''looks'' OK in the {{xref|Advanced menu|'''Advanced''' menu}}'s {{winlink|Lag Meter}}, and to a more detailed degree, {{winlink|Statistics}}.
* Only use this tool with great care after you've learned the technical aspects involved: while you can remove troublesome objects, you can also inadvertently destroy content.
* Only use this tool with great care after you've learned the technical aspects involved: while you can remove troublesome objects, you can also inadvertently destroy content.
* Since readings shown are for a brief instant in time, repeatedly click {{WebIcon_Refresh}} to observe if activity is sustaining or spurious. Particularly useful with colliders because something that's rapidly colliding at one moment may settle to rest the next.
* {{win|Top Colliders}}: Since readings shown are for a brief instant in time, repeatedly click {{WebIcon_Refresh}} to observe if activity is consistent and significant or transient and insignificant. Something that's rapidly colliding at one moment may settle to rest the next.
* {{win|Top Scripts}}: Prior to server version 11.06.17.233176 (released 2011-06-28) the times reported represent only a brief instance in time and are inaccurate. Server 11.06.17.233176 changed it so that the times reported are now the average script time per frame for the last 30 minutes for all scripts on the object. If the object has been in the region for less than 30 minutes the number reported will be the average time per frame since the object entered the region.


Click the columns to sort them in ascending or descending order.
Click the columns to sort them in ascending or descending order.
Line 12: Line 13:
| Columns
| Columns
|
|
* '''Score or Time''' - The higher, the worse, but consider it relative to the total shown in {{xref|Statistics}}.
* '''Score''' - The higher, the worse, but consider it relative to the total shown in {{xref|Statistics}}. Only shown in {{win|Top Colliders}}
* '''Time''' - The total average script time per frame over the last 30 minutes for all scripts in the object. Only shown in {{win|Top Scripts}}.
* '''Name''' - The object's name.
* '''Name''' - The object's name.
* '''Owner''' - The Resident who owns the object; if the owner is unfamiliar and the region just started behaving slowly, it may be worth checking out.
* '''Owner''' - The Resident who owns the object; if the owner is unfamiliar and the region just started behaving slowly, it may be worth checking out.
* '''Location''' - Coordinates of where the object is located in the region.
* '''Location''' - Coordinates of where the object is located in the region.
* '''Time''' - When the object was rezzed inworld. Older objects are more likely to be intended to stay.
* '''Time''' - When the object was rezzed inworld. Older objects are more likely to be intended to stay.
* '''Mono Time''' - {{redbug|Not completely implemented yet, check with Team Blighty}} Only shown in {{win|Top Scripts}}.
* '''Mono Time''' - The amount of time spent specifically running scripts compiled to Mono. Only shown in {{win|Top Scripts}}.
* '''URLs''' - Which URLs are being used per the [https://wiki.secondlife.com/wiki/LSL_http_server LSL HTTP server]. Only shown in {{win|Top Scripts}}. {{redbug|BROKEN per [https://jira.secondlife.com/browse/VWR-15163 VWR-15163]}}.}}
* '''URLs''' - Which URLs are being used per the [https://wiki.secondlife.com/wiki/LSL_http_server LSL HTTP server]. Only shown in {{win|Top Scripts}}.}}


{{UIref
{{UIref

Latest revision as of 14:07, 18 October 2011

KBnote.png Note: This article is ready for copy editing.

Shows potentially problematic physical or scripted objects. Many collisions and high script usage are causes of server-side lag.

  • Normally, you don't have to worry about removing anything if performance feels fine and looks OK in the Advanced menu's Lag Meter, and to a more detailed degree, Statistics.
  • Only use this tool with great care after you've learned the technical aspects involved: while you can remove troublesome objects, you can also inadvertently destroy content.
  • Top Colliders: Since readings shown are for a brief instant in time, repeatedly click to observe if activity is consistent and significant or transient and insignificant. Something that's rapidly colliding at one moment may settle to rest the next.
  • Top Scripts: Prior to server version 11.06.17.233176 (released 2011-06-28) the times reported represent only a brief instance in time and are inaccurate. Server 11.06.17.233176 changed it so that the times reported are now the average script time per frame for the last 30 minutes for all scripts on the object. If the object has been in the region for less than 30 minutes the number reported will be the average time per frame since the object entered the region.

Click the columns to sort them in ascending or descending order.

Columns

 
  • Score - The higher, the worse, but consider it relative to the total shown in Statistics. Only shown in Top Colliders
  • Time - The total average script time per frame over the last 30 minutes for all scripts in the object. Only shown in Top Scripts.
  • Name - The object's name.
  • Owner - The Resident who owns the object; if the owner is unfamiliar and the region just started behaving slowly, it may be worth checking out.
  • Location - Coordinates of where the object is located in the region.
  • Time - When the object was rezzed inworld. Older objects are more likely to be intended to stay.
  • Mono Time - The amount of time spent specifically running scripts compiled to Mono. Only shown in Top Scripts.
  • URLs - Which URLs are being used per the LSL HTTP server. Only shown in Top Scripts.
Object ID

  The object's UUID.
Show Beacon

  Select an object in the list, then click Show Beacon to visually pinpoint the object's Location as shown above.
Object Name

Owner

  For each of these, type in a specific name, then click Filter to only show matching results. Partial searches work: "car" shows objects named "red car".

  Refreshes the list.
Return Selected

  Returns the selected object in the list to its owner. Be careful, there's no confirmation.
Return All

  Returns all objects in the list to their owners. Asks for your confirmation; there's no undo.
Disable Selected

  Disables physics (for colliders) or scripts (for scripted objects) for the selected object in the list.
Disable All

  Turns off all physics or scripts in objects in the list. Asks for your confirmation; there's no undo.

For more tips and tricks, see Region Performance.