[
https://issues.apache.org/jira/browse/CASSANDRA-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944580#comment-13944580
]
Pavel Yaskevich commented on CASSANDRA-6746:
--------------------------------------------
[~enigmacurry] Yes, it would not eliminate it completely just shorten the
duration and speed up initial warmup, but this drop in operation is worrisome,
can you check if that could be something JVM related or something on Cassandra
side happening at the same time with drop in op rate?
> 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-buffered-io-tweaks.png,
> 6746-patched.png, 6746.blockdev_setra.full.png,
> 6746.blockdev_setra.zoomed.png, 6746.txt, buffered-io-tweaks.patch,
> 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)
