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 "Teodor Rosu (JIRA)" <ji...@apache.org> on 2015/12/18 13:22:46 UTC

[jira] [Comment Edited] (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=15063892#comment-15063892 ] 

Teodor Rosu edited comment on OAK-3791 at 12/18/15 12:22 PM:
-------------------------------------------------------------

The disadvantage for making the StatisticsProvider reference static (in osgi env) is that when/if the StatisticsProviderFactory.providerType is changed, the DocumentNodeStoreService component will be deactivated and reactivated.  As mentioned, the advantage is simpler code.



was (Author: rosu):
The disadvantage for making the StatisticsProvider reference static (in osgi env) is that when/if the StatisticsProviderFactory.providerType is changed, the DocumentNodeStore component will be deactivated and reactivated.  As mentioned, the advantage is simpler code.


> 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
>         Attachments: OAK-3791-RDB-0.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)