[jira] [Work logged] (ARTEMIS-4056) Optimize Paging Startup And Management operation

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

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

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

                Author: ASF GitHub Bot
            Created on: 18/Oct/22 03:35
            Start Date: 18/Oct/22 03:35
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic opened a new pull request, #4260:
URL: https://github.com/apache/activemq-artemis/pull/4260

   - optimize startup time on paging (check-depage on startup)
   - otpimize getNextPage() on complete pages
   - optimize getFirstMessage() and paging. (avoid iterator usage)




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

            Worklog Id:     (was: 817862)
    Remaining Estimate: 0h
            Time Spent: 10m

> Optimize Paging Startup And Management operation
> ------------------------------------------------
>
>                 Key: ARTEMIS-4056
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4056
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Clebert Suconic
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When there are a lot of queues paging, there are a few issues:
> - A few management operations are calling iterator(); and flushExecutors(). What may put the server down.
> - Paging is eventually reading pages even when they are complete (to just discard their value, when there is a page-complete record).
> - Paging is calling checkDepage() during reload, what will eventually delay startup time.
> - The main one: getFirstMessage() on QueueControl is calling an iterator(); Such iterator might put a lot of pressure in paging. (Imaging if you had 100 queues in a paged address. all of them would be issuing the iterator().
> Tests are optimizations and the servers should just behave the same without them.



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