Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 96199 invoked by uid 500); 13 Sep 2002 13:12:10 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 96113 invoked from network); 13 Sep 2002 13:12:09 -0000 Date: Fri, 13 Sep 2002 15:11:59 +0200 To: cocoon-dev@xml.apache.org Subject: Re: Add support for instrumentation ? Message-ID: <20020913131159.GB9892@fztig938.bank.dresdner.net> References: <20020913111838.GB3999@fztig938.bank.dresdner.net> <3D81E13D.8050609@anyware-tech.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <3D81E13D.8050609@anyware-tech.com> User-Agent: Mutt/1.4i From: Marcus Crafter X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Fri, Sep 13, 2002 at 02:59:41PM +0200, Sylvain Wallez wrote: > Marcus Crafter wrote: > > >Hi All, > > > > Hope all is well. > > > > I've been playing around with adding excalibur instrumentation > > support to cocoon over the past couple of days > > (http://jakarta.apache.org/avalon/excalibur/instrument/index.html) > > > > The initial results look quite nice (a sample screenshot of the > > instrument client in action is available at > > http://cvs.apache.org/~crafterm/instrumentation.jpg), allowing you > > to see what's going on inside your cocoon application as it happens. > > > > Does anyone see any problems with adding this support to HEAD (or > > should I wait till after 2.1 is released) ? > > > > > > +1e1000 for HEAD now !!! > > This looks really, really cool. Yes, I think it rocks! :) > A question that customers often ask is "how can I debug or tune the > application". By combining this extra-cool instrumentation, the profiler > and captor, we're starting to have good answers. > > A question however about the cost of instrumentation : is it possible to > know if an instrument is active to avoid costly value computations, in > the same way as we test logger.isDebugEnabled() ? Yes, the instrumentation api is similar to the logkit api in that sense - AbstractInstrument (http://jakarta.apache.org/avalon/excalibur/instrument/api/org/apache/excalibur/instrument/AbstractInstrument.html) defines an isActive() method which can be tested to see if the instrument is currently being used. On top of that I've added a general 'enable-instrumentation' startup parameter which can be used to completely disable the creation of an instrument-manager if its not needed. Cheers, Marcus -- ..... ,,$$$$$$$$$, Marcus Crafter ;$' '$$$$: Computer Systems Engineer $: $$$$: ManageSoft GmbH $ o_)$$$: 82-84 Mainzer Landstrasse ;$, _/\ &&:' 60327 Frankfurt Germany ' /( &&& \_&&&&' &&&&. &&&&&&&: --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org