20,741
edits
Howto:Use the system monitor: Difference between revisions
Jump to navigation
Jump to search
m
Howto:Use the system monitor (view source)
Revision as of 13:15, 15 November 2015
, 15 November 2015→The system monitor: + messy quotes that should be merged/rewritten into a single message probably
m (→Interpreting the OSG on screen stats: this really needs a rewrite and should become a separate article some day...) |
m (→The system monitor: + messy quotes that should be merged/rewritten into a single message probably) |
||
| Line 7: | Line 7: | ||
[[File:System-performance-monitor-fg260.png|400px|thumb|Screen shot showing the system performance monitor available in FG 2.6.0+]] | [[File:System-performance-monitor-fg260.png|400px|thumb|Screen shot showing the system performance monitor available in FG 2.6.0+]] | ||
{{Caution| | |||
{{FGCquote | |||
|1= the built-in performance monitor, and especially the GUI (it being used in PUI/PLIB)- is adding to the performance overhead you're seeing | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=243288#p243288 | |||
| title = <nowiki>Re: FlightGear permanently damages the performance of comput</nowiki> | |||
| author = <nowiki>Hooray</nowiki> | |||
| date = May 18th, 2015 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= you will want to use the http/telnet interfaces to watch the performance stats, because the GUI dialog using PUI/Nasal is dead-slow, and even adding to the overhead you are seeing | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=264313#p264313 | |||
| title = <nowiki>Re: Su-15</nowiki> | |||
| author = <nowiki>Hooray</nowiki> | |||
| date = Nov 13th, 2015 | |||
}} | |||
{{FGCquote | |||
|1= "events" is the subsystem that triggers/runs Nasal timers, and any Nasal code (anywhere), may trigger the GC (garbage collector) - to see if that's the case, you can use the "GC tracker" patch in the sigar code we have. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=258607#p258607 | |||
| title = <nowiki>Re: How to tell if you are CPU or GPU limited (split)</nowiki> | |||
| author = <nowiki>Hooray</nowiki> | |||
| date = Sep 23rd, 2015 | |||
}} | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= You can get pretty accurate stats using the performance monitor - it will write everything to the property tree. To see for yourself, open the performance monitor dialog and then use the property browser to watch the performance monitor branch in the property tree, you can learn more by inspecting $FG_ROOT/Nasal/performance_monitor/monitor.nas | |||
As you can see there, the switch for enabling the monitor is /sim/performance-monitor/enabled (bool) | |||
This will work regardless of the PUI dialog, and you can view/access all stats (for each subsystem!) without showing the PUI dialog (=better performance) | |||
For a list of subsystems, go to /sim/performance-monitor/subsystems | |||
Note that you can also use the http (browser) or telnet protocols to do this while extending the logging protocol | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=258579#p258579 | |||
| title = <nowiki>Re: How to tell if you are CPU or GPU limited (split)</nowiki> | |||
| author = <nowiki>Hooray</nowiki> | |||
| date = Sep 23rd, 2015 | |||
}} | |||
}} | |||
}} | |||
In FlightGear >= 2.6.0, use the menu option '''Debug''' => '''Monitor System Performance''' to analyze stutters. | In FlightGear >= 2.6.0, use the menu option '''Debug''' => '''Monitor System Performance''' to analyze stutters. | ||