db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DERBY-5772) Give users a way to monitor more Derby internals.
Date Wed, 26 Mar 2014 14:48:15 GMT

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

Dag H. Wanvik edited comment on DERBY-5772 at 3/26/14 2:48 PM:
---------------------------------------------------------------

- The prepared statement cache: size, % filled, statement texts on demand
- View current locks
- Current connections, active transactions
- "hot" queries: statement text, query plan, average execution time, and variance, possibly
  with accompanying data from the statistics snapshot used to choose the query plan



was (Author: dagw):
- The prepared statement cache: size, % filled, statement texts on demand
- View current locks
- Current connections, active transactions


> Give  users a way to monitor more Derby internals.
> --------------------------------------------------
>
>                 Key: DERBY-5772
>                 URL: https://issues.apache.org/jira/browse/DERBY-5772
>             Project: Derby
>          Issue Type: Improvement
>          Components: JMX, Tools
>    Affects Versions: 10.9.1.0
>            Reporter: Rick Hillegas
>
> We should give users a way to track hits/misses in the page cache. This will help users
tune the size of the page cache. JMX-visible monitors might be a useful solution here. See
the following email thread: http://old.nabble.com/Cache-Hit-Miss-rates-for-Derby-pageCache-to33865646.html#a33865646



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message