Add new scheduling algorithm for reducing tail latencies #105
Conversation
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
|
Hi, thank you for your contribution. Please confirm this code is submitted under the terms of the OCA (Oracle's Contribution Agreement) you have previously signed by cutting and pasting the following text as a comment: |
|
I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it. |
|
Nice paper and patch. I'm wondering when the VProfiler will be available on http://github.com/mozafari/vprofiler? |
|
Hi, thank you for your contribution. Your code has been assigned to an internal queue. Please follow |
dbussink
pushed a commit
to planetscale/mysql-server
that referenced
this pull request
Mar 6, 2024
* Support new Vitess internal table name format * Update sql/table.cc * Update sql/table.cc * Update sql/table.cc * optimize regexp search * match start of name --------- Signed-off-by: Shlomi Noach <[email protected]> Co-authored-by: Patrick Reynolds <[email protected]>
dbussink
pushed a commit
to planetscale/mysql-server
that referenced
this pull request
May 21, 2024
* Support new Vitess internal table name format * Update sql/table.cc * Update sql/table.cc * Update sql/table.cc * optimize regexp search * match start of name --------- Signed-off-by: Shlomi Noach <[email protected]> Co-authored-by: Patrick Reynolds <[email protected]>
dbussink
pushed a commit
to planetscale/mysql-server
that referenced
this pull request
May 21, 2024
* Support new Vitess internal table name format * Update sql/table.cc * Update sql/table.cc * Update sql/table.cc * optimize regexp search * match start of name --------- Signed-off-by: Shlomi Noach <[email protected]> Co-authored-by: Patrick Reynolds <[email protected]>
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.
This branch introduces a new scheduling algorithm (Variance-Aware-Transaction-Scheduling, VATS) for the record lock manager of InnoDB and XtraDB. Instead of using First-Come-First-Served (FCFS), the newly introduced algorithm uses an Eldest-Transaction-First (ETF) heuristic, which prefers older transactions over new ones. A configuration parameter (innodb_lock_schedule_algorithm) is introduced for users to choose between VATS and FCFS (the default one). We've extensively tested this algorithm in many workloads. The algorithm is very simple, and the changes are very local, but it significantly improves performance (in terms of average latency and throughput) and predictability (in terms of reduction of tail and quantile latencies) For more details, please refer to this paper http://arxiv.org/abs/1602.01871
The new code of the whole pull request, including one or several files that are either new files or modified ones, is contributed under the BSD-new license.