Add optional purge and write back for MariaDB TPROC-C #642
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
jamiere-msft
approved these changes
Nov 27, 2023
abondvt89
approved these changes
Nov 28, 2023
|
Merging after reviews and approval of the three members of the code maintenance team. |
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.
Only compatible with MariaDB 10.7.1 and above where purge_threads are dynamic.
Functionality is not possible to add to MySQL at the present time as innodb_purge_threads is a read only variable and functionality is dependent on setting purge_threads temporarily to a high value to accelerate the purge process.
In the CLI the time for purge and write back with require a higher setting of keepalive_time. Plan to add a gdset command to set generic dict settings dynamically rather than only through XML to achieve this.
Tested for both sync and async options