Modifying view queries to improve performance in MySQL / MariaDB. #5988
Conversation
This file contains 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
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.
When using the SCDF UI on an SCDF server based on MySQL / MariaDB, executing job executions becomes slow during pagination if there are thousands of job history records.
This occurs because job executions and other histories are basically exposed in descending order. Creating a view based on descending order can lead to performance improvements.
For reference, when an internal SCDF server had about 8,000 job history records, creating a descending order-based view reduced the pagination movement speed for the 8,000-item list from 30 seconds to 5 seconds.
This has only been verified in MySQL / MariaDB, so modifications for other databases have not been made.