Mailing-List: contact velocity-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: velocity-dev@jakarta.apache.org
Message-ID: <003601c139ca$5051ce00$8e00a8c0@pegasusii>
From: "Attila Szegedi" <szegedia@freemail.hu>
To: <velocity-dev@jakarta.apache.org>
References: <B7C17C6E.272F%geirm@optonline.net>
 <3B9C5E7F.3DC7F06C@binarix.com>
Subject: Re: performance questions - faster Introspector
Date: Mon, 10 Sep 2001 09:29:23 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hmm. So, if I'm right you'd be happier with per-classloader dumping of
cache? (I have this already coded, but have phased it out in agreement with
Geir in spirit of the KISS principle).

Attila.

----- Original Message -----
From: "Bojan Smojver" <bojan@binarix.com>
To: <velocity-dev@jakarta.apache.org>
Sent: 2001. szeptember 10. 8:32
Subject: Re: performance questions - faster Introspector


> "Geir Magnusson Jr." wrote:
> >
> > On 9/9/01 6:09 PM, "Paulo Gaspar" <paulo.gaspar@krankikom.de> wrote:
> >
> > > Attached is a little modification to Attila's great work on the
> > > Introspector.
> > >
> > > I just gave it a little twist by keeping everything keyed by Class
> > > instead of by class name. To do it was necessary to add an extra
> > > map, but this one only gets to be used when there is a new class or
> > > when a Class Loader got dumped.
> >
> > Note, for simplicity, we are going to knock out the 'by classloader'
stuff
> > and just dump the whole pile.
>
> If Tomcat lib/apps installation of Velocity is used, then the
> Introspector cache for all apps would be cleaned out since there would
> be only one of those caches hanging around. In other words, if there are
> many applications within one Tomcat, one has to be careful about
> deployment of new classes as that might cause jerks on heavily loaded
> servers.
>
> Hmm, OK, promise to deploy only during the graveyard shift :-)
>
> Bojan
>