You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2014/09/14 15:45:34 UTC

[jira] [Resolved] (CASSANDRA-7915) Waiting for sync on the commit log could happen after writing to memtable

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

Benedict resolved CASSANDRA-7915.
---------------------------------
    Resolution: Not a Problem

We don't actually do very much work at all besides the BTree merge on apply, which we cannot help but delay until the last moment without risking the work being wasted. So there's very little work to save whilst maintaining the current behaviour wrt correctness.

> Waiting for sync on the commit log could happen after writing to memtable
> -------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7915
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7915
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Branimir Lambov
>            Priority: Minor
>
> Currently the sync wait is part of CommitLog.add, which is executed in whole before any memtable write. The time for executing the latter is thus added on top of the time for file sync, which seems unnecessary.
> Moving the wait to a call at the end of Keystore.apply should hide the memtable write time and may improve performance, especially for the batch sync strategy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)