20,741
edits
FGAIS: Difference between revisions
Jump to navigation
Jump to search
→Possible Optimizations
| Line 83: | Line 83: | ||
* Use pointers / const references | * Use pointers / const references | ||
* Implement real copy constructors | * Implement real copy constructors | ||
* | * use a faster string implementation | ||
* Use a faster map implementation, i.e. unordered_map or something from boost (speed-up 2x-3x) | * Use a faster map implementation, i.e. unordered_map or something from boost (speed-up 2x-3x) | ||
* Use a spatial data structure (i.e. quadtree) to partition the space and only look up relevant aircraft | * Use a spatial data structure (i.e. quadtree) to partition the space and only look up relevant aircraft | ||
* also use the aircraft's current position, heading and FOV to determine highly relevant aircraft | * also use the aircraft's current position, heading and FOV to determine highly relevant aircraft | ||
* Provide support for multiple update/output threads to update fgfs clients in a handful of worker threads | |||
* run list cleanup (expired aircraft) in another worker thread | * run list cleanup (expired aircraft) in another worker thread | ||
* don't send positions but derivative information and compute positions at the client side (also requires changes in fgfs) | * don't send positions but derivative information and compute positions at the client side (also requires changes in fgfs) | ||