[
https://issues.apache.org/jira/browse/OAK-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886835#comment-13886835
]
Tobias Bocanegra commented on OAK-1356:
---------------------------------------
bq. I suggest to write the application such that it doesn't rely on features
that are not working well. And large transactions currently are not working
well. Therefore, there is no need to check anything.
LOL. that is exactly what we do already for jackrabbit - and which was hopped
to be solved for oak.
> 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
> Reporter: Tobias Bocanegra
>
> 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.1.5#6160)
