tahoe-lafs/trac-2024-07-25

more precise progress indication for MDMF retrieve #1515

New issue

Open

opened 2011-08-29 14:47:44 +00:00 by davidsarah · 1 comment

davidsarah commented

2011-08-29 14:47:44 +00:00

Owner

From the commit message for changeset:9756146d61673552:

More improvements to consider:

progress is currently 0% or 100%: should calculate how many segments are involved (remembering retrieve can be less than the whole file) and set it to a fraction
"fetch" time is fuzzy: what we want is to know how much of the delay is not our own fault, but since we do decode/decrypt work while waiting for more shares, it's not straightforward

From the commit message for changeset:9756146d61673552: More improvements to consider: * progress is currently 0% or 100%: should calculate how many segments are involved (remembering retrieve can be less than the whole file) and set it to a fraction * "fetch" time is fuzzy: what we want is to know how much of the delay is not our own fault, but since we do decode/decrypt work while waiting for more shares, it's not straightforward

tahoe-lafs added the

code-frontend-web

labels 2011-08-29 14:47:44 +00:00

tahoe-lafs added this to the undecided milestone 2011-08-29 14:47:44 +00:00

tahoe-lafs added

and removed

code-frontend-web

labels 2011-08-29 14:48:29 +00:00

tahoe-lafs added

and removed

labels 2012-04-01 04:42:20 +00:00

warner commented

2015-08-18 17:01:03 +00:00

Author

Owner

Yeah, mutable/retrieve.py currently only calls set_progress() twice: once with 0.0 at the start, and once with 1.0 at the end. This was correct for SDMF, but with MDMF we can make an update after each segment is finished downloading. The place to do this will be inside _decode_blocks(), in the _process() function, where it logs "now decoding segment X of Y". Basically add a set_progress(X/Y) there.

Yeah, mutable/retrieve.py currently only calls `set_progress()` twice: once with 0.0 at the start, and once with 1.0 at the end. This was correct for SDMF, but with MDMF we can make an update after each segment is finished downloading. The place to do this will be inside `_decode_blocks()`, in the `_process()` function, where it logs "now decoding segment X of Y". Basically add a `set_progress(X/Y)` there.

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1515

No description provided.