You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2009/03/20 15:22:50 UTC
[jira] Created: (QPID-1763) FtD implementation performs disk access
on every message delivery.
FtD implementation performs disk access on every message delivery.
------------------------------------------------------------------
Key: QPID-1763
URL: https://issues.apache.org/jira/browse/QPID-1763
Project: Qpid
Issue Type: Bug
Components: Java Broker, Performance
Reporter: Martin Ritchie
Assignee: Martin Ritchie
Fix For: 0.5
Summary:
When a QueueEntryImp is deleted() it requests the backing store deletes any corresponding data. However, whilst the data doesn't exist it does perform an exist() check which is costly. This can be avoided by having the QEI remember if it has ever been unloaded and therefore has data to delete.
Checking the results of the performance tests shows that this bug causes a 70% drop in performance in the No-Ack case.
Future enhancement would be to put the actual delete on a different thread, however, performance in when flowed is not a critical concern.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-1763) FtD implementation performs disk access
on every message delivery.
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1763:
---------------------------------
Status: Ready To Review (was: In Progress)
> FtD implementation performs disk access on every message delivery.
> ------------------------------------------------------------------
>
> Key: QPID-1763
> URL: https://issues.apache.org/jira/browse/QPID-1763
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Performance
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: 0.5
>
>
> Summary:
> When a QueueEntryImp is deleted() it requests the backing store deletes any corresponding data. However, whilst the data doesn't exist it does perform an exist() check which is costly. This can be avoided by having the QEI remember if it has ever been unloaded and therefore has data to delete.
> Checking the results of the performance tests shows that this bug causes a 70% drop in performance in the No-Ack case.
> Future enhancement would be to put the actual delete on a different thread, however, performance in when flowed is not a critical concern.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-1763) FtD implementation performs disk
access on every message delivery.
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reassigned QPID-1763:
------------------------------------
Assignee: Aidan Skinner (was: Martin Ritchie)
Hi Aidan can you review this change for me please.
> FtD implementation performs disk access on every message delivery.
> ------------------------------------------------------------------
>
> Key: QPID-1763
> URL: https://issues.apache.org/jira/browse/QPID-1763
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Performance
> Reporter: Martin Ritchie
> Assignee: Aidan Skinner
> Fix For: 0.5
>
>
> Summary:
> When a QueueEntryImp is deleted() it requests the backing store deletes any corresponding data. However, whilst the data doesn't exist it does perform an exist() check which is costly. This can be avoided by having the QEI remember if it has ever been unloaded and therefore has data to delete.
> Checking the results of the performance tests shows that this bug causes a 70% drop in performance in the No-Ack case.
> Future enhancement would be to put the actual delete on a different thread, however, performance in when flowed is not a critical concern.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org