db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4771) Continue investigation of automatic creation/update of index statistics
Date Mon, 29 Nov 2010 17:21:11 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan updated DERBY-4771:
-----------------------------------

    Attachment: derby-4771-2f-prototype_lcc_code_dump-WORK-IN-PROGRESS.diff

--- Dag's comment
Thanks, Dag. See my comments below (same order as above). I'm attaching
'derby-4771-2f-prototype_lcc_code_dump-WORK-IN-PROGRESS.diff', which isn't
quite finished yet but contains most of the test fixes.

 * fixed
 * the daemon will start working as soon as the work is scheduled.
   The time it takes depends on overhead related to thread creation/start and
   scanning the base table. Since the tables are small, 500ms is enough if the
   system is in a good state. You are right it may be too low in some cases, so
   I added a method that will try to get the statistics several times until the
   minimum number of stats has been obtained, or the operation times out (I set
   the default timeout to 20 seconds).
 * No, I deleted one and renamed the other.
 * You mean that it is used in several places without being declared a constant?
   I created MASTERDB.
 * Thanks, I have forgotten to shut down that database.
 * testDropWhileScanningThenDelete: TBD, but one option is to trigger another
   automated update after the drop, to at least make sure the daemon is able to
   work after a table has disappeared under its feet.
   Didn't quite get you proposal, but I'll give it some more thought tomorrow.
   I think originally this test found a bug where I was unable to delete the
   database because of dangling file handles on Windows.
 * comment added. We're expecting three entries for the single index, since it
   contains three columns (leading columns: c1, c1-c2, c1-c2-c3).
 * deleted dumpLocks, I think Knut added a similar function somewhere that can
   be copied (and adapted if required) if needed.


--- Lily's comment
Thanks for testing again, Lily.

Can you please apply patch 2f (work in progress, but no reason to test with the
older tests now), make sure you do a clean build and then run the tests again?
They're not failing for me, but I'm currently testing on Solaris.
>From the output, it looks like the statistics aren't getting generated [in time]
on your machine. This could be due to the problem that Dag commented on,
which is hopefully addressed in the preliminary patch 2f.

I'll run the tests on Windows myself too, to get some more data points.

For brevity, it would be nice if you deleted the deprecated properties from the
command line.


> Continue investigation of automatic creation/update of index statistics
> -----------------------------------------------------------------------
>
>                 Key: DERBY-4771
>                 URL: https://issues.apache.org/jira/browse/DERBY-4771
>             Project: Derby
>          Issue Type: Task
>          Components: SQL, Store
>    Affects Versions: 10.8.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>         Attachments: autoindexstats.html, derby-4771-1a-prototype_code_dump.diff, derby-4771-1a-prototype_code_dump.stat,
derby-4771-1b-prototype_code_dump.diff, derby-4771-2a-prototype_lcc_code_dump.diff, derby-4771-2b-prototype_lcc_code_dump.diff,
derby-4771-2c-prototype_lcc_code_dump.diff, derby-4771-2d-prototype_lcc_code_dump.diff, DERBY-4771-2e-prototype.rar,
derby-4771-2e-prototype_lcc_code_dump.diff, derby-4771-2f-prototype_lcc_code_dump-WORK-IN-PROGRESS.diff,
derby.log, error-stacktrace.out, rjall.out, rjall.out, rjall.out, rjall.rar, rjone.out
>
>
> Work was started to improve Derby's handling of index statistics. This issue tracks further
discussion and work for this task.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message