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 Mark.Shannon
Recipients Mark.Shannon
Date 2021-12-14.16:17:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1639498673.65.0.709719181358.issue46072@roundup.psfhosted.org>
In-reply-to
Content
By "stats" I mean the internal numbers gathered by the VM for performance and debugging. This has nothing to do with any statistics module.

Currently various parts of the VM gather stats: the GC, dicts, the bytecode interpreter, type lookup cache, etc.

These stats have various compile time flags to turn them on and off. They have differing ways to display the stats, and no unified way to gather stats across different runs.

For the specialization stats we dump stats, which we can parse to collate stats across runs.

We should:
1. Add a --with-pystats config flag (like with-pydebug) to turn on stat gathering at build time.
2. Convert the other stats to the format used by the specialization stats, so all stats can be parsed and collated.
History
Date User Action Args
2021-12-14 16:17:54Mark.Shannonsetrecipients: + Mark.Shannon
2021-12-14 16:17:53Mark.Shannonsetmessageid: <1639498673.65.0.709719181358.issue46072@roundup.psfhosted.org>
2021-12-14 16:17:53Mark.Shannonlinkissue46072 messages
2021-12-14 16:17:53Mark.Shannoncreate