20,741
edits
How the Nasal GC works: Difference between revisions
Jump to navigation
Jump to search
m
→Problem
m (→Objective) |
m (→Problem) |
||
| Line 6: | Line 6: | ||
= Problem = | = Problem = | ||
The current Nasal garbage collector (GC) is known to influence the frame rate in FlightGear and occasionally cause stutter under certain circumstances. This is largely attributed to it being a fairly simple sequential mark/sweep collector, which needs to stop all operations, mark all reachable objects and free unreachable objects in an exclusive, single-threaded, fashion. | The current Nasal garbage collector (GC) is known to influence the frame rate in FlightGear and occasionally cause stutter under certain circumstances. This is largely attributed to it being a fairly simple sequential mark/sweep collector, which needs to stop all operations, mark all reachable objects and free unreachable objects in an exclusive, single-threaded, fashion. | ||
In other words, the time spent in the GC is proportial to the number of active objects, even for objects which may not be running - just loaded. | |||
= Pool storage = | = Pool storage = | ||