Fix inaccurate time prediction for tasks

Peter Hucker
Peter Hucker
Joined: 12 Aug 06
Posts: 246
Credit: 219,015,274
RAC: 481,725
Topic 220383

FGRPB1G and O2MDFG2 applications both run on the same GPU.  But the estimated app speed for them differs greatly from reality.

After checking my completed tasks, I measured on my RX560 GPU (using task size divided by actual time taken): Gravity tasks run at 80Gflops/sec, Gamma tasks run at 365Gflops/sec.

But the estimates for each task are: Gravity tasks 304Gflops/sec, Gamma tasks 177Gflops/sec.

This makes a factor of 8 discrepancy between the estimated and the actual time.  Other users with different cards get similar values.  And since the same Duration Correction Factor seems to apply to both applications, after running one of them, the other one ends up with completely inaccurate time predictions, and I get over a week's work instead of a day's work, or the other way round.  Tasks can end up being late, or at least getting returned later than they have to be.

I've been told Einstein uses an older version of the server code and it would be a hassle to change it for reasons to do with getting the science to work, but could you change the time estimates?

These are my validated tasks for each application:

https://einsteinathome.org/host/12647993/tasks/4/40

https://einsteinathome.org/host/12647993/tasks/4/54

Keith Myers
Keith Myers
Joined: 11 Feb 11
Posts: 758
Credit: 645,148,335
RAC: 1,370,483

As Richard explained in your

As Richard explained in your original thread . .

Quote:
The project server doesn't actually calculate the runtime estimate you see in the BOINC Manager.

The only thing that can be done on the server side is change the <rsc_fpops_est> for the different applications to better reflect reality.

 

Peter Hucker
Peter Hucker
Joined: 12 Aug 06
Posts: 246
Credit: 219,015,274
RAC: 481,725

Keith Myers wrote:As Richard

Keith Myers wrote:

As Richard explained in your original thread . .

Quote:
The project server doesn't actually calculate the runtime estimate you see in the BOINC Manager.

The only thing that can be done on the server side is change the <rsc_fpops_est> for the different applications to better reflect reality.

Yes that's what I meant.  If the estimates for the two apps (from the server) are in the correct ratio, then my client will adjust accordingly to my card.  But as they are at the moment, they're out by a factor of 8, so my client adjusts for one app, then gets the other one out by a factor of 8.

Comment viewing options

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