jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomek Rękawek (JIRA) <j...@apache.org>
Subject [jira] [Updated] (OAK-4124) Persistent cache: consider using callstack blocking
Date Mon, 14 Mar 2016 09:23:33 GMT

     [ https://issues.apache.org/jira/browse/OAK-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tomek Rękawek updated OAK-4124:
-------------------------------
    Attachment: OAK-4124.patch

> 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