News for hackers. Stuff that matters.
Re:Garbage Collection for Systems Programmers by cratermoon on Saturday March 30, 2024 @12:04PM (#39876110)
In generational GCs there are two or more allocation regions. New objects are put in the "younger" generation, which is garbage collected separated from the other generations. This sort of resolves the issue of tracking individual object lifetimes by having all the short-lived objects subject to rapid GC. This means most of the effort tracking lifetimes is reserved for the fewer long-lived objects.
Re:Garbage Collection for Systems Programmers by lll-o-lll on Saturday March 30, 2024 @04:06PM (#39878145)
It’s “medium term” objects that cause all the trouble. Async operations. That’s why .net invested heavily into zero-alloc tasks, as the gc would kill scaling in async heavy code.