[
https://issues.apache.org/jira/browse/OAK-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882844#comment-13882844
]
Jukka Zitting commented on OAK-1356:
------------------------------------
bq. As far as I understand, the problem is that the oak-core code (editors,
observers) go through the whole transaction multiple times
I see, good point! That should definitely be fixed, the editor mechanism was
explicitly designed to avoid such multiple scans. There should ultimately be
just one EditorHook, instead of the many we have now, coming especially from
the security code. Also things like the VersionablePathHook should be doable as
an Editor.
> 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)
