20,741
edits
Howto:Disable Nasal entirely: Difference between revisions
Jump to navigation
Jump to search
no edit summary
m (→Patch: not updated/checked in a while ...) |
No edit summary |
||
| Line 7: | Line 7: | ||
| current-status=proof-of-concept (working patch) | | current-status=proof-of-concept (working patch) | ||
| developers=Hooray | | developers=Hooray | ||
| roadmap=* add a property to expose availability of the Nasal engine in the property tree | |||
* allow Nasal to be removed/added via the subsystemFactory (see [[Howto:Reset/re-init Troubleshooting]]) | |||
|motivation-body=Nasal, and particularly its garbage collector ([[How the Nasal GC works|GC]]), is known for having a certain impact on the frame rate, and frame spacing - however, there are performance issues other than [[Nasal]] code, and some Nasal related issues (e.g. poorly-written code) may contribute to masking such issues - so far, it's been impossible to easily disable Nasal (the scripting subsystem in FlightGear) entirely - the following patch makes it possible to disable Nasal completely, so that it can be eliminated from the equation altogether. This startup mode will obviously only be of interest to developers and power-users, i.e. those interested in doing regression testing (imagine running fgfs in a gdb/valgrind or [[Built-in Profiler]] session or even just viewing the [[OSG on screen stats]] without any scripting overhead), and understanding FlightGear issues (resource leaks, performance issues etc). | |motivation-body=Nasal, and particularly its garbage collector ([[How the Nasal GC works|GC]]), is known for having a certain impact on the frame rate, and frame spacing - however, there are performance issues other than [[Nasal]] code, and some Nasal related issues (e.g. poorly-written code) may contribute to masking such issues - so far, it's been impossible to easily disable Nasal (the scripting subsystem in FlightGear) entirely - the following patch makes it possible to disable Nasal completely, so that it can be eliminated from the equation altogether. This startup mode will obviously only be of interest to developers and power-users, i.e. those interested in doing regression testing (imagine running fgfs in a gdb/valgrind or [[Built-in Profiler]] session or even just viewing the [[OSG on screen stats]] without any scripting overhead), and understanding FlightGear issues (resource leaks, performance issues etc). | ||