You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Clebert Suconic (Jira)" <ji...@apache.org> on 2022/10/18 03:34:00 UTC
[jira] [Created] (ARTEMIS-4056) Optimize Paging Startup And Management operation
Clebert Suconic created ARTEMIS-4056:
----------------------------------------
Summary: 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
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)