The Linux CPU clock governor (powersaved) ignores processes running with the lowest priority, including project applications. However, because the client runs the benchmarks with normal priority, the benchmarks results are inflated relative to the applications, resulting in exaggerated credit claims and possible punishments by projects (e.g., WCG).

The benchmarks should rather run at the same priority as the applications in order to avoid such consequences.

This is done correctly for Windows (though its clock governor doesn't ignore processes at the lowest priority as Linux's does), but not for Linux. Thus, I propose this patch:

Index: cs_benchmark.C
===================================================================
RCS file: /home/cvs/cvsroot/boinc/client/cs_benchmark.C,v
retrieving revision 1.62.2.5
diff -p -u -w -p -u -w -r1.62.2.5 cs_benchmark.C
--- cs_benchmark.C      1 Mar 2007 16:10:08 -0000       1.62.2.5
+++ cs_benchmark.C      19 Mar 2007 20:55:40 -0000
@@ -223,6 +223,11 @@ void CLIENT_STATE::start_cpu_benchmarks(
         sprintf(benchmark_descs[i].filename, "%s_%d.xml", CPU_BENCHMARKS_FILE_NAME, i);
         PROCESS_ID pid = fork();
         if (pid == 0) {
+#ifdef HAVE_SETPRIORITY
+            if (setpriority(PRIO_PROCESS, 0, PROCESS_IDLE_PRIORITY)) {
+                perror("setpriority");
+            }
+#endif
             int retval = cpu_benchmarks(benchmark_descs+i);
             fflush(NULL);
             _exit(retval);

HTH

---

You'll probably want to sign up for the developers email list and send it there.

---

Kathryn :o)

That's not correct, both the benchmarks and the science apps measure CPU time and not clock time.

On Windows, any CPU-intensive program running on a priority above 'Normal' will make the whole computer hang until said program stops using CPU.

You'll probably want to sign up for the developers email list and send it there.

OK, I posted the patch here.

Thanks.

---

On Windows, any CPU-intensive program running on a priority above 'Normal' will make the whole computer hang until said program stops using CPU.

Indeed. Windows' scheduler allows a process to starve others from CPU time.

Thanks.

---

On Windows, any CPU-intensive program running on a priority above 'Normal' will make the whole computer hang until said program stops using CPU.

Nope... never noticed any effect on the computers responsiveness with BOINC.....maybe windows 98

Exactly, because BOINC correctly sets the science applications to LOW. I said that's what happens on a Windows computer if there is anything CPU-intensive above the level 'Normal'.