[jboss-dev] M2 Boot time

[Brian Stansberry]

On 02/11/2010 09:33 AM, Rémy Maucherat wrote:
> On Thu, Feb 11, 2010 at 3:54 PM, Jaikiran Pai<jpai at redhat.com>  wrote:
>> Did a quick round of profiling. Now that the admin-console deployment is
>> lazy and separate from the server bootup, it was easier to find out
>> what's taking time.
>>
>> For first access (*not* the login), turns out, the WARAnnotationDeployer
>> spends almost 41 % percent of the time processing the war - mainly in
>> getClasses() which starts looking for classes in the war file for
>> annotation scanning. The admin-console.war/WEB-INF/lib has jar totaling
>> to10 MB in size. I remember, there was discussion to add
>> metadata-complete, to the web.xml of this war. I don't see it in the
>> web.xml. Also, adding that hadn't shown any performance improvements.
>> Looking at the WarAnnotationMetaDataDeployer.deploy(...), or other
>> methods in there, i don't see any check for metadata-complete.
>
> As previously discussed, metadata-complete cannot be used for this usage.
>

Is some kind of blunt filtering mechanism useful? A la what we do with 
JBossCustomDeployDUFilter and GenScanDeployer beans in 
metadata-deployer-jboss-beans.xml.

(Unverified assumption: WARAnnotationMetaDataDeployer doesn't need to 
process admin-console.war)


-- 
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat