[ARTEMIS-3051] Fix MessageReferenceImpl::getMemoryEstimate

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.16.0
• Fix Version/s: 2.17.0
• Assignee: Francesco Nigro
• Reporter: Francesco Nigro
• Created: 05/Jan/21 14:02
• Updated: 09/Feb/21 21:22
• Resolved: 09/Feb/21 21:22

Description

MessageReferenceImpl::memoryOffset is used on MessageReferenceImpl::getMemoryEstimate: it reports 64 bytes.

https://github.com/openjdk/jol is reporting 72 bytes for OpenJDK 64 bit using COOPS and 8 bytes alignment, that's very common, and that's a more accurate estimated footprint value.

To be honest, a full-fat 64 bit JVM would use 112 bytes instead, but that could be improved in a bigger follow-up PR using JOL on the test suite to double check footprint.

 

The interesting thing is that paging will be positively affected by this change, because the broker won't under-estimate the memory footprint of many references, triggering paging sooner.

 

Issue Links

• links to: GitHub Pull Request #3398