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
b6759533
Commit
b6759533
authored
Nov 18, 1997
by
Guido van Rossum
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clarified reference to old profiler.
Mention conversion to Perl-style regular expressions.
parent
d6ab426d
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
14 additions
and
6 deletions
+14
-6
Doc/lib/libprofile.tex
Doc/lib/libprofile.tex
+7
-3
Doc/libprofile.tex
Doc/libprofile.tex
+7
-3
No files found.
Doc/lib/libprofile.tex
View file @
b6759533
...
...
@@ -57,6 +57,9 @@ examine the results of a profile operation.
\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.
...
...
@@ -441,9 +444,10 @@ the significant entries. Initially, the list is taken to be the
complete set of profiled functions. Each restriction is either an
integer (to select a count of lines), or a decimal fraction between
0.0 and 1.0 inclusive (to select a percentage of lines), or a regular
expression (to pattern match the standard name that is printed). If
several restrictions are provided, then they are applied sequentially.
For example:
expression (to pattern match the standard name that is printed; as of
Python 1.5b1, this uses the Perl-style regular expression syntax
defined by the
\code
{
re
}
module). If several restrictions are
provided, then they are applied sequentially. For example:
\bcode
\begin{verbatim}
print
_
stats(.1, "foo:")
...
...
Doc/libprofile.tex
View file @
b6759533
...
...
@@ -57,6 +57,9 @@ examine the results of a profile operation.
\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.
...
...
@@ -441,9 +444,10 @@ the significant entries. Initially, the list is taken to be the
complete set of profiled functions. Each restriction is either an
integer (to select a count of lines), or a decimal fraction between
0.0 and 1.0 inclusive (to select a percentage of lines), or a regular
expression (to pattern match the standard name that is printed). If
several restrictions are provided, then they are applied sequentially.
For example:
expression (to pattern match the standard name that is printed; as of
Python 1.5b1, this uses the Perl-style regular expression syntax
defined by the
\code
{
re
}
module). If several restrictions are
provided, then they are applied sequentially. For example:
\bcode
\begin{verbatim}
print
_
stats(.1, "foo:")
...
...
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