|Official| Smiles Benchmark 2.0 Ranking Thread! (new version :P)

I pretty much figured that. So I got 3 athlon cores and 1 phenom core. Its runs stable so who cares?
My bad.
I was responding to johnny and misinterpreted the part where he said every time he puts it on 4 he bsod's.
I thought he was referring to the 4th core not Ghz.
Now I see he has a 960, so I was in error. :eek:

But like I said, some get lucky and get a good one. :)
 
i compared my numbers to the 2500k @ 3.3GHz, and i really think the culprit is the special pass, 20 sec difference compared to 10 on the heavy pass, which that seems a little over but not too much.

Yeah that's what I'm trying to remove.
 
I pretty much figured that. So I got 3 athlon cores and 1 phenom core. Its runs stable so who cares?

Actually you have 4 athlon cores, a phenom has more cache i believe and is more stable or better fro overclocking, basically the only difference. Then they just lock one core off and charge a little less, no point in paying to build an entire other machine and having an excess of processors when they can use the same chip, costs them the same amount, and they already have a ton of chips laying around with a single defective core.
 
Yeah I thought the difference between the Athlon II and the Phenom II was that the Phenom II had more L3 cache? I may be wrong though.
 
Yeah I thought the difference between the Athlon II and the Phenom II was that the Phenom II had more L3 cache? I may be wrong though.

yup, you're right, and really the performance difference isn't hardly anything, and idk if athlons are unlocked, if they are then there's no real advantage to a phenom other than the name compared to a athlon x3 when you save 30-40 bucks and get the same power.
 
I have a feeling you can overclock the Athlons, but not as well as the Phenoms. May be wrong though. I've seen people round here getting their Athlon IIs overclocked. I'm not sure how stable they are once they're overclocked though.
 
SmileApp2.0BenchFuryRosewood.jpg


Updated, seems to be much more expected per clock of what I expect of AMD vs Intel.
 
I noticed that while running it didn't seem to be multi-threaded properly, or something. It would max one core out and then the usage would hop cores, they didn't load up all at once.

Weird, mine is stable between all cores...
You running on an AMD?
 
Made me think and after testing thought you might find this interesting, seems to mainly run on second core and barely on the others :confused:


hmm, It can be something in the code I added which is bottering the AMD's. Did you receive the fixed version from vistakid?
 
found this to disable it:
- Go to Regedit

- Find this key:- " 0cc5b647-c1df-4637-891a-dec35c318583 "

- Within this key, there is a value called: " ValueMax "

- This value represents the % number of cores the system will park - the default 100% ie: all Cores are potentially park-able

- Change the value from 64 to 0 so the " ValueMin " and " ValueMax " are both zero

- You will have to find the key a few times and repeat the process for each time it is found - the number of instances will depend on the number of power profiles in your system [ in my DAW it was only found twice ]

- Do a full shutdown and power-off and cold-re-start
 
Here is the fix I already made, there is a bit place for improvement though.
But you can see the difference, I made it (more) multithreaded (so it fits automatically over the cores). Also fixed Amd issue, with the fix the benchmark gonna last longer and be more intensive!

FIX--------------------------------------------------------------------------------------------------------------------OLD
fixofmyapp.jpg


some cores are likely more active then others, but I got multithreaded on... for 4 cores it will be divided properly!
 
found this to disable it:
- Go to Regedit

- Find this key:- " 0cc5b647-c1df-4637-891a-dec35c318583 "

- Within this key, there is a value called: " ValueMax "

- This value represents the % number of cores the system will park - the default 100% ie: all Cores are potentially park-able

- Change the value from 64 to 0 so the " ValueMin " and " ValueMax " are both zero

- You will have to find the key a few times and repeat the process for each time it is found - the number of instances will depend on the number of power profiles in your system [ in my DAW it was only found twice ]

- Do a full shutdown and power-off and cold-re-start


That key is not on my system.
 
Back
Top