[
https://issues.apache.org/jira/browse/JCRVLT-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800429#comment-13800429
]
Felix Meschberger commented on JCRVLT-18:
-----------------------------------------
[~tmueller] I think for package installation, stability is more important than
performance. The main drawback of autosave (which is why I really don't like
it) is that it is not atomic and may leave partially installed packages behind
which are hard to cleanup.
I would suggest to remove auto save alltogether and rather instruct users to
use smaller packages.
> Set default autosave threshold based on repository implementation
> -----------------------------------------------------------------
>
> Key: JCRVLT-18
> URL: https://issues.apache.org/jira/browse/JCRVLT-18
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Reporter: Tobias Bocanegra
> Priority: Minor
>
> with jackrabbit 2.0 we had a limitation of the size of the transient space as
> it is held in memory. in order to support large packages, the AutoSave
> threshold is set to 1024 nodes.
> with jackrabbit 3.0 the transient space is more or less unlimited in size,
> and we can install large packages in 1 save, which improves installation
> atomicity.
> however, the bigger the transient size, the higher the chance for collisions
> during installation of large packages, so saving in chunks yields to a more
> robust installation behavior.
> suggestions:
> - autosave threshold of 0 should mean 'auto'
> - autosave threshold of -1 should mean 'never'
> - packages can provide their desired autosave threshold via properties
--
This message was sent by Atlassian JIRA
(v6.1#6144)
