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 brandtbucher, nascheme, pablogsal, tim.peters
Date 2020-10-10.00:40:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1602290421.86.0.628218534121.issue41984@roundup.psfhosted.org>
In-reply-to
Content
> I’m just not sure I see a way to fix this without tracking them all.

IIRC we do skip the GC flags for user-created types only when the subtype is not adding new variables *and* the base class is not a GC class by itself. This includes the case with __slots__ but is not limited to. If I recall correctly, there is a bunch of metaclasses that fall into this category and some other minor things so maybe is not that bad to unconditionally make all user objects tracked.

In any case I think is prudent to run the performance test suite with PGO/LTO + CPU isolation to get an idea. Unfortinately we already have some unwanted 3.9 performance regressions of unknown origin and I would like to not add to it if we can.
History
Date User Action Args
2020-10-10 00:40:22pablogsalsetrecipients: + pablogsal, tim.peters, nascheme, brandtbucher
2020-10-10 00:40:21pablogsalsetmessageid: <1602290421.86.0.628218534121.issue41984@roundup.psfhosted.org>
2020-10-10 00:40:21pablogsallinkissue41984 messages
2020-10-10 00:40:20pablogsalcreate