Date: 2005-02-25T07:29:01
Editor: NicoVerwer
Wiki: Cocoon Wiki
Page: ProfilingPipelinesWithBigSaxEventStreams
URL: http://wiki.apache.org/cocoon/ProfilingPipelinesWithBigSaxEventStreams
no comment
Change Log:
------------------------------------------------------------------------------
@@ -52,4 +52,37 @@
</category>
}}}
+The LOWProfilerTransformer measures the time between calls to its `setup()`
and `endDocument()` methods, which is an indication of the time spent in the
pipeline. As a bonus, LOWProfilerTransformer also attempts to measure the
amount of heap memory used by the JVM. This works most reliable if you restart
the Cocoon servlet before each call to the pipeline.
+
+The LOWProfiler results can be read with the `LOWProfilerGenerator` (see
attachment). This yields the result in a format which is very similar to what
is generated by the standard `ProfilerGenerator`, without data for the
individual pipeline components.
+An exampl eoutput is:
+
+{{{
+<profiler:profilerinfo xmlns:profiler="http://apache.org/cocoon/profiler/1.0";
+ date="Fri Feb 25 14:33:12 MET 2005">
+ <profiler:pipeline uri="/test" count="4"
+ processingTime="956" processingMemory="33376">
+ <profiler:average time="239" memory="8344" />
+ <profiler:result time="379" memory="8824" index="0" />
+ <profiler:result time="193" memory="7903" index="1" />
+ <profiler:result time="188" memory="8746" index="2" />
+ <profiler:result time="196" memory="7903" index="3" />
+ </profiler:pipeline>
+</profiler:profilerinfo>
+}}}
+
+The generator is declared as follows:
+
+{{{
+ <map:generator name="lowprofiler"
+ src="org.apache.cocoon.generation.LOWProfilerGenerator"
+ label="content" logger="lowprofiler"
+ pool-grow="4" pool-max="32" pool-min="8"/>
+}}}
+
+When it is used, it gets the location of the log-file as its src-attribute:
+
+{{{
+ <map:generate type="lowprofiler"
src="context://WEB-INF/logs/lowprofiler.log"/>
+}}}
