STINNER Victor added the comment: PyThreadState.tick_counter field was added in 2002 by Armin Rigo: see issue #617311. "A very very small statistic-collecting patch. (...) The purpose is to give a useful measure of the number of interpreted bytecode instructions in a given thread."
My patch will probably break the following module :-) http://packages.ubuntu.com/fr/lucid/python-tickcount "Python C extension module giving access to the internal tickcounter of python. This is useful for certain forms of profiling or performance analysis." (But tickcounter was meanless since Python 3.2.) The PyThreadState.tick_counter field was mentionned in the following question: "Read how many Python instructions have been interpreted?" http://stackoverflow.com/questions/16437487/read-how-many-python-instructions-have-been-interpreted Should we add a new counter to count the number of executed Python instructions per thread? Or fix tick_counter? Does we really need such counter or other profilers (cProfile) are enough? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19199> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
