You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2016/10/05 12:07:20 UTC
[jira] [Assigned] (QPID-6803) ByteBuffer slices/duplicates
contribute significantly to garbage overhead in busy Brokers
[ https://issues.apache.org/jira/browse/QPID-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy reassigned QPID-6803:
--------------------------------
Assignee: Keith Wall (was: Alex Rudyy)
Keith,
Could you please review the changes committed under revision [ https://svn.apache.org/r1763439 ]?
> ByteBuffer slices/duplicates contribute significantly to garbage overhead in busy Brokers
> -----------------------------------------------------------------------------------------
>
> Key: QPID-6803
> URL: https://issues.apache.org/jira/browse/QPID-6803
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Keith Wall
> Assignee: Keith Wall
> Fix For: qpid-java-6.1
>
> Attachments: 0001-QPID-6803-Use-underlying-direct-byte-buffer-for-sett.patch, 0002-QPID-6803-Use-underlying-direct-byte-buffer-for-read.patch
>
>
> Profile whilst running auto-ack/transacted test at higher messages rates shows that the garbage collection is dominated being dominated by DIrectByteBuffers resulting from slicing/duplicating.
> We could refactor QpidByteBuffer (maintaining our own remaining/capacity/limit and keeping a reference to the original buffer) ourselves to avoid this overhead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org