Skip to content

Conversation

@TonsnakeLin
Copy link

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.

@TonsnakeLin
Copy link
Author

@zhangjinpeng87
Copy link
Member


## 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.
Copy link

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?

Copy link
Author

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.

@siddontang
Copy link
Contributor

don't use Chinese in the benchmark result picture.

@mjonss
Copy link

mjonss commented Feb 21, 2022

This looks like a simple version of GLOBAL INDEX for a hash partitioned global index. Are there any plans on extending it to fully support GLOBAL INDEX? So it supports any type of index, both partitioned and non-partitioned tables, and also support to partition the index by either HASH or RANGE ?

There is already an implementation of GLOBAL INDEX in TiDB, but it is only experimental and I don't think it is maintained. Some links in this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants