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: observer (OceanBase seekdb 1.2.0.0)
- Build Info: source revision 100000172026032022-47f5c040a1a438ce580c16548426b50f00cb0b73.seekd...
Description
During performance testing, the read performance of the standby database is observed to be significantly worse than that of the primary database. The standby's performance is approximately 2 times lower (slower) than the primary's.
Impact
This performance discrepancy impacts the effectiveness of read scaling using standby replicas and may affect overall system throughput in read-heavy scenarios that leverage standby nodes.
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
The issue provides no source files, tests, query, workload, or reproduction steps. Start by reproducing the standby-versus-primary comparison with the stated seekdb 1.2.0.0 environment and source revision, then identify the cause of the roughly 2x read-performance gap. Done means the discrepancy is explained and a verified improvement restores effective standby read scaling.
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