[
https://issues.apache.org/jira/browse/CASSANDRA-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028800#comment-15028800
]
Benjamin Lerer commented on CASSANDRA-10225:
--------------------------------------------
The CI results:
* The unit test results are
[here|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-10225-3.2-testall/2/]
* The Dtest results are
[here|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-10225-3.2-dtest/2/]
I investigated the {{jmxmetrics_test.TestJMXMetrics.begin_test}} dtest which
was failing due to the compression ratio. It seems that the test assertion is
just wrong. There are no reasons why the compression ratio for all the tables
together should decrease after the insertion of the values. I do not think that
it is reasonable to expect anything precise in this case for the compression
ratio.
I will modify the dtest to remove the compression ratio assertions.
> Make compression ratio much more accurate
> -----------------------------------------
>
> Key: CASSANDRA-10225
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10225
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Jeremy Hanna
> Assignee: Brett Snyder
> Labels: lhf
> Fix For: 2.1.x
>
> Attachments: 10225-trunk.txt, cassandra-2.1-10225.txt
>
>
> Currently in cfstats, it will take an average over the compression ratios of
> all of the sstables without regard to the data sizes. This can lead to a
> very inaccurate value. It would be good to factor in the uncompressed and
> compressed sizes for the sstables to give an accurate number.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
