You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Michael Marth (JIRA)" <ji...@apache.org> on 2015/12/21 16:43:46 UTC
[jira] [Commented] (OAK-3814) Collect and expose important runtime
statistics across various part of Oak
[ https://issues.apache.org/jira/browse/OAK-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066588#comment-15066588 ]
Michael Marth commented on OAK-3814:
------------------------------------
related to OAK-3791:
I think what would be very useful is to measure the read request flow/cache hits across the whole Oak stack, i.e.
1. cache hit/miss in persistent cache
2. cache hit/miss in DocStore cache (would be covered by OAK-3791)
3. at this point we would hit persistence (Mongo, RDB): timing on this would be useful
Other than that: do we have stats on query execution time indexing?
> Collect and expose important runtime statistics across various part of Oak
> --------------------------------------------------------------------------
>
> Key: OAK-3814
> URL: https://issues.apache.org/jira/browse/OAK-3814
> Project: Jackrabbit Oak
> Issue Type: Epic
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: 1.4
>
>
> Aim of this epic is to improve the collection of runtime statistics across various sub systems in Oak. This would enable following benefits
> # Better insight into operational aspects of Oak
> # Better integration with external monitoring system based on JMX
> # Based on stats we can decide what needs to be done to make Oak perform better i.e. based on actual usage data
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)