cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-2020) stress.java performance falls off heavily towards the end
Date Tue, 22 Feb 2011 16:37:38 GMT

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

Pavel Yaskevich updated CASSANDRA-2020:
---------------------------------------

    Attachment: CASSANDRA-2020.patch

branch: cassandra-0.7 (latest commit 9efe2f795157267fac53b6791734ca7a7a51fe31)

Also fixes CASSANDRA-2200

> 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
>
>         Attachments: CASSANDRA-2020.patch
>
>   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

        

Mime
View raw message