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 "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2016/03/14 10:19:33 UTC
[jira] [Updated] (OAK-4123) Persistent cache: control the add data
concurrency
[ https://issues.apache.org/jira/browse/OAK-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomek Rękawek updated OAK-4123:
-------------------------------
Attachment: OAK-4123.patch
> Persistent cache: control the add data concurrency
> --------------------------------------------------
>
> Key: OAK-4123
> URL: https://issues.apache.org/jira/browse/OAK-4123
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: cache
> Reporter: Tomek Rękawek
> Fix For: 1.4.1
>
> Attachments: OAK-4123.patch
>
>
> During operations that creates and reads a large number of nodes (eg. indexing content) it may happen that there's more items in the asynchronous queue (introduced in OAK-2761) than the queue consumer can handle. As a result, the queue is purged and items are not saved in the cache, which makes the overall performance worse.
> An easy fix is to add a property that allows to switch between async/sync mode. By default, it should be synchronous.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)