Jump to content
HWBOT Community Forums

UCBench11: Tweaks and Luck


GENiEBEN

Recommended Posts

  • Replies 207
  • Created
  • Last Reply

Top Posters In This Topic

  • 2 months later...

If you're reading this post than you probably had a blocked UCBench score. What we once considered "luck" turned out to be a design flaw of the benchmark, documented by a fellow member of the HWBOT community (credits pending) and personally tested for veracity.

 

TL;DR: The Passwords Checked column must be in ascending order (A<B<C etc)

 

How to make sure you're not going to get a bugged score:

Make sure that thread selected divided to total available threads (cpu threads) is not an odd number.

Let's take an example: -cpus=24,53,60 ; with a physical CPU that has 4 threads (4c/4t, 2c/4t).

Benchmark only cares about every other second thread (24,53,60 -- A,B,C,D,E,). This example will be bugged since 53 divided by 4 will result into an odd number (13) AND is also second in line. If we were to rearrange our original choice, we could return a valid result using: 24,60,53. Notice that since second number divided by 4 is now an even number, the result won't be affected.

 

We will refer to this rule as "A<B<C", in case you're wondering what mambo-jumbo were talking. Speaking of which, scores that resemble "A>B~C" are technically bugged but they will be at moderator's choice, with the chance of staying in the rankings.

===================================================

UPDATE 16 May 2014: TL;DR

UPDATE 22 June 2014: Typo in A<B<C

Edited by GENiEBEN
Link to comment
Share on other sites

#threads 1,2,3,4,5,6,7,8 and 64. Every other number counts, so in this case its 2,4,6 and 8. These are the ones you divide by the amount of cpu threads you ran with. 2 divided by 2 is 1. One is an even number and so a bugged run.

Link to comment
Share on other sites

#threads 1,2,3,4,5,6,7,8 and 64. Every other number counts, so in this case its 2,4,6 and 8. These are the ones you divide by the amount of cpu threads you ran with. 2 divided by 2 is 1. One is an even number and so a bugged run.

 

One is odd. ;)

I knew what you meant though.

Link to comment
Share on other sites

Let's take an example: -cpus=24,52,60 ; with a physical CPU that has 4 threads (4c/4t, 2c/4t).

Benchmark only cares about every other second thread (24,52,60 -- A,B,C,D,E,). This example will be bugged since 52 divided by 4 will result into an odd number (13) AND is also second in line. If we were to rearrange our original choice, we could return a valid result using: 24,60,52. Notice that since second number divided by 4 is now an even number, the result won't be affected.

 

Unless I'm being dumb, your example would also be invalid because 60/4 = 15 i.e. an odd number :P

 

What's the deal with numbers that don't divide exactly into each other then, I assume they are also invalid?

Edited by ObscureParadox
Link to comment
Share on other sites

So I could maybe get a better understanding of that explanation, could you let me know if this run is good or bad.

And if it is bad; Why?

 

Thank you for your time...

 

What Crabby said.

 

Unless I'm being dumb, your example would also be invalid because 60/4 = 15 i.e. an odd number :P

 

What's the deal with numbers that don't divide exactly into each other then, I assume they are also invalid?

 

Thanks for pointing it out, you are correct, those numbers were for the dual-core cpus, should have picked new ones for 4c/4t.

 

So....in theory then, a totally default run on a X3 Heka for example will always be a bugged run? :P

 

Bullsh1t. I don't buy it.

 

The cpu can actually complete those even threads without carrying over to next thread selection.

 

X3 with 3,15,60 = good

X3 with 4,16,64 = bad

X6 with 6,24,60 = good

Link to comment
Share on other sites

Because it removes part of the fun, we all like benches that you can tweak! Although having said that maybe it's not such a bad idea if system settings still have a big influence, that would still leave room for manoeuvre.

 

I guess another option would be just to shit can it and enable points on another bench. Would also save having to sort out 12k worth of subs!

Link to comment
Share on other sites

I cant see the problem here? why not just use the stock settings for the bench, and disallowe the user to set the threads them self?

 

 

 

Im also for disallow all threat settings...Then there is no problem like we have now :(

The bench is enough tweakable only with tweaking the OS :)

No one wants to bench with math calculator lol :P

Link to comment
Share on other sites

 

The cpu can actually complete those even threads without carrying over to next thread selection.

 

X3 with 3,15,60 = good

X3 with 4,16,64 = bad

X6 with 6,24,60 = good

 

 

You missed the point. Default settings for the bench automatically selects 1, 2, 3, 4, 8. A 3X core running 3 threads should be bugged according to your math.

Link to comment
Share on other sites

You missed the point. Default settings for the bench automatically selects 1, 2, 3, 4, 8. A 3X core running 3 threads should be bugged according to your math.

 

Except it never is bugged on default settings, I know what you meant.

Will update my post tonight with the answers I gave through PM's.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...