Printable View
http://setiathome.berkeley.edu/show_...hostid=3773162
Analyzing work unit IDs
http://setiathome.berkeley.edu/worku...wuid=155019947
Here, 8 1.9GHz K10s take ~twice as long as 2 2.66GHz Core 2s.
http://setiathome.berkeley.edu/worku...wuid=155285917
8 1.9ghz k10s are a very bit faster than 2 2.2ghz k8s
http://setiathome.berkeley.edu/worku...wuid=155286077
here, reverse, k10s a bit slower.
Quite strange. So I take it Barcelona isn't a SETI monster and that SETI doesn't care for cores.
cool thanks for the links :)
I think the links are not working any more, because everytime I click on them, I get an "unable to handle request" error. That's sad because I'm interested in the power of these CPUs. Does anyone have new and/or working links?
OT: *wave* @ JAWS! :)
http://setiathome.berkeley.edu//foru...ap=true#651457
http://setiathome.berkeley.edu/worku...wuid=162484226
Here's a random result, 2 1.86GHz Conroe cores beats 8 2GHz K10, about 3x as fast.
Anyone know what the SETI client apps do in terms of types of calculations. What I mean is, are they floating point or integer intensive?
What I'd really like to see is how an oc'd Opteron 23xx http://www.smileyarena.com/emoticons...nkenstein2.gif does on a WCG (drug discovery, not climate) work unit when boinc manager is running only WCG client apps.
must realize that there are optimized apps for those c2ds
no optimized apps for k10 though