Ben, Thanks for your reply. The numbers in my profiling here is only the amount of memory used for the Object[] array with empty slots, I do not think it includes any objects actually referenced by the array itself. In other words, it is 13600272 bytes just for having an Object[] array of 200000 elements, even if all those elements are null.
As you could see from the stack trace where it is allocated: | EDU.oswego.cs.dl.util.concurrent.BoundedBuffer.<init>(BoundedBuffer.java:46) | org.jboss.cache.eviction.Region.createQueue(Region.java:62) | | The code at Region.java at line 62 is | nodeEventQueue_ = new BoundedBuffer(RegionManager.CAPACITY); | (RegionManager.CAPACITY is 200000 in RegionManager.java) and line 46 at BoundedBuffer.java is | array_ = new Object[capacity]; | That is where the size of 13600272 bytes is coming from, just from the empty array of new Object[capacity] but not considering any elements actually in it. (Unless if I am misinterpreting the profiler output?) Thanks, Daniel View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923428#3923428 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3923428 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
