For ati13ati I see time estimation change with more completed CPU-only tasks.
And reverse, CPU only time estimate changes with each new completed ati13ati GPU task.

BOINC 6.10.48

Question is: do separate time estimations for different app_versions implemented already and in what BOINC version if yes ?

---

Question is: do separate time estimations for different app_versions implemented already and in what BOINC version if yes ?

They're implemented on the server only - do keep up!

And only on SETI Beta so far.

Question is: do separate time estimations for different app_versions implemented already and in what BOINC version if yes ?

They're implemented on the server only - do keep up!

And only on SETI Beta so far.

I see. This makes task of writing correct app_info host-specific :/

---

Question is: do separate time estimations for different app_versions implemented already and in what BOINC version if yes ?

They're implemented on the server only - do keep up!

And only on SETI Beta so far.

I see. This makes task of writing correct app_info host-specific :/

They always were.

Re-read the very first post ever written about GPU flop entries:

http://setiweb.ssl.berkeley.edu/beta/forum_thread.php?id=1536&nowrap=true#36887

Almost 15 months ago. It says

your machine's floating point benchmark, multiplied ....
your graphics card's CUDA FLOP count, multiplied ....

Edit - in case this is the point of confusion: the values to put in app_info.xml are speed estimates, which relate to your hardware: not counter values relating to the task size.