Re: [weld-dev] A significantly negative article on Weld

I just ran some very quick and dirty profiling with the latest Jbossas and the results are as follows: Beans Startup Time Startup (WELDX) Memory Usage Mem Usage(no beans.xml) No Deployment 17 135 20 20 22 149 500 24 26 178 2000 35 43 265 5000 87 104 440 210 So jboss uses 135Mb normally, and 210Mb when a war with 5000 classes is deployed that does not have beans.xml. When you add weld to the mix the memory usage jumps by 230Mb to 440Mb. According to yjp WeldClassImpl (and it's retained WeldMethod/Field etc) is responsible for 120Mb of this. Other major culprits seem to be TypeSafeObserverResolver at 24Mb (as it is caching ProcessAnnotatedType<Bean*> * 5000) and TypeSafeDecoratorResolver at 13Mb. Not much else stands out. The beans used where quite simple (1 injection point, 7 fields, 6 methods), no normal scoped beans, no interceptors, not decorators. Weldx does have a notable effect on startup time, which I will also investigate. I don't think it will be to hard to significantly reduce this. Reducing the number of HashMap's in WeldClassImpl (and replacing some with ImmutableArraySet) should give a significant gain, and clearing the TypeSafeObserverResolver and TypeSafeDecoratorResolver after startup should also save around 40Mb. I'll try and do some work this week and see how much I can get this down. Stuart On 10/11/2010, at 8:48 AM, Pete Muir wrote: