Hi All
I have noticed that for exactly the same machine (Proc. Memory, MoBo etc.) that when running Linux, the benchmark scores are only about half the benchmark scores under Windows. I noticed my Linux boxes have a Result Duration Correction Factor of 0.2 to 0.45 and the Windows boxes go from 0.7 to 0.9

This makes no difference at all to the processing times and usually Linux will run a higher RAC than Windows on the same machine.

I'm just wondering why the BOINC Benchmark test is so inconsistant between the two OS's ?

Regards
Brodo
(Getting right into the Tech of things :-)

Don't think anybody has found a reason for it yet. You have discovered why Seti moved to counting Flops to calculate credits.
If you had crunched units with Linux as the OS when it was Benchmark * time, as benchmark was low and time quicker on Linux the claimed was very low. Two Linux machines, in the quorum, on one unit and your RAC went done the pan.

Hi All
I have noticed that for exactly the same machine (Proc. Memory, MoBo etc.) that when running Linux, the benchmark scores are only about half the benchmark scores under Windows. I noticed my Linux boxes have a Result Duration Correction Factor of 0.2 to 0.45 and the Windows boxes go from 0.7 to 0.9

This makes no difference at all to the processing times and usually Linux will run a higher RAC than Windows on the same machine.

I'm just wondering why the BOINC Benchmark test is so inconsistant between the two OS's ?

Regards
Brodo
(Getting right into the Tech of things :-)

Most likely different compilers.

The duration correction factor takes care of that (among other things).

---

It's been known for many years that Linux benchmarks lower than 'doze. On my boxes Linux bm's at about 85% of 'doze. At one point in time Rom released a BOINC client that bm'd at about 105% of 'doze after weeks of discussions in the alpha mailing list. He soon reverted back however, after the version of a library was found to be not as backwards compitable as originally indicated and older linux versions would not work with this new build. Windoze appears to do backwards compitability better......

Live long and BOINC!

---

Paul
(S@H1 8888)
And proud of it!

Its all about compiler optimizations. By dfault the linux client is less optimized than the windows one. But if you are using Gentoo like I am on some of my systems then the boinc client is compiled from source with whatever optimizations you have set for the whole system. I recently changed one of my 4400+s from windows to linux. The old windows benchmark was 2246.68 floating point and 4151.96 integer. The same hardware, now running linux scored 2173.97 floating point and 5954.82 integer. As you can see the floating point is slightly lower (under 10%) and the integer benchmark is actually higher in linux. But this is just because it was compiled with different optimizations turned on. If I used the stock BOINC client it would be lower.

I may delete the windows host soon but until then you can compare them side by side

---

A member of The Knights Who Say NI!
For rankings, history graphs and more, check out:
My BOINC stats site