[
https://issues.apache.org/jira/browse/CASSANDRA-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141292#comment-14141292
]
Jason Brown edited comment on CASSANDRA-6809 at 9/19/14 9:02 PM:
-----------------------------------------------------------------
[~blambov] The github link referenced above just brings me to a page that says
"There isn't anything to compare". Tried looking at your c* repo, as well, on
github but no obvious branches to poke at.
was (Author: jasobrown):
[~blambov] The github link you add just bring me to a page that says "There
isn't anything to compare". Tried looking at your c* repo, as well, on github
but no obvious branches to poke at.
> Compressed Commit Log
> ---------------------
>
> Key: CASSANDRA-6809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6809
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Benedict
> Assignee: Branimir Lambov
> Priority: Minor
> Labels: performance
> Fix For: 3.0
>
> Attachments: logtest.txt
>
>
> It seems an unnecessary oversight that we don't compress the commit log.
> Doing so should improve throughput, but some care will need to be taken to
> ensure we use as much of a segment as possible. I propose decoupling the
> writing of the records from the segments. Basically write into a (queue of)
> DirectByteBuffer, and have the sync thread compress, say, ~64K chunks every X
> MB written to the CL (where X is ordinarily CLS size), and then pack as many
> of the compressed chunks into a CLS as possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
