Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-ui-dev] Progress reporting article
It is deprecated in Neon.

On Thu, Apr 28, 2016 at 11:09 AM, Wim Jongman <wim.jongman@xxxxxxxxx> wrote:

On Thu, Apr 28, 2016 at 7:12 PM, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:
A cursory look shows that this code is based on SubProgressMonitor that has been deprecated.

-sergey

On Thu, Apr 28, 2016 at 3:37 AM, Wim Jongman <wim.jongman@xxxxxxxxx> wrote:
Hi,

I remember that Buckminster presents a progress monitor with around 10 included submonitors [1] that report back on tasks that are run in parallel.

Cheers,

Wim

On Mon, Apr 25, 2016 at 7:42 PM, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:
On Mon, Apr 25, 2016 at 1:25 PM, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:


On Mon, Apr 25, 2016 at 10:08 AM, Mickael Istria <mistria@xxxxxxxxxx> wrote:
On 04/25/2016 07:00 PM, Sergey Prigogin wrote:
There is also a philosophical question on how properly report progress of work done in parallel. The orthodox approach is to just measure the amount of work completed so far relative to the total. This is the same approach that is used in the sequential case.
 This is the approach I have in mind.

An alternative is a long-pole approach. Consider a use case where the work is consists of two chunks of unequal size given to two worker threads. The total time to completion is determined by the larger chunk and therefore the progress related to the smaller chunk is irrelevant and should not be reported at all. This can be achieved by writing a custom progress monitor that contains a collection of progress monitors, one for each thread, and reports the lowest of progress values across all child monitors.
 In this case, how are we sure the longer thread will complete before the other one, so that it would be the only one to report? Somehow, it seems to me that reporting progress and reporting time to completion are different things when working in parallel, and that only the first one (progress) can easily be reported reliably, like you described in the 1st part of your answer.

Consider analogy with a horse race where the commentator only tells listeners what happens with the last horse. The horses may change places on the track so the horse whose position is being reported may change over time. 

That's the best analogy ever! :)
 

Reporting overall completed work has tendency to move quicker in the beginning and slow down towards the end when the remaining work is only done on a single thread.

Yes, there are few things worse than a progress bar giving you hope and then reneging on it. It really should be the total time (not work) divided by the current time.
 

Reporting work done may not be perfect, but it would already be quite good IMO.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

-sergey 

_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev


_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev


_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev


_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev


_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev


_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev

Back to the top