cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russ Hatch (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6943) very contentious writes result in performance degradation
Date Thu, 27 Mar 2014 17:09:19 GMT

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

Russ Hatch commented on CASSANDRA-6943:
---------------------------------------

interactive graphs here:

(datastax austin cluster):
http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6943.read_write.uber_contention_CL_one2.json&metric=op_rate&operation=write&smoothing=1&xmin=0&xmax=328.24&ymin=0&ymax=17487.8

(datastax bdplab cluster):
http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6943.read_write.uber_contention_CL_quorum2.json&metric=op_rate&operation=write&smoothing=1&xmin=0&xmax=258.94&ymin=0&ymax=13200

> very contentious writes result in performance degradation
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-6943
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6943
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Russ Hatch
>         Attachments: screenshot.png, screenshot2.png
>
>
> Running performance scenarios I have seen this characteristic drop in performance happen
several times. A similar effect was reproduced in another test cluster. Operations eventually
come to a standstill.
> !screenshot.png!
> !screenshot2.png!



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message