You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/05/28 12:39:00 UTC
[jira] [Commented] (QPID-7830) [Broker-J] Heap dominated by
duplicates of common routing values / header values etc
[ https://issues.apache.org/jira/browse/QPID-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492621#comment-16492621 ]
ASF subversion and git services commented on QPID-7830:
-------------------------------------------------------
Commit a4ade5a371eefdee764a6e13341625a945d67d1b in qpid-broker-j's branch refs/heads/7.0.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=a4ade5a ]
QPID-7830: [Broker-J] Simplify string caching functionality
(cherry picked from commit 57bda83de7fbe6291aea507b5c1098fda5cf130d)
> [Broker-J] Heap dominated by duplicates of common routing values / header values etc
> ------------------------------------------------------------------------------------
>
> Key: QPID-7830
> URL: https://issues.apache.org/jira/browse/QPID-7830
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Reporter: Keith Wall
> Assignee: Alex Rudyy
> Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
> Attachments: 0001-QPID-7830-Broker-J-Simplify-string-caching-functiona.patch
>
>
> When used for store and forwarding, in some use cases the Broker's heap can become dominated by duplicates of common values such as routing information (e.g. {{amq.direct}} or an application's queue name) or common header values (e.g a application/octet-stream or an application's user id).
> On the 0-8..0-91 paths, every enqueued message gets its own {{MessagePublishInfo}} referencing its own {{AMQShortString}} exchange and routing keys. For some use-cases, these are drawn from a small set. On the AMQP 1.0 path, {{Properties#to}} is an example. 0-10 is probably affected too.
> This unnecessarily increases the heap requirements of the Broker.
> The Broker should adopt a sensible intern/caching policy with the same policy applying regardless of whether messages follow the on-line enqueue or recovery path. Note that in AMQP 1.0, values which are {{Symbols}} have their underlying String automatically interned.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org