https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/YANGTOOLS-502 yangtools <p>Operating System: All<br/> Platform: All</p> YANGTOOLS-502

DataTree: make LazyContainerNode really lazy

Improvement Resolved Done Robert Varga Robert Varga Sun, 13 Sep 2015 22:02:05 +0000 Sun, 10 Apr 2022 18:35:37 +0000 Fri, 18 Sep 2015 12:06:20 +0000 0 0 <p>The step from LazyContainerNode to MaterializedContainerNode performs a complete materialization of the children map. This leads to potentially a large number of entries being created when only a single one is modified &#8211; especially for containers with large number of leaves and keyed maps. This process can introduce a stall in case of large maps, as the number of entries needing processing can be in the 100K range. This is also inefficient for MapEntryNodes, where we instantiate key leaf nodes &#8211; but those are typically not modified.</p> <p>Rename LazyContainerNode to UnmaterializedContainerNode and its place introduce a real LazyContainerNode, which will perform materialization in an incremental fashion when a child is actually modified.</p> <p>This should be done by first consulting the children map. If an entry is found, it will be returned. If it is not found, it needs to be created, stored in the map and then returned.</p> <p>The Mutable#seal() implementation should check if the size of the data children matches the number of stored child nodes. If it does it should create a full MaterializedContainerNode, eliminating the child lookup overhead.</p> <p><a href="https://git.opendaylight.org/gerrit/26896" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/26896</a></p> Development External issue ID 4300 External issue URL Issue Type ODL SR Target Milestone Rank 0|i027mf: