[jboss-dev-forums] [JBoss Microcontainer Development] New message: "Re: CallbackItem.changeCallback() very expensive due to context tracking"
JBoss development,
A new message was posted in the thread "CallbackItem.changeCallback() very expensive
due to context tracking":
http://community.jboss.org/message/527859#527859
Author : Kabir Khan
Profile : http://community.jboss.org/people/kabir.khan@jboss.com
Message:
--------------------------------------------------------------
alesj wrote:
Yeah, I think it you're right.
Since, if the context/scopeInfo's scope key doesn't include certain scope level,
looking additioanlly with C doesn't really help -- same result as with B.
e.g. B's MetaData is just a collection of Cs
I tried in AS and it does not go through to the expensive bit after the first few beans of
the bootstrap (probably the ones installed before the context tracker). I've removed
that code anyway and committed against https://jira.jboss.org/jira/browse/JBKERNEL-102
alesj wrote:
For ContextTracker retrieval, this should only be called once, as we should get the CT on
the first call.
(CT is setup in AS -- see kernel.xml, but not by default for MC tests)
It looks like the initial call is expensive, but necessary, so my benchmarks are
not realistic in this case. I put in some log statements and we do get some multiple calls
to scopeInfo.getMetaData() instances but the overhead is low, total of 6ms on AS startup
so there is no point in caching.
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/527859#527859