oceanbase / oceanbase/oceanbase
DAS并发写(DAS concurrent writing)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.3k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
Use Case
[中文版] | [English]
当前DML执行是单线程执行的，所以无论租户资源是否充足，DML执行都只会消耗一个线程资源。在租户资源充足的情况下，为了提升DML性能，在一些场景下可以使用加大并发的思路将租户资源更好的利用起来，从而提升响应时间。
[English] | [中文版]
The current DML execution is executed in a single thread, so regardless of whether the tenant resources are sufficient, DML execution will only consume one thread resource. When tenant resources are sufficient, in order to improve DML performance, in some scenarios the idea of increasing concurrency can be used to better utilize tenant resources, thereby improving response time.
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
Start by tracing the DAS DML execution entry points and how tenant resources are currently allocated; the issue names no files, tests, or implementation boundaries. Define which DML scenarios may run concurrently, how correctness and resource limits will be verified, and what response-time evidence would count as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100