mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-11-11 14:44:57 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 8

Bug #1066607: "Limitations" section of profiler docs is incorrect

Browse source
This commit is contained in:
Raymond Hettinger 2004-12-19 20:31:46 +00:00
parent 3a4231dd74
commit da264121f4
1 changed files with 1 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

11
Doc/lib/libprofile.tex
View file

@ -528,16 +528,7 @@ ordering are identical to the \method{print_callers()} method.
\section{Limitations \label{profile-limits}} \section{Limitations \label{profile-limits}}
There are two fundamental limitations on this profiler. The first is One limitation has to do with accuracy of timing information.
that it relies on the Python interpreter to dispatch \dfn{call},
\dfn{return}, and \dfn{exception} events. Compiled \C{} code does not
get interpreted, and hence is ``invisible'' to the profiler. All time
spent in \C{} code (including built-in functions) will be charged to the
Python function that invoked the \C{} code. If the \C{} code calls out
to some native Python code, then those calls will be profiled
properly.
The second limitation has to do with accuracy of timing information.
There is a fundamental problem with deterministic profilers involving There is a fundamental problem with deterministic profilers involving
accuracy. The most obvious restriction is that the underlying ``clock'' accuracy. The most obvious restriction is that the underlying ``clock''
is only ticking at a rate (typically) of about .001 seconds. Hence no is only ticking at a rate (typically) of about .001 seconds. Hence no