A problem I have seen for a long time is the GFLOPS number for each work unit. The more GFLOPS the faster the unit runs!
For example:
4079 GFLOPS about 3 hours 30 minutes run time.
65284 GFLOPS about 20 minutes run time.

A side effect of this is that when one of those 65284 GFLOP work units is downloaded BOINC thinks it will take a full day to run and doesn't download anything else until it finishes.

A problem I have seen for a long time is the GFLOPS number for each work unit. The more GFLOPS the faster the unit runs!
For example:
4079 GFLOPS about 3 hours 30 minutes run time.
65284 GFLOPS about 20 minutes run time.

A side effect of this is that when one of those 65284 GFLOP work units is downloaded BOINC thinks it will take a full day to run and doesn't download anything else until it finishes.

You are correct. I've got one of each type running. The estimated GFLOPS/sec is the same for both tasks at 0.92 GFLOPS/sec.
But the 4079 GFLOPS task is going to run for 1 hour 50 minutes and the 65,284 GFLOPS task is only estimated to run 22 minutes.

[Edit] I pinged Kevin to this thread for his attention.
[Edit2] This is backwards from standard BOINC client convention that the task property of estimated GFLOPs reflects the total amount of computation power needed to crunch the task.

Disregarding BOINC's broken ability to properly calculate GFLOPS for gpus, it should get this correct for cpu computation power based on the benchmark profile capability of each host.

---

I had not been able to put my finger on what I was seeing different in my downloads. My four PC's as they are downloading work ... but yes it is in smaller amounts Hopefully this will be the answer and it can easily be corrected.

---

In October of 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

I will put it on the list of things to look at this week.

Thanks Kevin, appreciated.

---