apache / apache/uniffle

[Improvement] Limit the read concurrency for one disk

Open
#903 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
454
Forks
172
Avg merge
5d 17h
Merged PRs (30d)
5

Description

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

### Search before asking

- [X] I have searched in the [issues](https://github.com/apache/incubator-uniffle/issues?q=is%3Aissue) and found no similar issues.

### What would you like to be improved?

I found the `get_local_data_process_latency_0.99` is high, sometimes it reaches 60 secs. And in this time, I found the disk utilization reached 100%.

So do we need to limit the concurrency for per disk? I think it's necessary

### How should we improve?

_No response_

### Are you willing to submit PR?

- [X] Yes I am willing to submit a PR!

Contributor guide

Open the contributing guide

Research direction

Start by tracing the get_local_data_process_latency_0.99 metric and the per-disk read path described in the issue. Establish how read concurrency is currently measured, determine the desired per-disk limit, and validate that latency and disk utilization improve without reducing correctness.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
distributed-systems, performance
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.