[
https://issues.apache.org/jira/browse/ARTEMIS-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278071#comment-17278071
]
ASF subversion and git services commented on ARTEMIS-3051:
----------------------------------------------------------
Commit 9e06a0645bf11ff1bbcc4c7230db1e1138f02c73 in activemq-artemis's branch
refs/heads/master from franz1981
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=9e06a06 ]
ARTEMIS-3051 Fix MessageReferenceImpl::getMemoryEstimate
> Fix MessageReferenceImpl::getMemoryEstimate
> -------------------------------------------
>
> Key: ARTEMIS-3051
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3051
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.16.0
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Minor
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> 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.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
