[
https://issues.apache.org/jira/browse/HBASE-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837501#action_12837501
]
Dan Washusen commented on HBASE-2249:
-------------------------------------
Oops, I missed a step...
# PerformanceEvaluation.Test#test gets the current time
# PerformanceEvaluation.Test#test calls PerformanceEvaluation.Test#testTimed
# PerformanceEvaluation.Test#testTimed calls PerformanceEvaluation.Test#testRow
# PerformanceEvaluation.Test#testRow opens the scanner and iterates over all
rows in the result set
# PerformanceEvaluation.Test#test calculates the difference between the start
time and end time and reports it as the elapsed time
> 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: 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.
