20,741
edits
Nasal optimisation: Difference between revisions
Jump to navigation
Jump to search
m
→Using the built in performance monitor
m (added explanation about using the built in performance monitor) |
|||
| Line 28: | Line 28: | ||
You can do this from the debug menu '''Monitor System Performance''' and currently the GUI only shows the top level. | You can do this from the debug menu '''Monitor System Performance''' and currently the GUI only shows the top level. | ||
When the performance monitor is active either by having the GUI on display or because <code>/sim/performance-monitor/enabled</code>is true overruns will be logged | When the performance monitor is active either by having the GUI on display or because <code>/sim/performance-monitor/enabled</code>is true overruns will be logged at ALRT level. An overrun is defined as exceeding<code>/sim/performance-monitor/max-time-per-frame-ms</code>). | ||
Setting <code>/sim/performance-monitor/dump-stats</code> to non-zero will cause detailed performance info will be output to the log. | Setting <code>/sim/performance-monitor/dump-stats</code> to non-zero will cause detailed performance info will be output to the log. | ||
Note that it is generally a good idea not to use the integrated UI to display these stats (aka no PUI/Canvas). Instead, consider using Phi or the telnet/props interface, so that performance isn't degraded even more by displaying all these stats via the main loop. | |||
== fdm-initialized listener == | == fdm-initialized listener == | ||