db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4587) Add tools for improved analysis and understanding of query plans and execution statistics
Date Sun, 27 Jun 2010 18:06:50 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882969#action_12882969
] 

Bryan Pendleton commented on DERBY-4587:
----------------------------------------

Good, I see all four nodes now. Thanks!

For result sets of "scan" table, like TABLESCAN or HASHSCAN, it
would be useful to include the information from the SYSXPLAIN_SCAN_PROPS
row. In particular, it would be nice for the SCAN nodes to identify what
table was being scanned; I think that information is in the SCAN_OBJECT_NAME
column of the corresponding SYSXPLAIN_SCAN_PROPS row.

At the top of this page, there is a sample query that shows a little bit
about how to join between SYSXPLAIN_RESULTSETS and SYSXPLAIN_SCAN_PROPS:
http://db.apache.org/derby/docs/10.6/ref/rrefsysxplain_scan_props.html


> 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.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.diff, DERBY-4587-tool-test1.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, 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