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 Tue, 06 Apr 2010 14:20:40 GMT

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

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

I think this is a great way to approach the problem. Your proposal
seems fine to me; we can always add more information to the
graphical view over time as we find uses for it. So long as all the
information is retained in the XML file, such enhancements would
just involve more logic in the XSLT processing, right?

You should also have a close look at the information in the Tuning Guide,
as it describes a lot of the query plan statistics data and how to
interpret it. In particular, you will probably want to have a look at
the XPLAIN tables feature that was added to the trunk, and will
be in the 10.6 release. You can find this feature documented in the
current "development" manuals, at:
http://db.apache.org/derby/docs/dev/tuning/ctun_xplain_tables.html

It seems that you are making very good progress with this idea.

> 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: Bryan Pendleton
>         Attachments: PostgreSQL license.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