[
https://issues.apache.org/jira/browse/QPID-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734727#comment-14734727
]
ASF subversion and git services commented on QPID-6726:
-------------------------------------------------------
Commit 1701786 from [email protected] in branch 'java/trunk'
[ https://svn.apache.org/r1701786 ]
QPID-6726: [Java Broker] Use reflection for getting maxDirectmemorySize with
HotSpotDiagnosticMXBean and fall back to evaluation of maxDirectmemorySize from
command line arguments when HotSpotDiagnosticMXBean is not not available in JVM
work by Lorenz Quack <[email protected]> and Alex Rudyy <[email protected]>
> Change flow to disk trigger to consider direct memory occupancy
> ---------------------------------------------------------------
>
> Key: QPID-6726
> URL: https://issues.apache.org/jira/browse/QPID-6726
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.0
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Fix For: qpid-java-6.0
>
> Attachments: Tmp.java
>
>
> Currently, flow to disk to triggers when a queue/virtualhost breaches a
> target size where the target size is 40% of the Broker's maxMemory.
> Message payload/headers are now stored in direct memory so considering the
> occupancy of heap is no longer appropriate. We need to change the algorithm
> to consider direct memory occupancy or the occupancy of the buffers allocated
> within direct memory.
> Note: We need to ensure that we leave sufficient direct memory for other
> usages such as Jetty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
