Sandy Bridge i7 support now included
It sucks
It's great
It could use work (please explain)
Sandy Bridge i7 support now included
WCG Rigs: 184 threads, mostly i7s
Just a little thing, a mite if you will.
Perhaps mentioning somewhere that any numbers from this thing are only valid for Windows systems in general?
[SIGPIC][/SIGPIC]
Scratch one of the ''it sucks vote'' was meant to be its great.
Cruncher #1: EVGA Z68 FTW | i7-2600k @ 4.5 | 6GB Ram
Cruncher #2: Supermicro Dual-Socket | 2 x 6-core Opterons | 4GB Ram
Cruncher #3: 8-core Xserve 1,1
T400 for non-crunching
"But don't think you'll run me over - It's, ah, planting season here in Texas... and the farm is growing..." -Otis11 on crunching WCG
Cruncher #1: EVGA Z68 FTW | i7-2600k @ 4.5 | 6GB Ram
Cruncher #2: Supermicro Dual-Socket | 2 x 6-core Opterons | 4GB Ram
Cruncher #3: 8-core Xserve 1,1
T400 for non-crunching
"But don't think you'll run me over - It's, ah, planting season here in Texas... and the farm is growing..." -Otis11 on crunching WCG
Linux 64bit crunches WCG work faster on all projects but most notably on HCC where it's up double the speed, give or take services and other apps etc. This means that each unit takes around half the time. Combine that with the benchmarks being not much different between Win64 and Lin64 and the Lin64 machine will always claim less for a given unit.
As for why the benchmarks are so close when the real world performance is so different ... well there's the fact that benchmarks are always a synthetic representation of a machine's performance and don't really show anything, then there's the conspiracy theory about how a Microsoft plant is diddling the code to inflate the benchmarks and make sure Windows appears competitive (I'm not convinced of this by the way, though MS did exactly this kind of thing with the World Standards Organisation not too long ago so ...) but overall I don't know. Whatever it is it's not a simple issue.
[SIGPIC][/SIGPIC]
I'm pretty sure it's faster on C4CW, I'm not sure what else.
That's astonishing!
So should dedicated WCG rigs run Linux x64 unless there's a compelling reason to do anything else? Even if PPD is about the same, it seems to me like it must be beneficial to the people at WCG to get twice as much work done, no?
WCG Rigs: 184 threads, mostly i7s
But ppd between the two OSes isn't the same though right?
Cruncher #1: EVGA Z68 FTW | i7-2600k @ 4.5 | 6GB Ram
Cruncher #2: Supermicro Dual-Socket | 2 x 6-core Opterons | 4GB Ram
Cruncher #3: 8-core Xserve 1,1
T400 for non-crunching
"But don't think you'll run me over - It's, ah, planting season here in Texas... and the farm is growing..." -Otis11 on crunching WCG
I think I pulled about the same PPD under Kubuntu 10.10 x64 as Win7 x64 on my i7 860 just running HCC. Kubuntu got far more WUs done, Win7 got far more points per WU.
WCG Rigs: 184 threads, mostly i7s
Back from the dead with a new version! Check the OP for a link to download the newest edition, which supports Sandy & Ivy Bridge (including -E variants) CPUs and the AMD FX4/6/8 CPUs (first and second generations!)
WCG Rigs: 184 threads, mostly i7s
Thanks.
For a moment I thought some thing was wrong. But when it asks for the number of cores, it really means cores and not threads.
BTW you need to update your signature.
Last edited by Rob_B; 06-25-2013 at 11:03 AM.
Yeah. I'm still working on getting support for non-HT Intel chips too, but I don't have any i5s available. And to avoid having three different entries each for Sandy/Ivy/FX-Gen1/FX-Gen2 I decided to have just a single entry and make the user enter the number of cores. Now it also works for the Sandy & Ivy 8+ core Xeons too
I do--thanks!
WCG Rigs: 184 threads, mostly i7s
Thanks for the great tool.
OP updated with new version, information, and download link!
WCG Rigs: 184 threads, mostly i7s
Bookmarks