You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2013/02/28 13:23:12 UTC
[jira] [Resolved] (OAK-175) MemoryNodeStateBuilder inefficient for
large child node lists
[ https://issues.apache.org/jira/browse/OAK-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dürig resolved OAK-175.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.7
Assignee: Michael Dürig
The main issue is fixed. Follow up work is tracked with OAK-659.
> MemoryNodeStateBuilder inefficient for large child node lists
> -------------------------------------------------------------
>
> Key: OAK-175
> URL: https://issues.apache.org/jira/browse/OAK-175
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Fix For: 0.7
>
>
> OAK-174 leverages the {{getChildBuilder()}} method introduced with OAK-170. This revealed a performance issue for large child node list with the {{MemoryNodeStateBuilder}} implementation: without additional measures (see below) {{RootImplTest.largeChildList()}} is very slow.
> The additional measures I currently implemented consist of counting the overall number of changes to a tree and purge these down to the branch when a certain threshold is reached. See {{RootImpl.purge()}}. However, I think this mechanism is too ad-hoc and we should find a more general solution.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira