Return-Path: Delivered-To: apmail-incubator-cassandra-commits-archive@minotaur.apache.org Received: (qmail 88726 invoked from network); 17 Jun 2009 17:20:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Jun 2009 17:20:29 -0000 Received: (qmail 42363 invoked by uid 500); 17 Jun 2009 17:20:40 -0000 Delivered-To: apmail-incubator-cassandra-commits-archive@incubator.apache.org Received: (qmail 42351 invoked by uid 500); 17 Jun 2009 17:20:40 -0000 Mailing-List: contact cassandra-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-dev@incubator.apache.org Delivered-To: mailing list cassandra-commits@incubator.apache.org Received: (qmail 42341 invoked by uid 99); 17 Jun 2009 17:20:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jun 2009 17:20:40 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jun 2009 17:20:28 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 67E19234C044 for ; Wed, 17 Jun 2009 10:20:07 -0700 (PDT) Message-ID: <508184340.1245259207409.JavaMail.jira@brutus> Date: Wed, 17 Jun 2009 10:20:07 -0700 (PDT) From: "Stu Hood (JIRA)" To: cassandra-commits@incubator.apache.org Subject: [jira] Commented: (CASSANDRA-234) Performance regression tests In-Reply-To: <503857938.1245174907929.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CASSANDRA-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720767#action_12720767 ] 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: https://issues.apache.org/jira/browse/CASSANDRA-234 > Project: Cassandra > Issue Type: New Feature > Environment: all > Reporter: Sandeep Tata > Fix For: 0.4 > > > Since we have a few performance/efficiency tickets open (https://issues.apache.org/jira/browse/CASSANDRA-233, https://issues.apache.org/jira/browse/CASSANDRA-174), 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: http://blog.oskarsson.nu/2009/05/vpork.html > Jon Travis has a description at http://wiki.github.com/trav/vpork/vpork > 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.