Slashdot Mirror


PCMark Memory Benchmark Favors GenuineIntel

javy_tahu writes "A review by Ars Technica disclosed that PCMark 2005 Memory benchmark favors GenuineIntel CPUID. A VIA Nano CPU has had its CPUID changed from the original VIA to fake GenuineAMD and GenuineIntel. An improvement of, respectively, 10% and 47% of the score was seen. The reasons of this behavior of FutureMark product are not yet known."

8 of 298 comments (clear)

  1. Money by TheRealMindChild · · Score: 5, Insightful

    The reasons of this behavior of FutureMark product are not yet known

    Easy. Intel paid them to make it that way.

    --

    "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    1. Re:Money by ShieldW0lf · · Score: 5, Insightful

      Moral of the story is, when you're dealing with code like this, where it has the capacity to influence who receives billions of dollars and who doesn't, well, you can't trust it if it's closed source and not subject to public scrutiny.

      Closed source test suites cannot be trusted, shouldn't even be considered by potential purchasers, and have been misleading the public for years and years. This is mute evidence to the fact.

      --
      -1 Uncomfortable Truth
    2. Re:Money by clickclickdrone · · Score: 5, Insightful

      This is just a classic example of amateur (poster) vs professional (Intel dev team).

      Writes an (anonymous) Intel representative.

      --
      I want a list of atrocities done in your name - Recoil
    3. Re:Money by Anonymous Coward · · Score: 5, Insightful

      Here, sir, is the Internet, which you have won fair and square.

    4. Re:Money by Goaway · · Score: 5, Insightful

      "Everything I don't know how to do is easy!"

  2. Possible semi-benign explaination? by davidwr · · Score: 5, Insightful

    This definitely requires clarification from the creator of the benchmark.

    It is possible that the benchmark uses the CPUID to change how the benchmark works, for example, to work around known flaws in a given chip. If this is the case, then the problem is not "omyghoshitplaysfavorites" but rather lack of full disclosure that the benchmarks are not directly comparable across different chips. In the most benign scenario, this could be someone at the benchmark creator's shop forgetting to tell the documentation team. This is still a very serious issue, but it's not fraud.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
  3. Moronic or Corrupt? by OmniGeek · · Score: 5, Insightful

    Does it really matter whether the cause was "incredibly sloppy coding" or "Intel bribed them?" Either way, their benchmark cannot be trusted, and trustworthiness is ESSENTIAL for a benchmark. If anyone pays serious attention to this (which, having read TFA, it seems to merit), then FutureMark is toast.

    --

    "My strength is as the strength of ten men, for I am wired to the eyeballs on espresso."
  4. Re:troll? really? mod up again! by deanoaz · · Score: 5, Insightful

    >>> Contrary to the claims of OSS proponents, the code isn't really more trustworthy if it's open, because not all of us are programmers. If we were (hell, even if most of us were), that'd be true. As things are, though, closed source is only slightly less trustworthy than open source.

    I disagree. At this point there is controversy. It will be explained by the vendor and people will have to either accept the explanation or not.
    If it were open source, the facts of how the code behaves could be determined by third parties and publicized. We wouldn't have to take anyone's word for it.

    --
    If 'the people' in Amendment 2 are 'the state' then Amendments 1, 2, 4, 9, and 10 benefit the state, not you.