Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

Difference between revisions of "Nasal performance and benchmarks"

From FlightGear wiki
Jump to: navigation, search
m (References: link to original Nasal regression tests (Andy Ross): https://github.com/andyross/nasal/tree/master/misc)
m (Articles: yet another one)
Line 26: Line 26:
* [[Feature Scaling]]
* [[Feature Scaling]]
* [[Built-in Profiler]]
* [[Built-in Profiler]]
* [[Resource Tracking for FlightGear]]
=== See also ===
=== See also ===

Revision as of 12:08, 22 January 2019

This article is a stub. You can help the wiki by expanding it.

This article shall collect best practices for coding in Nasal based on regular performance tests.


Over the years many things have been improved so some old findings regarding performance are not true anymore. Regular benchmarking and updating should help the FlightGear community to have a clear picture of which code constructs perform well. Sometimes performance and "good" coding style (e.g. readability, re-usability, maintainability) might be in conflict.

Benchmark add-on

The benchmark add-on will be published here. It is basically a collection of nasal snippets to be tested.

Performance analysis


to be written



Regression tests


See also