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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/12/15 13:16:46 UTC
[jira] [Commented] (OAK-3791) Time measurements for DocumentStore
methods
[ https://issues.apache.org/jira/browse/OAK-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057965#comment-15057965 ]
Chetan Mehrotra commented on OAK-3791:
--------------------------------------
[~rosu] Thanks for looking into this!. I was thinking about and have thought about below approach
# Have a new class DocumentStoreStats - This would expose method to record query call, read call, query for split docs etc.
# DocumentStoreStats is then used within MongoDocumentStore and RDBDocumentStore - The stores would make calls to it when there is a cache miss
# Internally this would make use of StatisticsProvider and manage the various stats and can also expose the JMX MBean for various time series data
Thoughts?
> Time measurements for DocumentStore methods
> -------------------------------------------
>
> Key: OAK-3791
> URL: https://issues.apache.org/jira/browse/OAK-3791
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, documentmk
> Reporter: Teodor Rosu
> Priority: Minor
>
> For monitoring ( in big latency environments ), it would be useful to measure and report time for the DocumentStore methods.
> These could be exposed as (and/or):
> - as Timers generated obtained from StatisticsProvider ( statistics registry )
> - as TimeSeries
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)