I believe the issue is that our EL resolver is first in the chain, so gets called every single time even if the expression does not turn out to be one that references a CDI bean. 2 million does seem like a very large number of times though.
Sincerely, Joe On Mon, Feb 22, 2010 at 3:32 PM, Mark Struberg <[email protected]> wrote: > Thanks Martin! > > And yes, this may be a problem, though not sure where it comes from ... > > :) > > LieGrue, > strub > > --- Martin Koci <[email protected]> schrieb am Mo, 22.2.2010: > > > Von: Martin Koci <[email protected]> > > Betreff: InjectionResolver.implResolveByName performance > > An: [email protected] > > Datum: Montag, 22. Februar, 2010 21:28 Uhr > > Hi, > > > > I did some profiling and YourKitProfiler always marks > > InjectionResolver.implResolveByName as hotspot. It is > > called over 2 > > mills. times per request/response. All those calls come > > from > > ELResolver.getValue() - its is a very non trivial JSF > > view so it is > > probably ok (even two milions) and in application is no CDI > > bean yet > > (all are still spring and jsf managed). > > Do you think it is a problem? > > > > Regards, > > > > Martin Kočí > > > > > > > > __________________________________________________ > Do You Yahoo!? > Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz > gegen Massenmails. > http://mail.yahoo.com >
