16 per node doesn't sound correct. I can see 1 per node for the child map, as well as
another one for the locks, but that's about it. You must remember though that this is
per NODE - so an Fqn like /a/b/c involves 3 nodes.
A lot of this stuff is due for major improvements in JBC 3.x where there won't be a
CHM per node for locks, just one for children.
Perhaps the CHMs you see are uncollected objects? Does your app frequently create and
delete nodes? Does this change significantly after a System.gc() call?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161727#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...