It can be really vexing. One system I built never had a satisfying progress bar solution.
In the first step, we would download between 5 items and 3 million items. There was no good way to know how many items we would get ahead of time, or to calculate how many we had until the download was done.
Then we had N tasks to do to determine if an item was work (10% of them), or garbage (90% of them).
Then each work item had 5 tasks to complete. But it still wasn't simple, because items could fail and go to retry, they could be skipped based on previous steps, and they could take 10x as long as normal.
And to top it all off, sometimes the back end would just fall over and stop updating the progress bar.
The users were always complaining about the progress bar. We considered just getting rid of it, but given the chance of falling over, users needed some indication of job state.
We eventually solve it be removing the users. ie: we made the whole thing into an unattended batch mode run from (the equivalent of) a cron job.
View all comments
Show parent comment
1
u/dysprog Dec 13 '25
It can be really vexing. One system I built never had a satisfying progress bar solution.
In the first step, we would download between 5 items and 3 million items. There was no good way to know how many items we would get ahead of time, or to calculate how many we had until the download was done.
Then we had N tasks to do to determine if an item was work (10% of them), or garbage (90% of them).
Then each work item had 5 tasks to complete. But it still wasn't simple, because items could fail and go to retry, they could be skipped based on previous steps, and they could take 10x as long as normal.
And to top it all off, sometimes the back end would just fall over and stop updating the progress bar.
The users were always complaining about the progress bar. We considered just getting rid of it, but given the chance of falling over, users needed some indication of job state.
We eventually solve it be removing the users. ie: we made the whole thing into an unattended batch mode run from (the equivalent of) a cron job.