NormalizedNodePruner is used heavily during recovery, where it is used for each modification being applied. Its design unfortunately does not lend itself for reuse and we end churning memory rather heavily due to its use of an internal stack.

Furthermore we end up looking up the same DataSchemaContextTree over and over, which while working on a weak cache, is still a waste of CPU cycles.