[ https://issues.apache.org/jira/browse/CASSANDRA-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937024#comment-13937024 ]
Edward Capriolo commented on CASSANDRA-6746: -------------------------------------------- {quote} FWIW, I'd be okay with dropping mmap mode entirely since compression has been the default for almost two years now. {quote} Are you implying that because compression is the default no one uses uncompressed tables any more? If so I disagree. In cases with small rows 1-10 columns compression can hurt your performance. I am assuming what happens is de serializing compressed blocks 4 k blocks when rows are small creates much more young gen and ends up being a bottleneck. Several operators have told me they do not use compression on high read column families. > Reads have a slow ramp up in speed > ---------------------------------- > > Key: CASSANDRA-6746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6746 > Project: Cassandra > Issue Type: Bug > Components: Core > Reporter: Ryan McGuire > Assignee: Benedict > Labels: performance > Fix For: 2.1 beta2 > > Attachments: 2.1_vs_2.0_read.png, 6746-patched.png, 6746.txt, > cassandra-2.0-bdplab-trial-fincore.tar.bz2, > cassandra-2.1-bdplab-trial-fincore.tar.bz2 > > > On a physical four node cluister I am doing a big write and then a big read. > The read takes a long time to ramp up to respectable speeds. > !2.1_vs_2.0_read.png! > [See data > here|http://ryanmcguire.info/ds/graph/graph.html?stats=stats.2.1_vs_2.0_vs_1.2.retry1.json&metric=interval_op_rate&operation=stress-read&smoothing=1] -- This message was sent by Atlassian JIRA (v6.2#6252)