-
Notifications
You must be signed in to change notification settings - Fork 458
perf: MRD improvements #3525
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
perf: MRD improvements #3525
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #3525 +/- ##
==========================================
- Coverage 79.70% 79.47% -0.23%
==========================================
Files 141 141
Lines 18931 18939 +8
==========================================
- Hits 15089 15052 -37
- Misses 3330 3375 +45
Partials 512 512
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
72eeef1
to
98d8c5d
Compare
case res := <-done: | ||
if !mrdWrapper.config.FileSystem.IgnoreInterrupts { | ||
select { | ||
case <-time.After(timeout): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can remove the timeout since its currently set to a very higher value @abhishek10004
Hi @Tulsishah, your feedback is needed to move this pull request forward. This automated reminder was triggered because there has been no activity for over 24 hours. Please provide your input when you have a moment. Thank you! |
Description
This PR optimizes CPU runtime by removing unused and unnecessary code paths within the Multi Range Downloader (MRD) flow.
During CPU profiling of the random reads flow (50GB file, 4KB I/O), we identified three key areas consuming significant CPU time that could be optimized:
This PR addresses these issues with the following changes:
NOTE: bug b/432639555 was identified during the implementation. This will be fixed in subsequent PR.
Link to the issue in case of a bug fix.
b/423600392
Testing details
Profiling:
Before:
After:

Bandwidth:
50G 4K IO:
Before changes: 3976kB/s
After changes: 4343kB/s (~10% improvement)
Any backward incompatible change? If so, please explain.