[
https://issues.apache.org/jira/browse/CASSANDRA-16036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173546#comment-17173546
]
David Capwell commented on CASSANDRA-16036:
-------------------------------------------
Fair point. I am spinning up two clusters, with and without CC, and can run a
few benchmarks Monday.
The current test used was a write heavy clustering key test with slices on
clustering, but mostly looked at the selects for this patch. Given the logic I
see the next test I will run is a 100% read test with pre-populated data.
> Add flag to disable chunk cache and disable by default
> ------------------------------------------------------
>
> Key: CASSANDRA-16036
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16036
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 4.0-beta
>
> Attachments: Histogram-11.png
>
>
> Chunk cache is enabled by default and doesn’t have a flag to disable without
> impacting networking. In performance testing 4.0 against 3.0 I found that
> reads were slower in 4.0 and after profiling found that the ChunkCache was
> partially to blame; after disabling the chunk cache, read performance had
> improved.
> {code}
> 40_w_cc-selects.hdr
> #[Mean = 11.50063, StdDeviation = 13.44014]
> #[Max = 482.41254, Total count = 316477]
> #[Buckets = 25, SubBuckets = 262144]
> 40_wo_cc-selects.hdr
> #[Mean = 9.82115, StdDeviation = 10.14270]
> #[Max = 522.36493, Total count = 317444]
> #[Buckets = 25, SubBuckets = 262144]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]