[jira] [Closed] (ARTEMIS-4065) Improving Page Counting by using real records, and not use the journal extensive for every message sent

["Clebert Suconic (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clebert Suconic closed ARTEMIS-4065.
------------------------------------
    Resolution: Fixed

> Improving Page Counting by using real records, and not use the journal extensive for every message sent
> -------------------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4065
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4065
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>            Priority: Major
>             Fix For: 2.28.0
>
>          Time Spent: 4h 20m
>  Remaining Estimate: 0h
>
> Paging will now keep a single record in the journal for every destination paged. 
> Once the system is paging, the system will update the record every minute (hard coded timeout), and once the server is shutdown.
> Every time the broker starts, we will swipe the paged messages in parallel. While the page-counters are being rebuild we will serve the counter based on the previously recorded journal (before the restart).
> The rebuild counter will shortly disable removing paged files while messages are being counted. We will save a snapshot position up to a positionN, and read all messages until that positionN.
> we will then merge the read counters with a snapshot between positionN and newly sent messages.
> This will allow using less records in the journal to keep the message counters boosting paging performance.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)