Skip to content

Optimizing hotspot small tables #25293

@tiancaiamao

Description

@tiancaiamao
Focus this week Current status
- Disable DDL for some cases
- Finish performance test report
Target: Make this feature GA

- KR1: Finish developing 95%
- KR2: Finish testing 90%
- KR3: Document, GA announce, etc 90%
Plan for the next 4 weeks Status indicator
Finish all testing The previous week is spend on core bank performance testing,
and the result is expected

Description

When a table is too small, it is located in just one region, that region would become a hotspot, and such hot spots would cause a performance bottleneck. By directly caching the small table data in the TiDB layer, such hot spot issues can be solved.

For a small, often used and rarely changed table, caching the whole table in memory in the TiDB server can improve performance.

Document Collection

Talent Challenge Program information

Milestones and action items

Milestone 1: Support schema change for caching table, Expected finish date: TBD

Milestone 2: Support reading and writing on cached table, Expected finish date: TBD

Milestone 3: Test with abnormal injection cases

  • Test by inject failpoint during some DDL change phase
  • Chaos testing for the read/write operation

Misc:

Limitation & Known bugs

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions