20,741
edits
Improving Nasal: Difference between revisions
Jump to navigation
Jump to search
→Performance / Optimizations
Philosopher (talk | contribs) m (→Better debugging/development support: Update on status) |
|||
| Line 139: | Line 139: | ||
* another straightforward optimization would be exposing an API to allocate new objects in a certain generation (GEN0/GEN1) to directly tell the interpreter about the object's lifetime ( until reset/reinit, until aircraft change, timer/frame based). | * another straightforward optimization would be exposing an API to allocate new objects in a certain generation (GEN0/GEN1) to directly tell the interpreter about the object's lifetime ( until reset/reinit, until aircraft change, timer/frame based). | ||
* marking/reaping could be parallelized using several threads, for each pool - by using write barriers to sync access to naRefs | * marking/reaping could be parallelized using several threads, for each pool - by using write barriers to sync access to naRefs | ||
== Expose additional threading primitives == | |||
Consider using pthreads, Nasal's threading support is extremely basic [http://plausible.org/nasal/lib.html]. | |||
[[Category:Core developer documentation]] | [[Category:Core developer documentation]] | ||
[[Category:Nasal]] | [[Category:Nasal]] | ||
[[Category:Developer Plans]] | [[Category:Developer Plans]] | ||