Right, this has pretty much been beaten to death, but an image is worth a thousand words.



For a test I just left one box on it's own for 18 days. As you can see it started very well... until it hit day -14 and ran its benchmark and start sliding down.

At day -12 I got tired of watching it go downhill and rolled the bench dices manually until I got high numbers again.

Ran OK until day -8 when the auto-benchmark decided to run again. (see a pattern emerging here? me too)

I wasn't at home so this was a 100% idle box at the time with 0 app running on it. Still, because of the low bench my rac slides down 30 points.

Again as I said, nothing that hasn't been discussed before but I thought that image would get the point across for those who didn't know about this boinc-specific problem.

---

Team CFVault.com
http://www.cfvault.com

And for those that wonder how they can workaround this :P

for windows:
C:Program FilesBOINC>boinccmd.exe --run_benchmarks

for linux:
FE 1107-212532 /opt/BOINC # ./boinc_cmd --run_benchmarks

The client does not have to be stopped, it stops by itself, and resumes automagically after the benchmark.

Both Windows and Linux have ways to automate tasks :hint: :hint: :)