[ https://issues.jboss.org/browse/TEIID-2404?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2404: --------------------------------------- 4) maxReserveBytes is a working measure of how much space is left over out of the initial maxReserveKB setting after accounting for soft memory references (which aren't counted toward the activeBatchBytes) and batch overhead. So the "Amount of Memory" we believe to be in use by the buffermanager object hard/soft references (not including the memory buffer / disk) is: activBatchBytes + (initial maxReserveBytes) - maxReserveBytes However we would need to add a reference to the initial maxReserveBytes setting to compute this. reserveBatchBytes is the amount of available space (out of the initial maxReserveKB) to be reserved by running plans. This value can drop below zero as plans can force memory reservations beyond the max. So the "amount of memory that plans have requested" is: (initial maxReserveBytes) - reserveBatchBytes The object/batches represented by reserveBatchBytes may (potentially as a weak or soft reference) or may not be held by the buffermanager. There are ConcurrentBitSet's that track the blocks of memory in use. There's one for blocks and one for inodes (which is mostly negligible). So the amount of the memory buffer currently in use would be: blocksInUse.getBitsSet() * BLOCK_SIZE where the memory block size is currently fixed at 8KB. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira