qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Rudyy (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QPID-6726) Change flow to disk trigger to consider direct memory occupancy
Date Thu, 10 Sep 2015 16:16:46 GMT

     [ https://issues.apache.org/jira/browse/QPID-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Alex Rudyy resolved QPID-6726.
    Resolution: Fixed

Reviewed changes whilst working with Lorenz and Rob at changes

> 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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message