[jira] [Commented] (OAK-1356) Expose the preferred transient space size as repository descriptor

["Michael Dürig (JIRA)" <ji...@apache.org>]

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

Michael Dürig commented on OAK-1356:
------------------------------------

I suggest to resolve this as won't fix as it is entirely unclear what 'preferred transient space' means. Such a value might differ a great deal depending on the backend, cluster size, cache configuration, heap size, CPUs etc., which makes determining a reliable value rather unreliable. 

OTOH we should aim to make large transactions as performant as possible by e.g. following up on the issue with multiple passes mentioned by [~tmueller].



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