WIP: BUGFIX: Speed up findChildNodes in a large content repository#5728
Draft
WIP: BUGFIX: Speed up findChildNodes in a large content repository#5728
findChildNodes in a large content repository#5728Conversation
a query always uses both the 'parentnodeanchor' and 'childnodeanchor' column thus we group them into a single (unique) index (we can simply use them as primary key) the position is now an own index otherwise `EXPLAIN SELECT` shows that the default ordering `h.position ASC` is not done via index this is merely the index adjustment. The queries must be adjusted as well to leverage subselects wich brings the full performance gain with the new indexes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
see https://discuss.neos.io/t/discussion-editing-and-storing-thousands-of-blog-posts-news-entries-in-nodes-in-neos-9-0/7154 for the full discussion
a query always uses both the 'parentnodeanchor' and 'childnodeanchor' column thus we group them into a single (unique) index (we can simply use them as primary key)
the position is now an own index otherwise
EXPLAIN SELECTshows that the default orderingh.position ASCis not done via indexthis is merely the index adjustment. The queries must be adjusted as well to leverage subselects wich brings the full performance gain with the new indexes
Ironically we had the primary key like this already but reverted that change #5009 because of slow replay performance. That will need to be reevaluated. See #5011 (comment)
Upgrade instructions
Review instructions
Checklist
FEATURE|TASK|BUGFIX!!!and have upgrade-instructions