[
https://issues.apache.org/jira/browse/CASSANDRA-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033477#comment-13033477
]
Terje Marthinussen commented on CASSANDRA-47:
---------------------------------------------
And yes, that traversal two times of the row to calculate serialized size
before writing the row is reasonably expensive with compression.
Any good reason we absolutely have to do this in two passes instead of one?
Or just the way it is for historical purposes?
Yes, we would need to write indexes etc. after the row or in a separate file if
we don't traverse it twice, but this would seems a relatively small change on
first sight?
> SSTable compression
> -------------------
>
> Key: CASSANDRA-47
> URL: https://issues.apache.org/jira/browse/CASSANDRA-47
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Priority: Minor
> Labels: compression
> Fix For: 1.0
>
>
> We should be able to do SSTable compression which would trade CPU for I/O
> (almost always a good trade).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
