159
edits
Howto:Use the system monitor: Difference between revisions
Jump to navigation
Jump to search
Howto:Use the system monitor (view source)
Revision as of 15:06, 12 February 2012
, 12 February 2012→The system monitor
| Line 21: | Line 21: | ||
* Main table shows statistics on the individual subsystems. Helps to identify how much tme certain systems currently consume, or which are responsible for jitters resulting in uneven frame rates. | * Main table shows statistics on the individual subsystems. Helps to identify how much tme certain systems currently consume, or which are responsible for jitters resulting in uneven frame rates. | ||
* A bit background on the FG subsystems may be necessary though to really judge what's going on | * A bit background on the FG subsystems may be necessary though to really judge what's going on: | ||
** For example, you'll see the "nasal" subsystem consuming almost no time at all, so it looks great. However, almost all the nasal code runs in timers, and timers are driven by the "events" subsystem. So, to judge Nasal performance, you'll mainly need to look at "events" (and yes, you'll see time being consumed and jitters being produced there, which is related due to Nasal's current MARK/SWEEP Garbage Collector implementation, i.e. see: [[Improving Nasal]]). | |||
** The "tile-manager" an "ai-model" subsystems may also contain time consumed by the Nasal engine, since each scenery tile and each AI/MP aircraft may trigger a Nasal script ("load"/"unload" hooks). | |||
* At the moment, it is unfortunately not yet possible to get timing statistics for individual Nasal scripts or sub modules, but this is something that has been requested by a number of users and so we are looking into making this possible eventually. | * At the moment, it is unfortunately not yet possible to get timing statistics for individual Nasal scripts or sub modules, but this is something that has been requested by a number of users and so we are looking into making this possible eventually. | ||