cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8729) Commitlog causes read before write when overwriting
Date Wed, 04 Feb 2015 23:35:35 GMT

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

Joshua McKenzie commented on CASSANDRA-8729:
--------------------------------------------

You're totally right - reads vs. writes are different beasts w/regards to this and my work
was regarding reads.

Also:  I highly approve of your benchmark class name. ;)

> Commitlog causes read before write when overwriting
> ---------------------------------------------------
>
>                 Key: CASSANDRA-8729
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8729
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Ariel Weisberg
>
> The memory mapped commit log implementation writes directly to the page cache. If a page
is not in the cache the kernel will read it in even though we are going to overwrite.
> The way to avoid this is to write to private memory, and then pad the write with 0s at
the end so it is page (4k) aligned before writing to a file.
> The commit log would benefit from being refactored into something that looks more like
a pipeline with incoming requests receiving private memory to write in, completed buffers
being submitted to a  parallelized compression/checksum step, followed by submission to another
thread for writing to a file that preserves the order.



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

Mime
View raw message