Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
6c1908d5
Commit
6c1908d5
authored
Dec 26, 2005
by
Georg Brandl
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Bug #489256: remove note about Python 1.1 profiler
parent
a2764add
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
41 additions
and
41 deletions
+41
-41
Doc/lib/libprofile.tex
Doc/lib/libprofile.tex
+41
-41
No files found.
Doc/lib/libprofile.tex
View file @
6c1908d5
...
...
@@ -55,47 +55,47 @@ examine the results of a profile operation.
\index
{
profiling, deterministic
}
\section
{
How Is This Profiler Different From The Old Profiler?
}
\nodename
{
Profiler Changes
}
(This section is of historical importance only; the old profiler
discussed here was last seen in Python 1.1.)
The big changes from old profiling module are that you get more
information, and you pay less CPU time. It's not a trade-off, it's a
trade-up.
To be specific:
\begin{description}
\item
[Bugs removed:]
Local stack frame is no longer molested, execution time is now charged
to correct functions.
\item
[Accuracy increased:]
Profiler execution time is no longer charged to user's code,
calibration for platform is supported, file reads are not done
\emph
{
by
}
profiler
\emph
{
during
}
profiling (and charged to user's code!).
\item
[Speed increased:]
Overhead CPU cost was reduced by more than a factor of two (perhaps a
factor of five), lightweight profiler module is all that must be
loaded, and the report generating module (
\module
{
pstats
}
) is not needed
during profiling.
\item
[Recursive functions support:]
Cumulative times in recursive functions are correctly calculated;
recursive entries are counted.
\item
[Large growth in report generating UI:]
Distinct profiles runs can be added together forming a comprehensive
report; functions that import statistics take arbitrary lists of
files; sorting criteria is now based on keywords (instead of 4 integer
options); reports shows what functions were profiled as well as what
profile file was referenced; output format has been improved.
\end{description}
%
\section{How Is This Profiler Different From The Old Profiler?}
%
\nodename{Profiler Changes}
%
%
(This section is of historical importance only; the old profiler
%
discussed here was last seen in Python 1.1.)
%
%
The big changes from old profiling module are that you get more
%
information, and you pay less CPU time. It's not a trade-off, it's a
%
trade-up.
%
%
To be specific:
%
%
\begin{description}
%
%
\item[Bugs removed:]
%
Local stack frame is no longer molested, execution time is now charged
%
to correct functions.
%
%
\item[Accuracy increased:]
%
Profiler execution time is no longer charged to user's code,
%
calibration for platform is supported, file reads are not done \emph{by}
%
profiler \emph{during} profiling (and charged to user's code!).
%
%
\item[Speed increased:]
%
Overhead CPU cost was reduced by more than a factor of two (perhaps a
%
factor of five), lightweight profiler module is all that must be
%
loaded, and the report generating module (\module{pstats}) is not needed
%
during profiling.
%
%
\item[Recursive functions support:]
%
Cumulative times in recursive functions are correctly calculated;
%
recursive entries are counted.
%
%
\item[Large growth in report generating UI:]
%
Distinct profiles runs can be added together forming a comprehensive
%
report; functions that import statistics take arbitrary lists of
%
files; sorting criteria is now based on keywords (instead of 4 integer
%
options); reports shows what functions were profiled as well as what
%
profile file was referenced; output format has been improved.
%
%
\end{description}
\section
{
Instant Users Manual
\label
{
profile-instant
}}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment