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, nedbat, pablogsal
Date 2021-11-29.11:37:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In our quest for performance, the performance of sys.settracing based tools has probably gotten worse.

1. How do we measure this?
2. How do fix this?

We will initially use as proxy for all sys.settracing based tools when measuring  performance.

The fix is probably to use quickening to insert a minimum set of instrumentation instructions required for tracing/profiling.
The existence of `f_trace_opcode` is a bit of a problem however, as we will have to instrument *every* instruction.

Ideally, sys.settracing based tools should be faster on 3.11 than 3.10, but at the least we should provide a simple alternative to sys.settracing that is faster.
Date User Action Args
2021-11-29 11:37:58Mark.Shannonsetrecipients: + Mark.Shannon, nedbat, pablogsal
2021-11-29 11:37:57Mark.Shannonsetmessageid: <>
2021-11-29 11:37:57Mark.Shannonlinkissue45923 messages
2021-11-29 11:37:57Mark.Shannoncreate