[ARTEMIS-4056] Optimize Paging Startup And Management operation

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.27.0
• Assignee: Unassigned
• Reporter: Clebert Suconic
• Created: 18/Oct/22 03:33
• Updated: 09/Nov/22 01:28
• Resolved: 09/Nov/22 01:28

Description

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.

Issue Links

• links to: GitHub Pull Request #4260