Details
-
Wish
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
The logic in NestedCugHook.addNestedCugPath maintains a hidden multivalue string property at /:nestedCugs (see [1]).
If a customer had many thousands of CUGs, this would result in many thousands of values on this string property which is unlikely to scale.
From anchela:
the reason for storing it is performance optimization i.e. minimizing reading from nodes to see if they hold a cug if the intended usages is that there are few and most nodes don't have a cug. i wouldn't not want to remove the hidden property for that default use case. but we could for sure take a look to see if we could introduce a threshold similar to the one at the root node i.e. using a counter instead of maintaining the complete list and in addition drop the list altogether in that case....