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 gvanrossum
Recipients BTaskaya, Mark.Shannon, eric.snow, gregory.p.smith, gvanrossum, pablogsal, rhettinger, serhiy.storchaka, terry.reedy, tim.peters
Date 2021-04-06.16:00:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1617724814.57.0.198295281984.issue43684@roundup.psfhosted.org>
In-reply-to
Content
> Interesting. What code did you use to collect statistics?

For static statistics I wrote my own script: https://github.com/python/cpython/pull/25090/files#diff-994d3592c951c78cbe71084d562590d1507ddfed767e2ec040f5e2610845a11c. I can add that to Tools permanently (I have a slightly improved version that can look for different things).

> I used patches in issue27255. Perhaps it is worth to add an optionally compiled code for collecting dynamic opcode statistics permanently.

We have that already: compile with -DDYNAMIC_EXECUTION_PROFILE -DDXPAIRS. There's a script (Tools/scripts/analyze_dxp.py) that works with such data, but it's primitive. Eric is working on improvements; I added my own hacky script to run an app and collect the data.

I collected a few different sets of statistics: static stats for the stdlib and for mypy, dynamic stats for running mypy and a few of the benchmarks in pyperformance. Eric and I have plans to do this more systematically; we'll then publish our tools and results.
History
Date User Action Args
2021-04-06 16:00:14gvanrossumsetrecipients: + gvanrossum, tim.peters, rhettinger, terry.reedy, gregory.p.smith, Mark.Shannon, eric.snow, serhiy.storchaka, pablogsal, BTaskaya
2021-04-06 16:00:14gvanrossumsetmessageid: <1617724814.57.0.198295281984.issue43684@roundup.psfhosted.org>
2021-04-06 16:00:14gvanrossumlinkissue43684 messages
2021-04-06 16:00:14gvanrossumcreate