You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Reza Motamedi (JIRA)" <ji...@apache.org> on 2016/11/27 18:59:58 UTC

[jira] [Commented] (AURORA-1833) Expose stats on MyBatis mapped statements

    [ https://issues.apache.org/jira/browse/AURORA-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15700150#comment-15700150 ] 

Reza Motamedi commented on AURORA-1833:
---------------------------------------

MyBatis allows us to intercept calls within the execution of a mapped statement. This allows us to time various mapped statements and ultimately gain more insight on the performance of the database module.

> Expose stats on MyBatis mapped statements
> -----------------------------------------
>
>                 Key: AURORA-1833
>                 URL: https://issues.apache.org/jira/browse/AURORA-1833
>             Project: Aurora
>          Issue Type: Story
>            Reporter: Mehrdad Nurolahzade
>            Priority: Minor
>              Labels: newbie
>
> Aurora exposes stats on high level storage operations. However, stats on individual low level MyBatis mapped statements is not currently exposed. Intercepting and exposing timing stats on these statements can facilitate database level optimizations such identifying long running queries, missing indexes, batching, etc.
> Please note that query stats can also be acquired from H2 through {{INFORMATION_SCHEMA.QUERY_STATISTICS}} meta-table.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)