Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <18521442.258441281462438599.JavaMail.jira@thor>
Date: Tue, 10 Aug 2010 13:47:18 -0400 (EDT)
From: "C.S. Nirmal J. Fernando (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4587) Add tools for improved analysis and
 understanding of query plans and execution statistics
In-Reply-To: <1597970315.314791268837787263.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/DERBY-4587?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1289=
6982#action_12896982 ]=20

C.S. Nirmal J. Fernando commented on DERBY-4587:
------------------------------------------------

Hi Rick,

Thanks for your feedback.

1) I'll modify the arguments, in my next patch.

2) Don't you think that a user will dislike when plans for all the tracked =
statements get generated each and every time he executed the tool? It may t=
ake considerable amount of time given that there are lots of tracked querie=
s. Also we may get into trouble when naming the generated files. What do yo=
u think?

3) Pardon me about the comment, as I said my above reply to Kristian I'll m=
odify it to "Apache Derby Query Explainer (DERBY-4587)" in my next patch.

PS: I suspect that the tool does not need Xalan.jar in the CLASSPATH, both =
to pass tests and generate query plans. Instead it uses the inbuilt Xalan c=
lasses in java. Can you please verify this, if you got some time?

Thanks.

> Add tools for improved analysis and understanding of query plans and exec=
ution statistics
> -------------------------------------------------------------------------=
----------------
>
>                 Key: DERBY-4587
>                 URL: https://issues.apache.org/jira/browse/DERBY-4587
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL, Tools
>            Reporter: Bryan Pendleton
>            Assignee: C.S. Nirmal J. Fernando
>         Attachments: AdavancedXSL-mouseover.jpg, advancedViewXSL.xsl, adv=
ancedViewXSL.xsl, advancedViewXSL2.xsl, advancedXSL-1.jpg, advancedXSL-2.jp=
g, advancedXSL-3.jpg, basic_html-2.2.jpg, basic_html-2.3.jpg, basic_html-2.=
jpg, basic_html-3.jpg, basic_html-4.1.jpg, basic_html-4.2.jpg, Derby Query =
Plan Screen Shot 2.jpg, DERBY-4587-javadoc_fix.diff, DERBY-4587-tool-2.diff=
, DERBY-4587-tool-3.diff, DERBY-4587-tool-4.diff, DERBY-4587-tool-5.diff, D=
ERBY-4587-tool-6.diff, DERBY-4587-tool-7-b.diff, DERBY-4587-tool-7.diff, DE=
RBY-4587-tool-8.diff, DERBY-4587-tool-9.1.diff, DERBY-4587-tool-9.2.diff, D=
ERBY-4587-tool-9.3.diff, DERBY-4587-tool-9.4.diff, DERBY-4587-tool-9.5.diff=
, DERBY-4587-tool-9.6.diff, DERBY-4587-tool-9.7.diff, DERBY-4587-tool-9.7.d=
iff, DERBY-4587-tool-9.diff, DERBY-4587-tool-test1.diff, DERBY-4587-tool-te=
st2.diff, DERBY-4587-tool.diff, derby-logo.png, Derby_Query_Plan_Screen_Sho=
t.jpg, PostgreSQL license.jpg, Read_Me.txt, screenshot-1.jpg, screenshot-2.=
jpg, screenshot-3.jpg, Simple HTML View (Pure XSL).jpg, Source.rar, test.xm=
l, test4.xsl, vanilla_html.xsl, vanilla_html.xsl, vanilla_html.xsl, vanilla=
_html.xsl, vanilla_html.xsl, xml_doc_screenshot.jpg, xml_doc_screenshot.jpg
>
>
> I think it would be great to see some work in the area of tools for helpi=
ng
> with the analysis of complex query execution. Quite frequently, users of
> Derby have trouble comprehending (a) how their query is being translated
> into a query plan by the optimizer, and (b) what the execution-time resou=
rce
> usage of the various parts of the query is.
> There are low-level features in Derby which capture this information and
> record it, such as logQueryPlan, and the XPLAIN tables, but there is a lo=
t
> of opportunity for designing higher-level tools which can process the que=
ry
> plan and execution statistics information and present it in a more
> comprehensible fashion.=20

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