[jira] [Updated] (QPID-8032) [AMQP1.0] AsyncAutoCommitTransaction optimisation
[
https://issues.apache.org/jira/browse/QPID-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8032:
-
Status: Open (was: Reviewable)
> [AMQP1.0] AsyncAutoCommitTransaction optimisation
> -
>
> Key: QPID-8032
> URL: https://issues.apache.org/jira/browse/QPID-8032
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Keith Wall
>Assignee: Keith Wall
>Priority: Major
> Fix For: qpid-java-broker-7.0.1
>
> Attachments:
> 0001-QPID-8032-Broker-J-AMQP-1.0-Use-asynchronous-transac.patch
>
>
> Some AMQP 1.0 messaging use-cases would benefit from the
> {{AsyncAutoCommitTransactions}} optimisation that is already in use on the
> older protocols.
> For instance, for a publisher sending persistent settled messages, currently
> each message is written to disk and sync before the next message is the
> buffer is processed,. With this optimisation, the syncs would be allowed to
> coalesce.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8032) [AMQP1.0] AsyncAutoCommitTransaction optimisation
[
https://issues.apache.org/jira/browse/QPID-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8032:
-
Attachment: 0001-QPID-8032-Broker-J-AMQP-1.0-Use-asynchronous-transac.patch
> [AMQP1.0] AsyncAutoCommitTransaction optimisation
> -
>
> Key: QPID-8032
> URL: https://issues.apache.org/jira/browse/QPID-8032
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Keith Wall
>Assignee: Keith Wall
>Priority: Major
> Fix For: qpid-java-broker-7.0.1
>
> Attachments:
> 0001-QPID-8032-Broker-J-AMQP-1.0-Use-asynchronous-transac.patch
>
>
> Some AMQP 1.0 messaging use-cases would benefit from the
> {{AsyncAutoCommitTransactions}} optimisation that is already in use on the
> older protocols.
> For instance, for a publisher sending persistent settled messages, currently
> each message is written to disk and sync before the next message is the
> buffer is processed,. With this optimisation, the syncs would be allowed to
> coalesce.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8032) [AMQP1.0] AsyncAutoCommitTransaction optimisation
[
https://issues.apache.org/jira/browse/QPID-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8032:
-
Description:
Some AMQP 1.0 messaging use-cases would benefit from the
{{AsyncAutoCommitTransactions}} optimisation that is already in use on the
older protocols.
For instance, for a publisher sending persistent settled messages, currently
each message is written to disk and sync before the next message is the buffer
is processed,. With this optimisation, the syncs would be allowed to coalesce.
was:
Some AMQP 1.0 messaging use-cases would benefit from the
{{AsyncAutoCommitTransactions}} optimisation that is already in use on the
older protocols.
For instance, for a publisher sending persistent settled messages, currently
each message is written to disk and sync before the next message is the buffer
is processed,. With this optimisation, the syncs would be allowed to coalesce.
Care needs to be taken when the work includes actions that aren't
non-transactional transfers to ensure that transactions remain ACID.
> [AMQP1.0] AsyncAutoCommitTransaction optimisation
> -
>
> Key: QPID-8032
> URL: https://issues.apache.org/jira/browse/QPID-8032
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Keith Wall
>Assignee: Keith Wall
>Priority: Major
> Fix For: qpid-java-broker-7.0.1
>
>
> Some AMQP 1.0 messaging use-cases would benefit from the
> {{AsyncAutoCommitTransactions}} optimisation that is already in use on the
> older protocols.
> For instance, for a publisher sending persistent settled messages, currently
> each message is written to disk and sync before the next message is the
> buffer is processed,. With this optimisation, the syncs would be allowed to
> coalesce.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8032) [AMQP1.0] AsyncAutoCommitTransaction optimisation
[
https://issues.apache.org/jira/browse/QPID-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8032:
-
Status: Reviewable (was: In Progress)
> [AMQP1.0] AsyncAutoCommitTransaction optimisation
> -
>
> Key: QPID-8032
> URL: https://issues.apache.org/jira/browse/QPID-8032
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Keith Wall
>Assignee: Keith Wall
>Priority: Major
> Fix For: qpid-java-broker-7.0.1
>
>
> Some AMQP 1.0 messaging use-cases would benefit from the
> {{AsyncAutoCommitTransactions}} optimisation that is already in use on the
> older protocols.
> For instance, for a publisher sending persistent settled messages, currently
> each message is written to disk and sync before the next message is the
> buffer is processed,. With this optimisation, the syncs would be allowed to
> coalesce.
> Care needs to be taken when the work includes actions that aren't
> non-transactional transfers to ensure that transactions remain ACID.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8032) [AMQP1.0] AsyncAutoCommitTransaction optimisation
[
https://issues.apache.org/jira/browse/QPID-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8032:
-
Fix Version/s: (was: Future)
qpid-java-broker-7.0.1
> [AMQP1.0] AsyncAutoCommitTransaction optimisation
> -
>
> Key: QPID-8032
> URL: https://issues.apache.org/jira/browse/QPID-8032
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Keith Wall
> Fix For: qpid-java-broker-7.0.1
>
>
> Some AMQP 1.0 messaging use-cases would benefit from the
> {{AsyncAutoCommitTransactions}} optimisation that is already in use on the
> older protocols.
> For instance, for a publisher sending persistent settled messages, currently
> each message is written to disk and sync before the next message is the
> buffer is processed,. With this optimisation, the syncs would be allowed to
> coalesce.
> Care needs to be taken when the work includes actions that aren't
> non-transactional transfers to ensure that transactions remain ACID.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
