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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/02/04 10:56:35 UTC
[jira] [Commented] (OAK-1356) Expose the preferred transient space
size as repository descriptor
[ https://issues.apache.org/jira/browse/OAK-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304860#comment-14304860 ]
Chetan Mehrotra commented on OAK-1356:
--------------------------------------
[~mreutegg] Given the recent work of yours around supporting large transactions what should we do about this issue. Is this change required?
> Expose the preferred transient space size as repository descriptor
> -------------------------------------------------------------------
>
> Key: OAK-1356
> URL: https://issues.apache.org/jira/browse/OAK-1356
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, jcr
> Reporter: Tobias Bocanegra
> Assignee: Chetan Mehrotra
> Labels: api
> Fix For: 1.2
>
>
> The problem is that the different stores have different transient space characteristics. for example the MongoMK is very slow when handling large saves.
> suggest to expose a repository descriptor that can be used to estimate the preferred transient space, for example when importing content.
> so either a boolean like:
> {{option.infinite.transientspace}}
> or a number like:
> {{option.transientspace.preferred.size}}
> the later would denote the average number of modified node states that should be put in the transient space before the persistence starts to degrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)