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

Alex Rudyy updated QPID-8202:
-----------------------------
    Description: When large message cannot fit in one frame it is sent in 
multiple blocks. Currently, the flowed to disk message is reloaded from store 
and evicted from memory on sending every block. As result, the message 
consumption performance is very slow. Only AMQP  protocols 0-8..0-91 are 
affected by the issue  (was: When large message cannot fit in one frame it is 
sent in multiple blocks. Currently, the flowed to disk message is reloaded from 
store and evicted from memory on sending every block. As result, the broker 
consumption performance is very slow. Only AMQP  protocols 0-8..0-91 are 
affected by the issue)

> [Broker-J][AMQP 0-9] Large flowed to disk message can be re-loaded from store 
> for every content chunk sent to the client
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-8202
>                 URL: https://issues.apache.org/jira/browse/QPID-8202
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Broker-J
>    Affects Versions: qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, 
> qpid-java-broker-7.0.0, qpid-java-broker-7.0.1, qpid-java-broker-7.0.4
>            Reporter: Alex Rudyy
>            Assignee: Alex Rudyy
>            Priority: Major
>             Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.5
>
>
> When large message cannot fit in one frame it is sent in multiple blocks. 
> Currently, the flowed to disk message is reloaded from store and evicted from 
> memory on sending every block. As result, the message consumption performance 
> is very slow. Only AMQP  protocols 0-8..0-91 are affected by the issue



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to