cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kushal Pisavadia (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-875) Performance regression tests, take 2
Date Fri, 19 Mar 2010 22:22:27 GMT

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

Kushal Pisavadia commented on CASSANDRA-875:
--------------------------------------------

I'm pretty interested by this problem, but I see a few different directions that it could
be taken in. 

Would this tool be used as part of the continuous integration process? If so, is it aimed
at entire coverage or just basic regression tests to make sure new feature <x> hasn't
caused too much of a problem? Would it take into account different configurations for read/write
heavy nodes? 

Would there be default datasets to keep things reproducible or would you just define lengths
of data types and fill on the fly? 

A lot of the performance comparisons you see don't take into account specific features of
the databases and just go by lowest common denominator. How generic should the performance
test be? 

Finally, I've been trying to find research related to performance testing these new(er) database
systems and have only come across the works of Brian Cooper to be useful. If you could provide
any other sources that have been successful It would be much appreciated.

> Performance regression tests, take 2
> ------------------------------------
>
>                 Key: CASSANDRA-875
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-875
>             Project: Cassandra
>          Issue Type: Test
>          Components: Tools
>            Reporter: Jonathan Ellis
>
> We have a  stress test in contrib/py_stress, and Paul has a tool using libcloud to automate
running it against an ephemeral cluster of rackspace cloud servers, but to really qualify
as "performance regression tests" we need to
>  - test a wide variety of data types (skinny rows, wide rows, different comparator types,
different value byte[] sizes, etc)
>  - produce pretty graphs.  seriously.
>  - archive historical data somewhere for comparison (rackspace can provide a VM to host
a db for this, if the ASF doesn't have something in place for this kind of thing already)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message