From: Harald Wellmann <harald.wellmann_at_gmx.de>
Date: Thu, 04 Nov 2010 16:49:26 +0100

CDI in Glassfish (i.e. Weld) is known to have a severe memory leak,
which has already been discussed on this list (see also
https://glassfish.dev.java.net/issues/show_bug.cgi?12368).

But apart from the leak on redeployment, even the basic footprint of
Weld is excessive: In my application, 50 % of heap memory is claimed by
Weld.

I've just filed a bug on this
https://glassfish.dev.java.net/issues/show_bug.cgi?id=14419, and some
more background can be found in my blog:

http://hwellmann.blogspot.com/2010/11/cdi-major-risk-factor-in-java-ee-6.html

I would love to get your feedback on this:

- Do you see a similar amount of memory used by Weld in your applications?

- Are you willing to double your RAM requirements just for using CDI?

- Is there any chance for Weld reaching production quality before the
Glassfish 3.1 release?

- What is the post-3.1 perspective for CDI support in Glassfish?

Best regards,
Harald