Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <11239703.398221285397194046.JavaMail.jira@thor>
Date: Sat, 25 Sep 2010 02:46:34 -0400 (EDT)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Updated: (HBASE-2249) The PerformanceEvaluation read tests
 don't take the MemStore into account.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack updated HBASE-2249:
-------------------------

    Fix Version/s:     (was: 0.90.0)

Moving out of 0.90.  We're all YCSB these times rather than PE.

> The PerformanceEvaluation read tests don't take the MemStore into account.
> --------------------------------------------------------------------------
>
>                 Key: HBASE-2249
>                 URL: https://issues.apache.org/jira/browse/HBASE-2249
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.20.3
>            Reporter: Dan Washusen
>         Attachments: 2249-TRUNK.patch, HBASE-2249.patch, HBASE-2249_v2.patch
>
>
> The write tests in the PerformanceEvaluation flush the MemStore after they complete, as a result the read tests don't take the MemStore into account (because it's always empty).  An optional flag could be provided when the performance evaluation starts that dictates if the table should be flushed after a test completes.  This optional flag would allow changes to the MemStore to be performance tested...

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