[
https://issues.apache.org/jira/browse/QPID-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024489#comment-16024489
]
ASF subversion and git services commented on QPID-7689:
-------------------------------------------------------
Commit 1857f0b0a74a98280bffd89a2b842ff6d9864429 in qpid-broker-j's branch
refs/heads/master from [~lorenz.quack]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=1857f0b ]
QPID-7689: [Java Broker] Cache message metadata size to avoid reloading
metadata from disk
> [Java Broker] Consider message header size where appropriate
> ------------------------------------------------------------
>
> Key: QPID-7689
> URL: https://issues.apache.org/jira/browse/QPID-7689
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: qpid-java-broker-7.0.0
>
>
> The changes introduced by QPID-7618 have the broker track the size of each
> queue including header. The new ring queue policy and producer flow
> control now consider messages sizes including header. The queue depth
> alerting and flow to disk ought to be consistent.
> Is there actually value tracking queue size and queue size including header
> separately?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]