Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
Description
The parameter innodb_prefix_index_cluster_optimization enables an optimization that was added in MDEV-6929. Should the optimization turn out to be incorrect and broken beyond repair in our stress testing, it will have to be reverted. If it is correct, there should be no point to disable it by default.
Related to this, the counters Innodb_secondary_index_triggered_cluster_reads and Innodb_secondary_index_triggered_cluster_reads_avoided are determining the usefulness of this optimization. If we hard-wire the optimization to enabled or disabled, these counters should not serve any useful purpose. As noted in MDEV-21212, frequently updating global counters is not for free.
Attachments
Issue Links
- relates to
-
-
- Closed
-
-
MDEV-21212 buf_page_get_gen -> buf_pool->stat.n_page_gets++ is a cpu waste (0.5-1%)
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue relates to |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Description |
The parameter {{innodb_prefix_index_cluster_optimization}} enables an optimization that was added in Related to this, the counters {{Innodb_secondary_index_triggered_cluster_reads}} and {{Innodb_secondary_index_triggered_cluster_reads_avoided}} are determining the usefulness of this optimization. If we hard-wire the optimization to enabled or disabled, these counters should not serve any useful purpose. As noted in |
The parameter {{innodb_prefix_index_cluster_optimization}} enables an optimization that was added in Related to this, the counters {{Innodb_secondary_index_triggered_cluster_reads}} and {{Innodb_secondary_index_triggered_cluster_reads_avoided}} are determining the usefulness of this optimization. If we hard-wire the optimization to enabled or disabled, these counters should not serve any useful purpose. As noted in |
| Description |
The parameter {{innodb_prefix_index_cluster_optimization}} enables an optimization that was added in Related to this, the counters {{Innodb_secondary_index_triggered_cluster_reads}} and {{Innodb_secondary_index_triggered_cluster_reads_avoided}} are determining the usefulness of this optimization. If we hard-wire the optimization to enabled or disabled, these counters should not serve any useful purpose. As noted in |
The parameter {{innodb_prefix_index_cluster_optimization}} enables an optimization that was added in Related to this, the counters {{Innodb_secondary_index_triggered_cluster_reads}} and {{Innodb_secondary_index_triggered_cluster_reads_avoided}} are determining the usefulness of this optimization. If we hard-wire the optimization to enabled or disabled, these counters should not serve any useful purpose. As noted in |
| Fix Version/s | 10.10.0 [ 27912 ] | |
| Fix Version/s | 10.10 [ 27530 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |