[
https://issues.apache.org/jira/browse/OAK-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397255#comment-15397255
]
Vikas Saurabh commented on OAK-4543:
------------------------------------
Yeah, sorry... should've been clearer... so, queue length growing with
inefficient/efficient filter can be due to really fast incoming commits OR
event generation being slow. Low ratio with inefficient filter is probably same
as a listener which quits early per path but asks for whole diff anyway - queue
length growth in such cases would mean that event generation isn't able to keep
up with incoming commits.
Optimizing filter or optimizing event generation as potential resolutions is
probably orthogonal to the monitoring task.
> 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)
