-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
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
Integer Shard Index #84
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: TonsnakeLin <[email protected]>
@TonsnakeLin Please move this design to https://github.com/pingcap/tidb/tree/master/docs/design |
|
||
## Summary | ||
|
||
Hot index reduces the write scalability of the TiDB cluster when the written data is monotonically increasing. We find out a proposal to solve the problem that is using an expression index to scatter the hot index, the new expression index is called a shard index. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the table schema and what's the insert workload?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No matter what table schema, but it must has a index and the insert data for this index is monotonically increasing.
don't use Chinese in the benchmark result picture. |
This looks like a simple version of There is already an implementation of |
Signed-off-by: TonsnakeLin [email protected]
Hot index reduces the write scalability of the TiDB cluster when the written data is monotonically increasing. We find out a proposal to solve the problem that is using an expression index to scatter the hot index, the new expression index is called a shard index.