[issue39143] Implementing sub-generation steps in the gc
Pablo Galindo Salgado
report at bugs.python.org
Sat Dec 28 14:38:31 EST 2019
Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:
> How many semi-spaces do you think of having in this generation? Most systems have and recommend two.
I suppose we would need to experiment, but for what I have seen I think two or three :) What do you think?
> If it is a worse tradeoff to managing steps then I would suggest to stick to the steps.
I think any memory increase that scales with the number of objects will be a big concern.
> we need to add a step and manage it which is more complex than for example when tracking ages, incase of a change we only change the age threshold which looks simpler to implement.
Exactly, but if with "tracking ages" you mean store per-object ages then the previous concern applies :( Adding sub-generation steps should not be much more complicated IMHO.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue39143>
_______________________________________
More information about the Python-bugs-list
mailing list