[jboss-dev] Bootstrap times

Kabir Khan kabir.khan at jboss.com
Wed Sep 10 04:37:40 EDT 2008


Since AS 5 does not use load time weaving out of the box, we have not  
put much effort into optimizing that. You can however use the Include/ 
Exclude attributes of the AspectManagerService to control what is  
woven. Also, previously we matched every joinpoint of every class  
against every binding. Bindings are now classified, so for example we  
only match a constructor against bindings that could pick out a  
constructor. Flavia has written some great stuff to optimize this  
further, but it is too late for AOP 2.0.0.GA.

Apart from inspecting the classes and doing the pointcut matching the  
other main overhead will be actually modifying and compiling the  
classes using javassist.

If you're really keen, I can get some numbers for this over the next  
few weeks.

On 9 Sep 2008, at 21:32, Anil Saldhana wrote:

> Kabir,  has the load time weaving performance of aop improved? It  
> was crawling last time I looked.
>
> Kabir Khan wrote:
>> Interesting idea. AFAIK not that many people are using those  
>> aspects anyway, although I'd need to adjust the testsuite since  
>> that tests some of them
>> On 9 Sep 2008, at 17:55, Adrian Brock wrote:
>>
>>> On Tue, 2008-09-09 at 18:06 +0100, Kabir Khan wrote:
>>>> On startup, it parses and deploys the information from base-
>>>> aspects.xml. I don't really think it makes sense to look at that  
>>>> until
>>>> I have switched to use the MC based AOP deployers, for which http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173781#4173781
>>>> is the outstanding issue.
>>>
>>> I'm not saying you've got to fix it (at least no straight away ;-)
>>>
>>> I just want to understand why a deployer (which is just a bean)
>>> would take more than one second to deploy.
>>>
>>> Ideally, this reading of default configuration should be lazy.
>>> Because, if nobody uses that type of deployment they don't
>>> want to pay the startup time for having it configured.
>>>
>>> In your case, I think all the aspects in base-aspects.xml
>>> should be commented out anyway. Somebody can uncomment them
>>> when they want them.
>>>
>>> Not only would that reduce startup time, it would reduce
>>> the aspect matching time if it has less aspect definitions
>>> to check.
>>> -- 
>
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development




More information about the jboss-development mailing list