> From: Vincent Massol [mailto:[EMAIL PROTECTED]]
>
> > -----Original Message-----
> > From: Leo Sutic [mailto:[EMAIL PROTECTED]]
> > Sent: 08 March 2002 20:01
> > To: Avalon Developers List
> > Subject: RE: Performance questions about ECM
> >
> >
> >
> > > From: Vincent Massol [mailto:[EMAIL PROTECTED]]
> > >
> > > Leo,
> > >
> > > First thanks for the quick answer.
> > >
> > > The problem with our application is that there is a very very strict
> > > requirement : 99.97% of user requests must not take longer than 1
> second
> > > (it's not a web application and we do control the maximum number of
> > > users that come in the system, lucky us !).
> >
> > OK... I would do all my lookups in compose() then, and release them in
> > dispose().
> >
>
> yep that's what we are doing everywhere. However, for the SingleThreaded
> components that are using either SingleThreaded or ThreadSafe components
> the issue is still the same (their compose() method will be called for
> every lookup of the SingleThreaded component, which will in turn do
> lookups for all dependent components).
Then, can you make the SingleThreaded component poolable? That would cut
away
most of the lookups and preserve MT-safety.
I think you are spending a lot of time constructing these single threaded
components, much more than you spend in ECM lookup.
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
