[jira] [Work logged] (ARTEMIS-3051) Fix MessageReferenceImpl::getMemoryEstimate

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-3051?focusedWorklogId=547069&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-547069 ]

ASF GitHub Bot logged work on ARTEMIS-3051:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 03/Feb/21 15:29
            Start Date: 03/Feb/21 15:29
    Worklog Time Spent: 10m 
      Work Description: asfgit closed pull request #3398:
URL: https://github.com/apache/activemq-artemis/pull/3398


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 547069)
    Time Spent: 1.5h  (was: 1h 20m)

> 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: 1.5h
>  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)