[PoC] Investigate performance improvements from using a segment-action link table #21966
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.
Description:
This is a work-in-progress, proof-of-concept pull request for #19581 to investigate potential archiving performance improvements by using link tables to match segment parts to actions using primary keys instead of string matching the action name each time.
As a first step this includes a console command to generate link tables and back-fill them with data based on the existing segments and actions in the current dataset. This is a quick way to allow performance testing to validate the approach, it is not intended as production code and therefore not all segment actions are supported.
The console command is:
./console development:build-salt
Run without parameters it will generate the tables and using site specific segment parts.
--v
for more output--nosites
to generate without site specific parts (all actions can be matched to any site)--drop
remove the new link tablesReview