[
https://issues.apache.org/jira/browse/CASSANDRA-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200604#comment-14200604
]
Shawn Kumar commented on CASSANDRA-7217:
----------------------------------------
I'll be continuing testing on a more cpu-perfomant instance but thought I would
briefly try the cstar_perf on bdplab.
[Here|http://cstar.datastax.com/graph?stats=dd73c4a6-65d9-11e4-9413-bc764e04482c&metric=op_rate&operation=1_write&smoothing=1&show_aggregates=true&xmin=0&xmax=279.07&ymin=0&ymax=120665.6]
are the results - I increase the threads from 500 - 1500 in 250 thread
increments from the first operation to the last and it seems like there is a
noticeable drop.
> Native transport performance (with cassandra-stress) drops precipitously past
> around 1000 threads
> -------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-7217
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7217
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Benedict
> Assignee: Shawn Kumar
> Labels: performance, triaged
> Fix For: 2.1.2
>
>
> This is obviously bad. Let's figure out why it's happening and put a stop to
> it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
