Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cocoon Wiki" for change 
notification.

The following page has been changed by StephanTeuschl:
http://wiki.apache.org/cocoon/Cocoon_3_Profiling

------------------------------------------------------------------------------
  We are about to build a suitable data structure for the profiling data, and 
we are now facing the problem that some of the data we store is redundant. This 
is because some of our aspects are very generic and intercept calls of the same 
object (e.g. a PipelineComponent) several times, storing the same information 
in several ProfilingData objects. I see no way to make the aspects more 
specific, since we have no information which servlets, sitemaps and pipeline 
components might be used and which methods are called.
  
  Measuring the runtime of servlets, sitemaps and pipeline components is now 
done at a method basis, which means that we have accurate data on the runtime 
of the intercepted methods, but no data on the runtime (lifetime) of a specific 
servlet or pipeline component.
+ 
+ === HowTo ===
+ 
+ This is a small HowTo which should help you to get the Cocoon 3 Profiling 
successfully up and running.
+ 
+ == Profiling ==
+ 
+ == Firebug ==
+ 
+ Getting the Firebug Plugin able to work is really easy. You'll need to 
install Firebug 1.4X  [[http://getfirebug.com/releases/firebug/1.4X]] and then 
install the Firebug .xpi from cocoon-profiling-firebug (opening it with Firefox 
should suffice, though). Afterwards, you should have a little bug on the bottom 
right corner of your Firefox. Clicking will open it, then you can navigate to 
the net-panel (you might want to get sure its activated) and there open up a 
request (you might need to refresh). In the request, there should be a tab 
called "Cocoon 3 Profiling", if you click it, and the Profiling Service works, 
you should now see the generated profiling data in the form of a tree.
  
  === First Examples ===