You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2011/02/17 21:28:29 UTC

[jira] Updated: (CASSANDRA-2020) stress.java performance falls off heavily towards the end

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

Brandon Williams updated CASSANDRA-2020:
----------------------------------------

    Fix Version/s:     (was: 0.7.2)
                   0.7.3

> stress.java performance falls off heavily towards the end
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-2020
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2020
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Contrib
>            Reporter: Brandon Williams
>            Assignee: Pavel Yaskevich
>            Priority: Minor
>             Fix For: 0.7.3
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> This is due to threads completing towards the end, such that there aren't enough to fully stress the cluster.  The main problem here is that stress.java is a straight port of stress.py, where each thread runs through some range until it's done, and the threads finish at different times (probably offset by jvm warmup time.)  Instead, a producer/consumer model would work better.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira