jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-4124) Persistent cache: consider using callstack blocking
Date Tue, 15 Mar 2016 11:41:33 GMT

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

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

>  If the load is low again, the put()s will be done asynchronously.

OK I understand. This is similar to what the MVStore (the current storage mechanism for the
persistent cache) does: it uses a background thread to persist changes to disk, unless if
there are more than about 4 MB of changes, in which case the writer is blocked. So my guess
is that this patch will not help much.

But it could be tested of course.

> 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)

Mime
View raw message