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 "Thomas Mueller (JIRA)" <ji...@apache.org> on 2016/03/15 10:50:33 UTC

[jira] [Commented] (OAK-4124) Persistent cache: consider using callstack blocking

    [ https://issues.apache.org/jira/browse/OAK-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195016#comment-15195016 ] 

Thomas Mueller commented on OAK-4124:
-------------------------------------

Would you block only some of the callers, or all? If you block all, (how) is it different from synchronous operation? (Sorry I don't understand the patch yet)

> Persistent cache: consider using callstack blocking
> ---------------------------------------------------
>
>                 Key: OAK-4124
>                 URL: https://issues.apache.org/jira/browse/OAK-4124
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: cache
>            Reporter: Tomek Rękawek
>              Labels: performance
>             Fix For: 1.6
>
>         Attachments: OAK-4124.patch
>
>
> In the current implementation of the asynchronous add operation in persistence cache, data are added to a queue and if the queue is full, the oldest entries are removed (see OAK-2761).
> It may deteriorate the system performance in some cases (OAK-4123). Let's consider a different approach, in which we block the caller thread in case the queue is full.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)