Return results immediately?

ADDMP
ADDMP
Joined: 25 Feb 05
Posts: 104
Credit: 7,332,049
RAC: 0
Topic 188527

I have noticed that the "Average turnaround time" is considerably larger than the average of the "CPU time"s reported in stats. This is apparently because the clients hang on to results for some time before returning them.

I have seen some posts here in which a user set a flag to return results as soon as they finished.

My question is: Is is regarded a beneficial by the program to get results back as soon as finished, or is that regarded as merely an unnecessary added burden on tbe servers?

ADDMP

Keck_Komputers
Keck_Komputers
Joined: 18 Jan 05
Posts: 376
Credit: 5,744,455
RAC: 0

Return results immediately?

It is generally considered an added burden on the scheduling server. With that switch on the client will make 2 scheduler RPCs per workunit, with it off the worst case is about 1.1 RPC per workunit. The client will automatically return work that is in deadline trouble.

BOINC WIKI

BOINCing since 2002/12/8

John McLeod VII
John McLeod VII
Moderator
Joined: 10 Nov 04
Posts: 547
Credit: 632,255
RAC: 0

> It is generally considered

Message 8411 in response to message 8410

> It is generally considered an added burden on the scheduling server. With that
> switch on the client will make 2 scheduler RPCs per workunit, with it off the
> worst case is about 1.1 RPC per workunit. The client will automatically return
> work that is in deadline trouble.
>
Only if it is completed before the deadline.

Keck_Komputers
Keck_Komputers
Joined: 18 Jan 05
Posts: 376
Credit: 5,744,455
RAC: 0

> > It is generally

Message 8412 in response to message 8411

> > It is generally considered an added burden on the scheduling server. With
> that
> > switch on the client will make 2 scheduler RPCs per workunit, with it off
> the
> > worst case is about 1.1 RPC per workunit. The client will automatically
> return
> > work that is in deadline trouble.
> >
> Only if it is completed before the deadline.
>
This also applies if it is overdue. The relevent code fragment is:
(r->report_deadline (less or equal) (now + REPORT_DEADLINE_CUSHION))

BOINC WIKI

BOINCing since 2002/12/8

John McLeod VII
John McLeod VII
Moderator
Joined: 10 Nov 04
Posts: 547
Credit: 632,255
RAC: 0

> > > It is generally

Message 8413 in response to message 8412

> > > It is generally considered an added burden on the scheduling server.
> With
> > that
> > > switch on the client will make 2 scheduler RPCs per workunit, with
> it off
> > the
> > > worst case is about 1.1 RPC per workunit. The client will
> automatically
> > return
> > > work that is in deadline trouble.
> > >
> > Only if it is completed before the deadline.
> >
> This also applies if it is overdue. The relevent code fragment is:
> (r->report_deadline (less or equal) (now + REPORT_DEADLINE_CUSHION))
>
Sorry, what I was trying to say was that it will not report a result that has not yet finished.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.