[
https://issues.apache.org/jira/browse/HBASE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765930#action_12765930
]
stack commented on HBASE-410:
-----------------------------
So, I moved TestClient to new system as TestFromClientSide. I see that the
latter runs in about half the time; 2m30s vs. 4m30s. Here is some detail:
Here is old school TestClient timings:
{code}
Testcase: testWeirdCacheBehaviour took 22.499 sec
Testcase: testFilterAcrossMutlipleRegions took 42.655 sec
Testcase: testSuperSimple took 16.456 sec
Testcase: testFilters took 17.679 sec
Testcase: testSimpleMissing took 17.761 sec
Testcase: testSingleRowMultipleFamily took 21.571 sec
Testcase: testNull took 23.111 sec
Testcase: testVersions took 17.3 sec
Testcase: testVersionLimits took 16.351 sec
Testcase: testDeletes took 20.947 sec
Testcase: testJIRAs took 47.615 sec
{code}
Here are TestFromClientSide timings:
{code}
Testcase: testWeirdCacheBehaviour took 7.609 secTestcase:
testFilterAcrossMutlipleRegions took 30.97 sec
Testcase: testSuperSimple took 5.135 sec
Testcase: testFilters took 6.403 sec
Testcase: testSimpleMissing took 5.132 sec
Testcase: testSingleRowMultipleFamily took 10.877 sec
Testcase: testNull took 11.268 sec
Testcase: testVersions took 5.424 sec
Testcase: testVersionLimits took 5.132 sec
Testcase: testDeletes took 5.105 sec
Testcase: testJiraTest867 took 9.234 sec
Testcase: testJiraTest861 took 6.593 sec
Testcase: testJiraTest33 took 5.59 sec
Testcase: testJiraTest1014 took 5.139 sec
Testcase: testJiraTest1182 took 6.4 sec
Testcase: testJiraTest52 took 5.132 sec
{code}
I broke out the individual jira tests that were bundled as TestJiras so we're
paying test setup on each instead of once as was done previous. Means only
1/3rd the time savings for testjiras.
> [testing] Speed up the test suite
> ---------------------------------
>
> Key: HBASE-410
> URL: https://issues.apache.org/jira/browse/HBASE-410
> Project: Hadoop HBase
> Issue Type: Test
> Components: test
> Affects Versions: 0.2.0
> Reporter: Bryan Duxbury
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: 410-v2.patch, 410.patch
>
>
> The test suite takes a long time to run, and a lot of the time spent running
> is really wasted on repeated startup and shutdown, waiting for asynchronous
> events to occur, and production-tuned timeouts to occur. Additionally, we use
> a MiniDFS instead of the local filesystem.
> We should:
> - Make whatever changes are needed to the local DFS so that it can run on
> Windows and use that as the basis of all of our tests
> - Minimize redoing expensive setup where possible by combining tests into
> groups or suites that can share common setup
> - Create a way of running all the parts (Master, Regionserver, Client) in a
> single thread and explicitly advancing through necessary states so that we
> can reliably and quickly get what we need tested accomplished
> - Use smaller test datasets where it would make a difference (TestTableIndex
> and TestTableMapReduce, I'm looking at you!)
> A faster test suite means faster turnaround on new patches, faster Hudson,
> and a shorter patch queue. Not to mention less annoyance on the part of the
> developers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
