[Swift-devel] progress stats lying

[Glen Hocky]

Agreed. but if they are inaccurate then it is as bad as not having them 
at all.

Mihael Hategan wrote:
> On Tue, 2009-04-28 at 13:05 -0500, Glen Hocky wrote:
>   
>> as a user, it seems very important to have accurate summary stats so you 
>> can tell if anything is going wrong.
>>     
>
> You're overgeneralizing. You can infer some things from the summary
> stats, but many things can go wrong even though the summary stats are
> right.
>
>   
>> Mihael Hategan wrote:
>>     
>>> On Tue, 2009-04-28 at 07:15 +0000, Ben Clifford wrote:
>>>   
>>>       
>>>> On Tue, 28 Apr 2009, Ben Clifford wrote:
>>>>
>>>>     
>>>>         
>>>>>> A possible solution is to add another state ("Checking status" or
>>>>>> something), that is triggered in Execute by a task completed event.
>>>>>>         
>>>>>>             
>>>> r2887 adds a checking status event in execute2, right after the 
>>>> vdl:execute call. I think that is sufficient? or are you claiming that 
>>>> something deeper in the execute layer is delaying things?
>>>>     
>>>>         
>>> It's probably better but not sufficient. With many threads there may be
>>> delays between the vdl:execute call completing and the next thing
>>> running may be visible.
>>>
>>> The problem is that swift may say that more jobs are active than known
>>> possible, which will raise eyebrows.
>>>
>>> _______________________________________________
>>> Swift-devel mailing list
>>> Swift-devel at ci.uchicago.edu
>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>>   
>>>       
>
>