This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pablogsal
Recipients nanjekyejoannah, nascheme, pablogsal, tim.peters
Date 2019-12-28.19:38:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1577561911.64.0.981947970193.issue39143@roundup.psfhosted.org>
In-reply-to
Content
> 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.
History
Date User Action Args
2019-12-28 19:38:31pablogsalsetrecipients: + pablogsal, tim.peters, nascheme, nanjekyejoannah
2019-12-28 19:38:31pablogsalsetmessageid: <1577561911.64.0.981947970193.issue39143@roundup.psfhosted.org>
2019-12-28 19:38:31pablogsallinkissue39143 messages
2019-12-28 19:38:31pablogsalcreate