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