cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Branimir Lambov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7915) Waiting for sync on the commit log could happen after writing to memtable
Date Sat, 13 Sep 2014 06:25:33 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132570#comment-14132570
] 

Branimir Lambov commented on CASSANDRA-7915:
--------------------------------------------

You're right, I didn't realize early availability could be a problem.

Maybe we could still prepare the write and delay attaching it to the table, but that would
be much more complicated and most probably not worth the effort.

> 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)

Mime
View raw message