Actually all CDI containers use proxies for NormalScoped beans. This is mandated by the spec. We also only cache 1 instance for all ApplicationScoped proxies of the same type. So I profiled (using YourKit profiler) that OWB allocates WAY less temporary objects - what results in a fraction of the gc utilisation of other CDI containers.
Of course this is only at runtime. I did not yet focus much on startup for my optimisations. I think OWB still can get heavily improved in the area of CDI events for example. But OWB is a fun project of a few spare time hackers without any big $Co backing it, so please feel free to get involved ;) LieGrue, strub > On Tuesday, 21 October 2014, 12:27, Daniel Kasmeroglu > <[email protected]> wrote: > > A missing point: > > * Since the container is using proxies to improve the performance it's > necessary to take the additional memory cost into account. Especially > the ratio between performance gain and memory cost. If the memory costs > are too high it might backfire on systems with low memory due to things > like paging etc. Although I doubt that telling from my experience the > JBoss server is a cheaper choice here ;-) > > > > Best regards > > Daniel Kasmeroglu >
