20,741
edits
Nasal GC Musings: Difference between revisions
Jump to navigation
Jump to search
→Problem
No edit summary |
|||
| Line 9: | Line 9: | ||
=== Problem === | === Problem === | ||
In a flight simulator like FlightGear, the frame rate and latency of the graphics engine are critical to the user experience. If the frame rate is too low or the latency is too high, the simulator will feel sluggish and unresponsive, making it difficult to control the aircraft accurately. | |||
When the garbage collector in Nasal runs for a long time, it can cause frame rate and latency issues, which can have adverse consequences for users during critical phases of a flight. For example, during takeoff or landing, the simulator may feel unresponsive, making it difficult to control the aircraft accurately. This can be particularly problematic when attempting carrier approaches or takeoff/landing on an aircraft carrier, where precise control is essential. | |||
Overall, long garbage collection runs can have serious impacts on the performance and usability of a flight simulator, especially during critical phases of a flight. It is important to address these issues to ensure that the simulator remains responsive and usable at all times. | |||
Over the years, Nasal has received criticism for its garbage collection implementation, as it has been linked to performance issues in FlightGear. However, this criticism ignores the fact that Nasal is just one part of the FlightGear system, and that other subsystems have also contributed to performance issues and resource leaks in the past. | Over the years, Nasal has received criticism for its garbage collection implementation, as it has been linked to performance issues in FlightGear. However, this criticism ignores the fact that Nasal is just one part of the FlightGear system, and that other subsystems have also contributed to performance issues and resource leaks in the past. | ||