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 2016/01/13 16:43:39 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=15096367#comment-15096367 ]
Chetan Mehrotra commented on OAK-3791:
--------------------------------------
[~rosu] [~mreutegg] [~julian.reschke@gmx.de] Thinking further on this - It might be sufficient to just measure the "rate" of calls i.e. query/per second etc and not the distribution of time. As we are more looking into reducing the number of calls and cannot do much about time taken (query cannot be optimized further).
Would it make sense to just collect meter rate for now and not time taken? This would reduce any possible overhead around time and would also simplify the data collection (clock needs to be started and closed) So creates clutter.
> 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
> Assignee: Chetan Mehrotra
> Fix For: 1.4
>
> Attachments: OAK-3791-RDB-0.patch, OAK-3791-v1.patch
>
>
> 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)