[DERBY-5067] Performance regression tests should populate tables before creating indexes

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.8.1.2
• Fix Version/s: 10.8.1.2
• Component/s: Test
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 24/Feb/11 17:20
• Updated: 13/May/11 06:53
• Resolved: 25/Feb/11 09:27

Description

I've noticed that the results from some of the performance regression tests have become more unstable the last two weeks. See for example here: http://home.online.no/~olmsan/derby/perf/select_30d.html

I suspect it's because the automatic index statistics thread is running (the instability started at about the same time as it was enabled). We should make the test clients create indexes after the tables have been populated so that the statistics will be up to date and no work in the background is needed.

Issue Links

• is related to: DERBY-5206 Investigate reduced throughput in some of the nightly performance tests
• relates to: DERBY-4939 Enable istat daemon and tests
• relates to: DERBY-3790 Investigate if request for update statistics can be skipped for certain kind of indexes, one instance may be unique indexes based on one column.