Author vstinner
Recipients nedbat, pitrou, r.david.murray, serhiy.storchaka, vstinner
Date 2013-10-08.21:47:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1381268823.28.0.572036685667.issue19199@psf.upfronthosting.co.za>
In-reply-to
Content
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?
History
Date User Action Args
2013-10-08 21:47:03vstinnersetrecipients: + vstinner, pitrou, nedbat, r.david.murray, serhiy.storchaka
2013-10-08 21:47:03vstinnersetmessageid: <1381268823.28.0.572036685667.issue19199@psf.upfronthosting.co.za>
2013-10-08 21:47:03vstinnerlinkissue19199 messages
2013-10-08 21:47:03vstinnercreate