Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove reference to env variable PROFILE_PUBLISHER #468

Merged
merged 2 commits into from Feb 4, 2019
Merged

Remove reference to env variable PROFILE_PUBLISHER #468

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4189da5
Remove section about debuggig via Control Panel
jugmac00 Feb 3, 2019
a0abfb4
Remove reference to env variable PROFILE_PUBlISHER
jugmac00 Feb 3, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 0 additions & 5 deletions docs/zdgbook/ObjectPublishing.rst
View file
Open in desktop
Expand Up @@ -579,11 +579,6 @@ environment variables.
dialog. You can also set the realm with the '__bobo_realm__' module
variable, as mentioned previously.

- 'PROFILE_PUBLISHER' -- Turns on profiling and sets the name of the
profile file. See the Python documentation for more information
about the Python profiler.


Many more options can be set using switches on the startup script.
See the *Zope Administrator's Guide* for more information.

Expand Down
34 changes: 0 additions & 34 deletions docs/zdgbook/TestingAndDebugging.rst
View file
Open in desktop
Expand Up @@ -20,40 +20,6 @@ Zope provides debugging information through a number of sources. It
also allows you a couple avenues for getting information about Zope
as it runs.

The Control Panel
-----------------

The control panel provides a number of views that can help you debug
Zope, especially in the area of performance. The *Debugging
Information* link on the control panel provides two views, *Debugging
Info* and *Profiling*.

Debugging info provides information on the number of object
references and the status of open requests. The object references
list displays the name of the object and the number of references to
that object in Zope. Understanding how reference counts help
debugging is a lengthy subject, but in general you can spot memory
leaks in your application if the number of references to certain
objects increases without bound. The busier your site is, or the
more content it holds, the more reference counts you will tend to
have.

Profiling uses the standard Python profiler. This is turned on by
setting the 'PROFILE_PUBLISHER' environment variable before executing
Zope.

When the profiler is running, the performance of your Zope system
will suffer a lot. Profiling should only be used for short periods
of time, or on a separate ZEO client so that your normal users to not
experience this significant penalty.

Profiling provides you with information about which methods in your
Zope system are taking the most time to execute. It builds a
*profile*, which lists the busiest methods on your system, sorted by
increasing resource usage. For details on the meaning of the
profiler's output, read the `standard Python documentation
<http://www.python.org/doc/current/lib/profile.html>`_

Product Refresh Settings
------------------------

Expand Down