New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tiny profiling info (Psyco #2) #37246
Comments
Psyco-friendly patch #2. A very very small statistic-collecting patch. pystate.h: added a field at the end of the int tick_counter; ceval.c: eval_frame():
The purpose is to give a useful measure of the number We can safely guess that a single integer increment |
Logged In: YES I see no harm in this. Are you sure it's actually going to be useful, though? |
Logged In: YES It is the only way I could work out so far that can (fn name) (speed-up) (bytecode insns per second) The third column is '(tick_counter * check_interval) / Note that similar information could be obtained by setting a |
Logged In: YES I'd like to get this into 2.2.2. MWH, can you check it in? |
Logged In: YES Done in Include/pystate.h revision 2.18.16.1 Armin, I don't know how you generated this patch, but it $ cvs diff Include/pystate.h Python/ceval.c > ~/diff |
Logged In: YES Uploaded the 2.3 patch (this one cleanly generated -- for the |
Logged In: YES Attached an updated diff for 2.3. This one doesn't have |
Logged In: YES I got lazy and checked in all the psyco patches at once: Include/pystate.h revision 2.21 |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: