Have someone realized how bad are scoring most of new multiple-cpu hosts and the hosts running third-parts "optimized client"?
Their credit are only fraction of those claimed by single cpu hosts and/or hosts running the original client.
Maybe it's good for Science, but their ranks in users statistics are going back!

Have someone realized how bad are scoring most of new multiple-cpu hosts and the hosts running third-parts "optimized client"?
Their credit are only fraction of those claimed by single cpu hosts and/or hosts running the original client.
Maybe it's good for Science, but their ranks in users statistics are going back!

That is why you download a core client as well.

---

- cJ

I found just the opposite after four weeks.
Less cpu cycles but more throughput of work.

Regards,
Graeme.

www.setiuk.com

---

Have someone realized how bad are scoring most of new multiple-cpu hosts and the hosts running third-parts "optimized client"?
Their credit are only fraction of those claimed by single cpu hosts and/or hosts running the original client.
Maybe it's good for Science, but their ranks in users statistics are going back!

One possibility is to download an "optimized" core client as well; however, this will inflate your claims on ALL projects, not just SETI, and many people consider this at least borderline cheating.

Another workaround is to run a longer work queue, so the work you return is less likely to be part of the validation quorum and the credit claims based on the other units. (This is what I do on my Linux box that runs an optimized science app, and has a typical claim of 4.5 - 5.5 per WU.)

Finally, the _enhanced application uses an actual operations count rather than relying on the flawed benchmarks, so the problem may largely go away once that's in place. The enhanced application is supposed to be released Real Soon Now (tm). So it may be a temporary problem anyway.

Cheers,
Brian

---

If you think education is expensive, try ignorance.

It doesn't have to be a multi-cpu computer to claim low credits, those single core cpu's with large L2 cache also suffer same problem.

---