Skip to content
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

withprogress is barely helpful with threaded/distributed collectors #527

Open
tecosaur opened this issue Jun 9, 2022 · 0 comments
Open

Comments

@tecosaur
Copy link

tecosaur commented Jun 9, 2022

I'm a big fan of withprogress, when it works. It's nice and easy to slot it into a pipeline like so:

1:10000 |> withprogress |> Map(_ -> sleep(0.01)) |> collect

and I see a nice live-updating progress bar.

Unfortunately, the moment I start doing threaded or distributed computations it becomes markedly less helpful. With the example above, instead of smoothly updating in-step with the computation it has a tenancy to sit at 0% progress, and then jump to completion. This is particularly unhelpful when I have a multi-hour computation which I'd rather like to monitor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant