hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2249) The PerformanceEvaluation read tests don't take the MemStore into account.
Date Sat, 06 Mar 2010 23:36:27 GMT

    [ https://issues.apache.org/jira/browse/HBASE-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842345#action_12842345

stack commented on HBASE-2249:

I applied HBASE-2249.patch to the branch.  I made one change adding the scanner setup to timing
(I moved the scanner setup out of set setup and into testRow --- if scanner is null, create
it).  It changes timings but it should have been in there all along (as Dan and Dave suggest

Maybe someone can fix up the patch so it applies to TRUNK?

> The PerformanceEvaluation read tests don't take the MemStore into account.
> --------------------------------------------------------------------------
>                 Key: HBASE-2249
>                 URL: https://issues.apache.org/jira/browse/HBASE-2249
>             Project: Hadoop HBase
>          Issue Type: Improvement
>    Affects Versions: 0.20.3
>            Reporter: Dan Washusen
>             Fix For: 0.20.4
>         Attachments: 2249-TRUNK.patch, HBASE-2249.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.

View raw message