Date: 2005-02-25T07:30:40
Editor: NicoVerwer
Wiki: Cocoon Wiki
Page: ProfilingPipelinesWithBigSaxEventStreams
URL: http://wiki.apache.org/cocoon/ProfilingPipelinesWithBigSaxEventStreams
no comment
Change Log:
------------------------------------------------------------------------------
@@ -10,7 +10,7 @@
This error is caused by the `XMLByteStreamCompiler`, which is used to store a
compiled format of the SAX-event stream in a byte-array (I am not sure why that
is needed).
Especially when you are dealing with large documents, measuring performance
can be very important, but if the profiling pipelines give up, some other
method must be used.
-'''Warning: In the rest of this page, some ugly coding techniques are used.
+'''Warning: In the rest of this page and the accompanying attachments, some
ugly coding techniques are used.
Do not use the code given here as an example of how to program Cocoon
components.'''
Instead of one of the profiling pipelines, a normal (non-profiling, and
probably non-caching) pipeline must be used. The performance measuring is done
by a new transformer, the `LOWProfilerTransformer` (see the attachment).
@@ -52,7 +52,7 @@
</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 `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:
