[
https://issues.apache.org/jira/browse/OAK-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395736#comment-15395736
]
Vikas Saurabh commented on OAK-4543:
------------------------------------
Looks useful to me. My understanding being that the approach should be to find
listener with high ratios and fix observer code. Otoh, if the queue length is
increasing with listener with relatively low ratio, then look for logged
information to see what's going wrong.
> Add info about event generation and consumption by observer
> -----------------------------------------------------------
>
> Key: OAK-4543
> URL: https://issues.apache.org/jira/browse/OAK-4543
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Vikas Saurabh
> Assignee: Marcel Reutegger
> Priority: Minor
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4,
> monitoring, observation, performance
> Fix For: 1.6
>
> Attachments: OAK-4543.patch
>
>
> I'm not sure if it's possible in the current scheme of things
> (implementation), but it'd useful to be able to easily differentiate between
> slow diff calculation or slow observer as a reason to see why observation
> queue might fill up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
