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 Mon, 08 Sep 2014 17:39:29 GMT

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

Dag H. Wanvik edited comment on DERBY-5772 at 9/8/14 5:39 PM:
--------------------------------------------------------------

Attaching [^derby-5772-db-bean-1.diff]:
{quote}

adds an mbean per database booted with the following attributes:

	-  name
	-  foo

The first is just the database name (quoted full path). The other is an example attribute
that shows how we could leverage access to the database via SQL in an MBean if we need it
(sans authorization here, though, but I believe we could extend the bean to cover that). We
would probably only want to use a connection if it might allow some observables that might
otherwise be hard or impractical to extract without SQL. Not sure that is the case, though.
Not for commit, proof of concept only for now.
{quote}
Builds on Knut's patch plus my previous one.


was (Author: dagw):
Attaching [^derby-5772-db-bean-1.diff]:
{quote}

adds an mbean per database booted with the following attributes:

	-  name
	-  foo

The first is just the database name (quoted full path). The other is an example attribute
that shows how we could leverage access to the database via SQL in an MBean if we need it
(sans authorization here, though, but I believe we could extend the bean to cover that). We
would probably only want to use a connection if it might allow some observables that might
otherwise be hard or impractical to extract without SQL. Not sure that is the case, though.
Not for commit, proof of concept only for now.
{quote}

> 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
>         Attachments: derby-5772-db-bean-1.diff, derby-5772-more-pagecache.diff, pagecache-counters.diff,
pagecache-counters.diff, pagecache-counters.png
>
>
> 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.3.4#6332)

Mime
View raw message