db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dag.wan...@oracle.com (Dag H. Wanvik)
Subject Re: [jira] Closed: (DERBY-5067) Performance regression tests should populate tables before creating indexes
Date Tue, 01 Mar 2011 08:40:03 GMT
"Knut Anders Hatlen (JIRA)" <jira@apache.org> writes:

>      [
> https://issues.apache.org/jira/browse/DERBY-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
> Knut Anders Hatlen closed DERBY-5067.

Jeg får disse rapportene, men det er tungt å lese dem (rar
linjebrekking, ingen grafikk).. hva gjør du får å raskt se hva som er


> -------------------------------------
> The results seem to have stabilized at the same level as before the
> enabling of istat. Closing the issue.
>> Performance regression tests should populate tables before creating indexes
>> ---------------------------------------------------------------------------
>>                 Key: DERBY-5067
>>                 URL: https://issues.apache.org/jira/browse/DERBY-5067
>>             Project: Derby
>>          Issue Type: Improvement
>>          Components: Test
>>    Affects Versions:
>>            Reporter: Knut Anders Hatlen
>>            Assignee: Knut Anders Hatlen
>>             Fix For:
>>         Attachments: pk.diff, select.png
>> 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.

View raw message