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 16:09, 12 February 2012
, 12 February 2012→The system monitor
| Line 32: | Line 32: | ||
** 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). | ** 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). | ||
** The GUI system is another subsystem which may trigger Nasal hooks | ** The GUI system is another subsystem which may trigger Nasal hooks | ||
** While it is true that the Nasal garbage collector has been shown to cause occasional stuttering under certain circumstances, the system monitor in its current form is '''not''' suitable to tell you the difference between a badly coded "rogue" script causing stutter or the stuttering being really caused by the GC. Also, it is worth noting that following good coding practices may actually help decrease the overall pressure on the GC, i.e. by keeping the number of references to be traversed low and pretty constant. | |||
* 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. | ||