cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Royal <>
Subject Re: Displaying status (was Re: Cocoon 2 RC2 performance disappointment)
Date Mon, 26 Nov 2001 17:48:33 GMT
On Monday 26 November 2001 12:31 pm, you wrote:
> > * Run in debug mode and look for "decomissioning instance of" messages.
> > That means that an object pool's maximum size is not large enough and it
> > has turned into a factory. Creating & destroying objects for each request
> > *kills* performance.
> It would be cool if status page can display for each pool the current
> size, the
> max size and the max number of instance created over the pool-size.
> I can try to code this but I don't know where I should do that. Pools
> are part
> of Avalon ?

I don't know if there is a way to externally query a Pool to see its 
statistics, that's a Berin question. I know there was work on some sort of 
resource monitoring framework for Avalon that I belive would assist greatly 
in such a task.

> > * Watch the cachability in logs, and make sure things are being fed from
> > the cache.
> Same problem, where are classes about caching ? I want to display what
> is in
> the cache and the number of hit for each one.

You want to be looking at the debug output from the CachingEventPipeline and 
the CachingStreamPipeline. Unfortunately it does not keep statistics on the 
cache hit rate, but if you look at the debug output you can see if it did 
pick up on the cached content or not.

One bug I noticed with the MRUMemoryStore writing objects out to disk is that 
the generated filename can be longer than the OS supports if you have a deep 
pipeline. (I haven't had time to write a patch to make it do directories yet)

> > On a side note, we deployed our Cocoon-based application at our first
> > customer last week and it all went very smoothly! Kudo's to the dev team
> > for making such a solid product :)
> Great ! Which Servlet engine are you using ? What is the load ?

Tomcat 3.2.1. Its an intranet application with 20-something users I think. 
I'm not sure how heavily they are using it yet though as they are still 
transitioning from their old system. I am susposed to get a copy of the logs 
at some point so I can comb through them and make sure nothing unexpected 
happened. I'll post once I get some hard statistics.
peter royal ->

To unsubscribe, e-mail:
For additional commands, email:

View raw message