-
1. Re: Bean objects representing interceptors, decorators and producer methods
nickarls Nov 18, 2009 8:32 PM (in response to asookazian)Javassist is used for the proxies in Weld. The performance overhead should be negligable (haven't seen any benchmarks, though. More of an annoyance when debugging). It's not about patterns, it's the way to do it if you aren't AOP:ing
-
2. Re: Bean objects representing interceptors, decorators and producer methods
swd847 Nov 18, 2009 9:14 PM (in response to asookazian)The biggest performance impact from proxies that I have seen comes on container startup when the proxies are being generated, this is why seam takes quite a while to start when you have several hundred components.
-
3. Re: Bean objects representing interceptors, decorators and producer methods
nickarls Nov 19, 2009 8:51 AM (in response to asookazian)Yes, and I think there could be optimizations done here, too (pooling, ordering, background processing - whatever)
It would be cool experiment, determine the ordering of beans, start a queue in the background and if something is needed right away, override it and process it immediately ;-) Well, perhaps not...
-
4. Re: Bean objects representing interceptors, decorators and producer methods
asookazian Nov 19, 2009 6:26 PM (in response to asookazian)
Stuart Douglas wrote on Nov 18, 2009 21:14:
The biggest performance impact from proxies that I have seen comes on container startup when the proxies are being generated, this is why seam takes quite a while to start when you have several hundred components.Performance hits on app server startup are typically not a big concern (but perhaps it depends on the size of the cluster).
I'm more concerned with performance hit in runtime. But maybe it's negligible cost...