20,741
edits
(Mark for cleanup) |
m (→Approach: https://sourceforge.net/p/flightgear/mailman/message/27250036/) |
||
Line 22: | Line 22: | ||
it would be better to look at the performance monitor stats without using the PUI dialog, e.g. by using the httpd-based property browser or the telnet daemon (--props). | it would be better to look at the performance monitor stats without using the PUI dialog, e.g. by using the httpd-based property browser or the telnet daemon (--props). | ||
You will have to manually activate the property browser (if in doubt, refer to menubar.xml for details) | You will have to manually activate the property browser (if in doubt, refer to menubar.xml for details): | ||
Use "Debug -> Toggle Subsystem | |||
Statistics" to enable/disable. It prints min/max/average and | |||
std-deviation for each of FG's subsystems to the console. The statistics | |||
interval is configurable via /sim/timing-statistics/interval-s | |||
Since there are a lot of submodules in FG (most of them are very | |||
friendly and don't consume much time), you can restrict the output to | |||
modules exceeding a certain minimum execution time - or a certain jitter | |||
(hey!). Use /sim/timing-statistics/min-time-ms and | |||
/sim/timing-statistics/jitter-ms to configure the filters (in | |||
milliseconds, obviously). | |||
Should help finding performance and jitter issues if they were caused by | |||
one of our internal subsystems.<ref>https://sourceforge.net/p/flightgear/mailman/message/27250036/</ref> | |||
Alternatively, use the property browser, which is more lightweight than the performance monitor dialog. | Alternatively, use the property browser, which is more lightweight than the performance monitor dialog. | ||
== Motivation == | == Motivation == | ||