mads321 Posted February 11, 2009 Share Posted February 11, 2009 (edited) Hi. So i'm benching my 5000+ Brisbane, and got thus far on same settings: 5th place Pifast - 36.30 sec (1st 35.11 sec) 10th place on SuperPI 1M - 25.95 sec (24.41 sec) 45th place on Wprime 32M - 47sec 720ms (1st place - 22sec 250ms) Anyone find that a little odd? First 2 results makes sense, but the Wprime is so ridiculesly out of charts I have no idea what to think. Either I'm the dumbest OC'er in here, or there has been some hefty moderations to that 1st place wprime system. It has CPU clocked 123 MHz lower than mine, and still get a score 25,47 seconds lower than mine. Thats more than twice as fast.. At first I was running Vista 64-bit, but then i switched to a trimmed down XP, and even ran the RAM with better timings with some better cooling, and guess what... I still got 47 seconds. So I figured I'd try only 2 sticks of memory instead (2x1 in stead of 4x1), and sure thing.. the same number once more. You can find the results here: http://hwbot.org/listResults.do?cpuModelId=1149&applicationId=6&filterUser=true&filterBlocked=true&limit=100 Settings I was running is: Athlon 64 5000+ X2 Brisbane @ 3458mhz on h2o 4096MB DDR2 MIX @ 494mhz 5-4-4-5 (5-4-4-12 on the Vista 64-bit run) Any one care to enlighten me? Edited February 11, 2009 by mads321 Quote Link to comment Share on other sites More sharing options...
komadyret Posted February 11, 2009 Share Posted February 11, 2009 What thread count did you set? It might very well make a huge impact. Test it, and see what you get Quote Link to comment Share on other sites More sharing options...
mads321 Posted February 11, 2009 Author Share Posted February 11, 2009 Ahh.. So there you have it It's the treadcount allright. haven't used this app a whole lot, so I kinda just figured it was out of the box like superPI etc. Thank you for the info! I'll be trying to get better results now then Quote Link to comment Share on other sites More sharing options...
cbjaust Posted March 4, 2009 Share Posted March 4, 2009 I've noticed that sometimes it detects the number of cores correctly and sometimes it doesn't. It must be down to the operating system; in WinXP x64 it works right and detects both cores of my X2 Brisbane, in WinXP x86, Win7 x64 it doesn't find both cores and I just set it manually. The quickest way I find is to press "~" to get the console and type "ft 2" to set wPrime to two threads. "st 6" runs the 32M test, "st 11" runs the 1024M test and "gui" gets back to the normal interface. Cheers Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.