db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "C.S. Nirmal J. Fernando (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4587) Add tools for improved analysis and understanding of query plans and execution statistics
Date Sun, 04 Jul 2010 14:56:50 GMT

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

C.S. Nirmal J. Fernando updated DERBY-4587:
-------------------------------------------

    Attachment: DERBY-4587-tool-8.diff
                vanilla_html.xsl

I've modified the XML document generated by the tool, as it displays nodes 
as a tree structure, an according to that I've changed the XSL style sheet as well.
Screen shots are attached to display the outcome after applying the style sheet, 
and to display how a XML file looks, after changing it to a tress structure.

As Rick requested I've changed the name of the tool to "PlanExporter".
So, now you have to run the new tool like this:
java org.apache.derby.tools.PlanExporter jdbc:derby:nirmal 
me mine MYSCHEMA b9810038-0128-e492-0a47-00000035b7e8 xml_file

*note the change of the name.

And the new patch (8) is contain these modifications done and also the modifications
on XplainStatisticsTest.java.

I've run that test file and all 17 tests were passed, and I had a close look at
all the XML file, to check whether they display as expected in the tests
and if I believe my eyes I couldn't find any error.

Anyway I highly appreciate if someone can have a look at the final out come,
if you need any help to set up contact me or Bryan.

And I'm hoping to get ideas of all the members of the community, please feel free
to criticize on the tool.

Thanks.

> Add tools for improved analysis and understanding of query plans and execution 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: 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-tool-2.diff,
DERBY-4587-tool-3.diff, DERBY-4587-tool-4.diff, DERBY-4587-tool-5.diff, DERBY-4587-tool-6.diff,
DERBY-4587-tool-7-b.diff, DERBY-4587-tool-7.diff, DERBY-4587-tool-8.diff, DERBY-4587-tool-test1.diff,
DERBY-4587-tool-test2.diff, DERBY-4587-tool.diff, Derby_Query_Plan_Screen_Shot.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.xml, test4.xsl, vanilla_html.xsl, vanilla_html.xsl,
vanilla_html.xsl, vanilla_html.xsl, xml_doc_screenshot.jpg
>
>
> I think it would be great to see some work in the area of tools for helping
> 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 resource
> 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 lot
> of opportunity for designing higher-level tools which can process the query
> plan and execution statistics information and present it in a more
> comprehensible fashion. 

-- 
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