jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-1356) Expose the preferred transient space size as repository descriptor
Date Wed, 04 Feb 2015 15:38:35 GMT

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

Marcel Reutegger commented on OAK-1356:

Large transaction work better now, but the problems mentioned by Thomas are still the same.
We still have multiple passes over the change set, which will result in a lot of repeated
uncached calls. Even if it is technically possible to have large transactions, I wouldn't
recommend them for performance reasons.

> 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

View raw message