You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2014/09/10 11:24:29 UTC

[jira] [Commented] (DERBY-6733) Implement an MBean for monitoring caches

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

Knut Anders Hatlen commented on DERBY-6733:
-------------------------------------------

The discussion in DERBY-5772 has only talked about the page cache so far, but since the code for collecting statistics has to live inside the CacheManager implementation, it will be just as easy to get the information out of any of Derby's caches.

I think it would at least make sense to have a way to monitor the page cache and the statement cache, and probably also the container cache.

There are many more caches, though:

VMTypeIdCache
TableDescriptorOIDCache
TableDescriptorNameCache
SPSNameDescriptorCache
SequenceGeneratorCache
PermissionsCache
ConglomerateDirectoryCache

I'm not sure how useful it would be to expose all of them.

> Implement an MBean for monitoring caches
> ----------------------------------------
>
>                 Key: DERBY-6733
>                 URL: https://issues.apache.org/jira/browse/DERBY-6733
>             Project: Derby
>          Issue Type: Improvement
>          Components: JMX
>    Affects Versions: 10.12.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>
> Add an MBean that allows users to monitor Derby's CacheFactory instances, as discussed in DERBY-5772.



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