Standby read performance is significantly lower than primary (approximately 2x slower)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 342
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 53
Description
Environment
- Version: seekdb (OceanBase seekdb 1.2.0.0)
- Source Revision: 100000172026032022-47f5c040a1a438ce580c16548426b50f00cb0b73.seekd...
Description
During performance testing, the read performance of the standby database is observed to be significantly lower than that of the primary database, with the standby being approximately 2 times slower.
Impact
This performance gap may affect the effectiveness of read scaling or failover scenarios that rely on the standby instance.
Priority
High (Performance regression)
Contributor guide
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
No source files, tests, or entry points are identified. Start by reproducing the standby-versus-primary read benchmark on seekdb 1.2.0.0 and compare profiling results for both paths. Done means identifying and addressing the cause of the approximately 2x standby slowdown, with measurements showing the performance gap has been reduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100