You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2015/01/26 23:52:35 UTC
[jira] [Commented] (CASSANDRA-8686) Introduce Latency Target for
Stress
[ https://issues.apache.org/jira/browse/CASSANDRA-8686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292563#comment-14292563 ]
Benedict commented on CASSANDRA-8686:
-------------------------------------
I like this idea. There's a lot of stress improvements needed in the near future, and I'll see if I can sneak this one in as well.
> Introduce Latency Target for Stress
> -----------------------------------
>
> Key: CASSANDRA-8686
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8686
> Project: Cassandra
> Issue Type: Improvement
> Reporter: jonathan lacefield
> Priority: Minor
>
> This item is a request to add a latency target to the rate option for the new stress tool. The goal of the latency target would be to provide a guideline for SLAs to the stress tool so the stress tool can determine threads and throughputs that can be sustained while meeting the SLA targets.
> For example:
> cassandra-stress [options/commands] -rate latency p90=5 p95=10 p99=100
> The outcome of this command would be a stress execution that would gradually increase threads, and hence throughput (trans/sec), until the latency profile can no longer be satisfied with the current workload (yaml file definition) and/or cluster. This would provide a ceiling for throughput and connections for the given cluster, workload, and SLA profile.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)