jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (JCRVLT-18) Set default autosave threshold based on repository implementation
Date Mon, 21 Oct 2013 06:36:42 GMT

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

Thomas Mueller edited comment on JCRVLT-18 at 10/21/13 6:36 AM:
----------------------------------------------------------------

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

Yes. Please note it does not necessarily improve installation *performance* when using one
very large transaction (autosave threshold of -1) for the MongoDB case. In fact large transactions
might be slower than small ones. The reason is that MongoMK does not support large transactions
efficiently (and MongoDB doesn't support transactions at all), so that large transactions
require more work than multiple smaller transactions.



was (Author: tmueller):
> 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.

Yes. Please note it does not necessarily improve installation *performance* when using one
very large transaction (autosave threshold of -1) for the MongoDB case. In fact large transactions
might be slower than small ones. The reason is that MongoMK does not support large transactions
(and MongoDB doesn't support transactions at all), so that large transactions require more
work than multiple smaller transactions.


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

Mime
View raw message