db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5772) Give users a way to monitor more Derby internals.
Date Wed, 19 Feb 2014 13:30:22 GMT

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

Rick Hillegas updated DERBY-5772:
---------------------------------

    Summary: Give  users a way to monitor more Derby internals.  (was: Give  users a way to
monitor hits/misses in the page cache.)

Broadening the scope of this issue from just cache hits/misses to include more monitors in
general. For instance, we also get many requests to provide a way to track the number of open
connections to a database. See http://apache-database.10148.n7.nabble.com/Number-of-connection-to-an-embedded-derby-database-td137214.html

> 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.1.5#6160)

Mime
View raw message