undefined | Better HN

0 pointsBlanketLogic10y ago0 comments

Thanks.

> I've worked a lot with LispWorks and tuning the gc had the same method of programmatically calling a full GC after every N operations.

What is "full GC", here? Do you mean, even the "older" generations? (Assuming Lispworks also has generational GC a la sbcl)

In other words, Would it have helped if the implementation was a mark-compact rather than generational?

0 comments

We normally used

with the full set to nil.

j / k navigate · click thread line to collapse

0 pointsBlanketLogic10y ago0 comments

Thanks.

> I've worked a lot with LispWorks and tuning the gc had the same method of programmatically calling a full GC after every N operations.

What is "full GC", here? Do you mean, even the "older" generations? (Assuming Lispworks also has generational GC a la sbcl)

In other words, Would it have helped if the implementation was a mark-compact rather than generational?

We normally used

with the full set to nil.

j / k navigate · click thread line to collapse