Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 16659 invoked from network); 23 Sep 2010 20:09:58 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Sep 2010 20:09:58 -0000 Received: (qmail 68369 invoked by uid 500); 23 Sep 2010 20:09:58 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 68204 invoked by uid 500); 23 Sep 2010 20:09:57 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 68197 invoked by uid 99); 23 Sep 2010 20:09:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Sep 2010 20:09:57 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Sep 2010 20:09:54 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o8NK9Wgi009005 for ; Thu, 23 Sep 2010 20:09:33 GMT Message-ID: <19956082.370971285272572833.JavaMail.jira@thor> Date: Thu, 23 Sep 2010 16:09:32 -0400 (EDT) From: "Kristian Waagan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-4771) Continue investigation of automatic creation/update of index statistics In-Reply-To: <27013377.329781281704596759.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ 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-2a-prototype_lcc_code_dump.diff Patch 2a is another code dump, still prototyping. I am now using an lcc to update the data dictionary directly from the daemon. The damoen is enabled by default and will write some information to the log. More detailed tracing can be enabled (see the comments in IndexStatisticsDaemon). If anyone has an application or a db load they can test this with, I'd be happy to know if the daemon works. To do so, build Derby with the patch, run your app and then grep your derby.log file afterwards for "istat". It might also crash... You should see statistics being generated for indexes which don't have them, and potentially also updates of existing stats (depends on many factors, I'll explain more later, but some keywords: row count estimate, table growth, statement compilation). I'll be away for a week, and will answer any comments when I'm back. My next step will be to validate/rewrite the logic I added to the table descriptor and the other "catalog classes", potentially followed by some initial tuning of various thresholds, and writing more tests. > 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 > Reporter: Kristian Waagan > Assignee: Kristian Waagan > Attachments: 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.log, error-stacktrace.out, rjall.out, rjall.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.