You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the projection replay takes ages if you have a lot of events. This seems to be caused by the GraphProjectorCatchUpHookForCacheFlushing because of:
The catchUpHook get's called on each event and we can't disable that during replay -> AFAIK this will change anyway with @bwaidelich rework of the CatchUpHooks
ContentGraph::findParentNodeAggregates becomes slower on bigger datasets. Due to the mass on executions, this sums up very quickly. -> We might reduce the amount of call here with @mhsdesignPR for the ContentGraph::findAncestorNodeAggregateIds.
The text was updated successfully, but these errors were encountered:
I also tried to optimize the ContentGraph::findParentNodeAggregates and may have found something. Not sure if I understand fully, but I think we can remove on join with hierarchyrelation, as we have all information we need in the first hierarchyrelation-join. Please check the PR #5268
Currently the projection replay takes ages if you have a lot of events. This seems to be caused by the GraphProjectorCatchUpHookForCacheFlushing because of:
The text was updated successfully, but these errors were encountered: