Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: Very slow doctrineDbalContentGraph projection replay #5269

Closed
dlubitz opened this issue Sep 27, 2024 · 1 comment · Fixed by #5268
Closed

BUG: Very slow doctrineDbalContentGraph projection replay #5269

dlubitz opened this issue Sep 27, 2024 · 1 comment · Fixed by #5268
Assignees

Comments

@dlubitz
Copy link
Contributor

dlubitz commented Sep 27, 2024

Currently the projection replay takes ages if you have a lot of events. This seems to be caused by the GraphProjectorCatchUpHookForCacheFlushing because of:

  1. 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
  2. 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 @mhsdesign PR for the ContentGraph::findAncestorNodeAggregateIds.
@dlubitz dlubitz self-assigned this Sep 27, 2024
@dlubitz
Copy link
Contributor Author

dlubitz commented Sep 27, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant