We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I'm testing the performance of #38442
autoid.txt
I use this table schema:
create table test (id int unsigned key nonclustered auto_increment) shard_row_id_bits=4 auto_id_cache 1;
It avoids the sequent rowid caused tikv hotspot issue. But I find the flamegraph abnormal:
Row ID allocating takes too much resource! I figure out that cause by the side effect of the auto_id_cache = 1 setting.
The text was updated successfully, but these errors were encountered:
meta/autoid: fix AUTO_ID_CACHE 1 setting affect row id allocator perf…
272d328
…ormance (#39534) close #39528
Successfully merging a pull request may close this issue.
Enhancement
When I'm testing the performance of #38442
autoid.txt
I use this table schema:
It avoids the sequent rowid caused tikv hotspot issue.
But I find the flamegraph abnormal:
Row ID allocating takes too much resource!
I figure out that cause by the side effect of the auto_id_cache = 1 setting.
The text was updated successfully, but these errors were encountered: