cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-234) Performance regression tests
Date Wed, 17 Jun 2009 17:20:07 GMT


Stu Hood commented on CASSANDRA-234:

Performance metrics are a great idea, but it will be pretty important to make the coverage
broad enough that we don't focus optimizations in the wrong place. For instance, performing
VPork runs that do range queries, and other runs that fetch varying numbers of column families.

Also, you might want to consider the ability to fire up multiple client machines as well,
because we know that in some cases Cassandra can saturate the network before breaking a sweat.

> Performance regression tests
> ----------------------------
>                 Key: CASSANDRA-234
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>         Environment: all
>            Reporter: Sandeep Tata
>             Fix For: 0.4
> Since we have a few performance/efficiency tickets open (,, we should probably start using some
basic benchmark for regression. 
> VPork's an option.
> Johan has a description of how to get going with it:
> Jon Travis has a description at
> A performance graph that keeps getting better as we move forward is always fun :-)
> Can apache provide resources for a perf regression service? How do other projects set
this up? Suggestions?

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

View raw message