Jump to content
HWBOT Community Forums

Mr.Scott

Members
  • Posts

    3337
  • Joined

  • Last visited

  • Days Won

    59

Posts posted by Mr.Scott

  1. If you have nothing better to do feel free to report all my "standard stock clocking runs" with bad scores and make yourself ridiculous.

     

    And please go through all the submissions in the core 2 stage that don't have correct screenshots too. Would save us all a lot of time ;)

     

    I also would suggest you as "screenshot prove guy" for Hwbot, you can look for not 100% correct screenshots all day then!

    Not interested.:P

    Just proving a point is all.

    I'm done with this conversation.

  2. Yea, sorry for that, i am quite new to all this "Hwbot rules".

     

    I am not talking about doing the screenshot 100% right here. It was just an example that on the one hand people are taking correct screenshots serious - that is good - but on the other hand the rules are not clear to people who do not read all the threads in the forum.

     

    I just say someone from the hwbot-staff should take care about this, and just set the rules clear on the Team Cup Page.

    You missed the point. The point was, instead of b1tching and complaining about the rules, and being so quick on the report button to try to get submissions removed, one should be a little more concerned that one's own submissions conform to the rules.

    When in doubt, ASK somebody first.

  3. I remember someone reporting me in the last stage because i did not include the "optional" mem tab, and i had to rerun my results.

     

    This is an overclocking competition and not a "who finds the best arguments to bend the rules to his needs competition".

    People who live in glass houses shouldn't throw stones.;)

     

    http://hwbot.org/submission/2278860_robot_3dmark06_2x_geforce_8800_gtx_27387_marks

    No subtest details in SS, no ORB link.

  4. I'm not writing the rules right now, I'm just participating here:)

     

    Most of the gains from the pcmark tweaks can be explained once you know how they work, right? That's not the case here - I've never seen 32 threads per core be a very efficient way of running a benchmark. What is it with this benchmark that makes it scale that way?

    I wasn't trying to antagonize you.;)

    Here's what I've found after tweaking UCB for quite a while now.

    There is no set pattern for number of optimal threads. It varies across platforms. The 'sweet' combination for threads for say 939, is not the same combination that you would want for socket A or AM3 for example. Number of physical cores seems to make no difference either. I've been testing thread combinations for UCB before Frank even knew there was a tweak. I turned him on to that. The combinations he uses on his Intel submissions aren't even close to being good on an AMD setup, so there's a difference in the way the bench is calculated right off the bat, based on CPU manufacturer.

  5. The question here is if ucbench calculates different things when forcing 64 threads rather than the default number of threads. wprime is very easy to understand that way, there the work is split into x number of threads and all threads run simultaneously. That COULD be the case with UCBench, but it's not that clear - it just seems odd to me that you gain 20% this way

    Slippery slope you're approaching here. The same thing could be said for most of the PCM05 tweaks. You can't have it both ways, so choose your words and battles wisely. Honestly, there's quite a few threads where people have asked if it was 'legal' already. The answer has always been yes, including from the staff. Why all of a sudden is this such a problem?

    Anybody that looks at a tweaked submission could easily see what was tweaked and just mimic it.

×
×
  • Create New...