cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6746) Reads have a slow ramp up in speed
Date Thu, 13 Mar 2014 04:27:45 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932862#comment-13932862
] 

Jonathan Ellis commented on CASSANDRA-6746:
-------------------------------------------

bq. if true we do not explicitly DONTNEED, but we do not WILLNEED either

I get that, but the reason this was introduced in the first place was because the default
behavior of (at least some) Linux kernels was to evict other data in favor of the newly flushed.

> 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)

Mime
View raw message