[ 
https://issues.apache.org/jira/browse/CASSANDRA-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan McGuire updated CASSANDRA-6746:
------------------------------------

    Attachment: 6746.buffered_io_tweaks.write-flush-compact-mixed.png

write, flush, compact, mixed read/write:

!6746.buffered_io_tweaks.write-flush-compact-mixed.png!

[data 
here|http://riptano.github.io/cassandra_performance/graph/graph.html?stats=stats.6746.buffered-io-tweaks.write-flush-compact-mixed.json&metric=op_rate&operation=mixed&smoothing=1&xmin=0&xmax=381.59&ymin=0&ymax=98910.9]


So, looks like it's eliminating any drop at the start. I don't have an 
explanation for the short/periodic drops here in mixed mode. I don't have a lot 
of experience with this new stress mode yet to know, except that 2.0 without 
JNA still faired better.

> 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.buffered_io_tweaks.logs.tar.gz, 
> 6746.buffered_io_tweaks.write-flush-compact-mixed.png, 
> 6746.buffered_io_tweaks.write-read-flush-compact.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)

Reply via email to