Further improvement of PageStorgae V3
Open
Nobody has claimed this yet.
component/storage
type/enhancement
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Enhancement
We release storage.format_version = 4 and enable PageStorage V3 by default in the v6.1 https://github.com/pingcap/tiflash/issues/3594. There are some improvements remain. Here is the tracking issue of all improvements.
- Polish the debugging tools
- Make it a subcommand of tiflash binary
- Make it can dump the encrypted data https://github.com/pingcap/tiflash/issues/4962
- https://github.com/pingcap/tiflash/issues/5122
- https://github.com/pingcap/tiflash/issues/5336
- Polish the performance testing tools
- Make it a subcommand of tiflash binary https://github.com/pingcap/tiflash/issues/5037
- #5558
- #6056
- [P2] Optimize the restore speed https://github.com/pingcap/tiflash/issues/4914
- [P2] Compression on serialized entries (in WAL), which can optimize the serialized data length for wide tables https://github.com/pingcap/tiflash/issues/4996
- [P2] https://github.com/pingcap/tiflash/issues/5078
- [P3] Split the pipeline of persisting write batch into smaller parts and speed up the throughput for WALStore
- [P3] https://github.com/pingcap/tiflash/issues/4562
- https://github.com/pingcap/tiflash/issues/5675
- https://github.com/pingcap/tiflash/issues/5700
- https://github.com/pingcap/tiflash/issues/5568
- https://github.com/pingcap/tiflash/issues/6071
- https://github.com/pingcap/tiflash/issues/6162
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This is a tracking issue for remaining PageStorage V3 improvements rather than a single scoped change. Review the unchecked linked issues and the listed WALStore, compression, pipeline, and other improvement descriptions; the tracking work is done when the remaining items are addressed and marked complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100