[ https://issues.apache.org/jira/browse/ARTEMIS-4809?focusedWorklogId=928595&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-928595 ]
ASF GitHub Bot logged work on ARTEMIS-4809: ------------------------------------------- Author: ASF GitHub Bot Created on: 02/Aug/24 21:56 Start Date: 02/Aug/24 21:56 Worklog Time Spent: 10m Work Description: joshb1050 commented on PR #4966: URL: https://github.com/apache/activemq-artemis/pull/4966#issuecomment-2266191199 @jbertram I agree, that makes sense. I have revised to `initial-queue-buffer-size` and changed usages, and also added additional context on when one might want to configure. Issue Time Tracking ------------------- Worklog Id: (was: 928595) Time Spent: 3h 20m (was: 3h 10m) > Make intermediateMessageReferences initial capacity configurable > ---------------------------------------------------------------- > > Key: ARTEMIS-4809 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4809 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker > Reporter: Josh Byster > Priority: Minor > Time Spent: 3h 20m > Remaining Estimate: 0h > > In some setups, there could be a few hundred thousand queues that are created > due to many consumers that are connecting. However, most of these are empty > and stay empty for the entire day since there aren't necessarily messages to > be sent. > The 8K {{intermediateMessageReferences}} instantiates an 64KB buffer > ({{Object[]}}). This means we have large allocation and live heap that > ultimately remains empty for almost the entire day. > It would be quite nice if we could configure this initial size. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org For additional commands, e-mail: issues-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact