A document has been updated:
http://cocoon.zones.apache.org/daisy/legacydocs/569.html
Document ID: 569
Branch: main
Language: default
Name: Cocoon Profiler (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 1/10/07 4:59:24 AM
Updated by: Lars Huttar
A new version has been created, state: draft
Parts
=====
Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name: (unchanged)
Size: 6942 bytes (previous version: 6746 bytes)
Content diff:
(23 equal lines skipped)
profiling tool to analyze them.</p>
<p>The Cocoon samples include a demonstration of the profiler. It can be
found
--- below "Block samples".</p>
+++ under "Block samples" at
<tt>http://localhost/samples/blocks/profiler/</tt>.</p>
<h1>Usage</h1>
<p>To use the profiler, two things need to be done:</p>
<ul>
--- <li>Configure profiling pipeline implementations</li>
+++ <li>Declare profiling pipeline implementations</li>
<li>Add matchers to generate the profiler information</li>
</ul>
--- <h2>Change pipeline implementation</h2>
+++ <h2>Declare profiling pipeline implementations</h2>
<p>First, check that the profiling pipeline implementations (caching and/or
noncaching) are declared in the map:components section of the sitemap. (As
of
(53 equal lines skipped)
the Cocoon distribution under samples/blocks/profiler/. (Or use
<tt>src="context://samples/blocks/profiler/profile2page.xsl"</tt>.)</p>
--- <p>Note that the <a href="../profile-generator.html">profile generator</a>
will
--- generate somewhat different information depending on the presence of request
--- parameters (see below for info).</p>
+++ <p>Note that the
+++ <a
href="../sitemap-components/generators/optional/profile-generator.html">profile
+++ generator</a> will generate somewhat different information depending on the
+++ presence of request parameters (see below for info).</p>
<p>You also need the pretty-content view (which is included in the default
Cocoon sitemap). It can be added in the map:views section of the sitemap as
(11 equal lines skipped)
<p>Now you are ready to use the profiler. First make a series of requests
on the
pages you want to profile, then go look at the profiler results by
requesting
--- the profile.html page. (This can be easily seen by visiting the profiler
sample
--- block, at <tt>http://localhost/samples/blocks/profiler/profile.html</tt>.
Adjust
--- to suit your installation.) You can add the <tt>cocoon-view=content</tt>
--- request parameter to see the raw XML output.</p>
+++ the profile.html page. These request URIs and their results can be easily
seen
+++ by visiting the profiler sample block, at
+++ <tt>http://localhost/samples/blocks/profiler/profile.html</tt>. (Adjust the
+++ hostname and port to suit your installation.) You can add the
+++ <tt>cocoon-view=content</tt> request parameter to see the raw XML
output.</p>
<ul>
<li><tt>profile.html</tt>: generate a report of all pipelines profiled so
far;
(12 equal lines skipped)
</ul>
<p>For more details about the request parameters taken by the profile
generator,
--- and its XML output, see <a href="../profile-generator.html">profile
+++ and its XML output, see
+++ <a
href="../sitemap-components/generators/optional/profile-generator.html">profile
generator</a>.</p>
<h1>Notes</h1>
<ul>
--- <li>The profiler is contained in a seperate Cocoon block,
+++ <li>The profiler is contained in a separate Cocoon block,
<tt>samples/blocks/profiler</tt>. Unless you have deactivated it, it is
included
in the standard build.</li>
<li>If you are streaming very large documents through the pipeline, the
profiler
(11 equal lines skipped)
