IntersectMBO / IntersectMBO/mithril

Computing digest takes 10½ min on Mainnet – could we get progress there, too?

Open
#1,894 3 comments 0 reactions 0 assignees View on GitHub
good first issue :wave: UX :sun_with_face:
Dominant language
Rust
Stars
154
Forks
51
Avg merge
1d 23h
Merged PRs (30d)
38

Description

## Why

Considering that the digest currently takes over 10 minutes to compute on Mainnet, it would be better UX if we could show the progress to the user.

![image](https://github.com/user-attachments/assets/a3ce25b1-4c94-47d3-b045-b1ab84ef07ff)

## What

I see in [this code fragment](https://github.com/input-output-hk/mithril/blob/52a7beb77c537b54fcb1ca171bf1b1c0c059bad8/mithril-client/src/message.rs#L64-L100) that no progress is being updated.

This can be tricky because I'm assuming that the digest is recursive. But we could check the whole unpacked directory size first? Maybe even in parallel, delaying the first progress update to not lose unpacking time? Or even just progress in terms of the number of files processed would work well, the speed wouldn't be constant, but still.

([original Slack thread](https://input-output-rnd.slack.com/archives/C04NGRE6GLQ/p1723203968279289))

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.