Bug: file download time and throughput is not accurate
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No files, tests, or entry points are named. Start by tracing multifile download timing, chunk blocking, download_elapsed, and throughput aggregation; done means per-file timing and throughput exclude connection-blocking time, with one of the proposed approaches selected and validated.
Written by the indexing model from the issue text.
Description
With the recent changes download timings are no longer accurate for time spent downloading an individual file in multifile mode.
This is related to some chunks blocking on connections so download_elapsed is effectively total_elapsed in all cases.
-
Pget should have a way of communicating time spent for a chunk and aggregating it for a given file rather than download_elapsed including blocking time. This also breaks the throughput calculation.
-
An alternative is to explore downloading one file at a time and allocating connections to meet the target chunk size before moving on to the next file.
If we go with communicating the download time up the stack, this feels like a legitimate use for values in the context (pointer to per-chunk data) instead of trying to pass data back up the whole stack.
- Dominant language
- Go
- Stars
- 151
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
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.
More from replicate/pget
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 32/100
-
Performance Tuning Open
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100