From derby-dev-return-595-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Tue Oct 05 01:21:49 2004 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 89238 invoked from network); 5 Oct 2004 01:21:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 5 Oct 2004 01:21:49 -0000 Received: (qmail 87443 invoked by uid 500); 5 Oct 2004 01:21:47 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 87415 invoked by uid 500); 5 Oct 2004 01:21:47 -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: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 87404 invoked by uid 99); 5 Oct 2004 01:21:47 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [66.163.168.182] (HELO smtp803.mail.sc5.yahoo.com) (66.163.168.182) by apache.org (qpsmtpd/0.28) with SMTP; Mon, 04 Oct 2004 18:21:45 -0700 Received: from unknown (HELO debrunners.com) (ddebrunner@sbcglobal.net@66.125.228.35 with plain) by smtp803.mail.sc5.yahoo.com with SMTP; 5 Oct 2004 01:21:29 -0000 Message-ID: <4161F6A1.9010208@debrunners.com> Date: Mon, 04 Oct 2004 18:19:29 -0700 From: Daniel John Debrunner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4.1) Gecko/20031008 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derby Development Subject: Re: Query Optimization Tool References: In-Reply-To: X-Enigmail-Version: 0.76.8.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jonas S Karlsson wrote: > Sunitha Kambhampati wrote: > >>It is not very user friendly, but it helps to give an idea of which >>indexes have been used. > > > Yes, reading that very wide output is a lot of fun, so fun that I > wrote a script to do it a while back, it picks out the major structure > of the query, gives some index/join info of the plan and shows the > general outline. My query had 15 nested joins so it was really > impossible to read the output by hand. You may need to modify it > for your queries... The TO-DO list has this entry Generate run time statistics output in XML format [http://incubator.apache.org/derby/DerbyToDo.html] A regular format for the output would be a great help to everyone, an XML format seems natural. As far as I know no-one is working on this, though maybe what Sandeep is doing is similar. Sandeep, is there any chance you could give an overview of what you are doing? I'm hoping that work in this area could reduce Derby's footprint by removing the specialized classes in the org.apache.derby.impl.sql.execute.rts package. Dan. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBYfahIv0S4qsbfuQRAga3AJ48COY5wuu0PliztjEBnlTXl9ryEgCfYrwx dSMIMPKuiyoT3iACs12AdYg= =1/t7 -----END PGP SIGNATURE-----