Slashdot Mirror


AMD Rejects SYSmark Benchmark

Deathspawner writes "In an unusual move, Advanced Micro Devices has issued a press release rejecting its endorsement for the industry recognized benchmark SYSmark 2012. Developed by BAPCo and backed by industry heavyweights such as Dell, Intel and Hewlett-Packard, AMD has stated that BAPCo both has tuned SYSmark to create bias in favor of its competitor, and that its benchmarks are not relevant for the audience it targets. Also noted is a complete lack of heterogeneous CPU+GPU testing. Techgage tears apart AMD's claims to see if they are valid, while also evaluating the overall usefulness of SYSmark and the impact it can have on consumers."

24 of 118 comments (clear)

  1. Not the only ones. by ustolemyname · · Score: 5, Informative
    1. Re:Not the only ones. by Groo+Wanderer · · Score: 2

      You are wrong about both the site, and how I left.

                  -Charlie

  2. link to clean article by cheeks5965 · · Score: 2
    --
    -- Flame me and I will happily flame you back. Bring it!
  3. Once again... by ThoughtMonster · · Score: 2

    This would've been avoided if these "industry standard" tools were released as open source. It would be interesting to see if such a development will arise from this dispute.

    1. Re:Once again... by h4rr4r · · Score: 3, Insightful

      There is always the Phoronix test suite. They might be chicken littles, but their test suite is at least open and repeatable.

    2. Re:Once again... by meerling · · Score: 3, Interesting

      Of course, the more the people being tested know about how it's tested, the easier it is for them to cheat.
      (Plenty of past history from both Nvidia and ATI doing that with video cards.)

      (Note: Always investigate claims of benchmark cheating, sometimes it's a misunderstanding. One example deals with a claim of cheating because an optimization routine found the same process being hit constantly, so it cached it. There were screams of cheating and 'tuning' the driver to trick the benchmark when all it really was is caching doing what it's supposed to. Even though it did give artificially high scores in that one test. Once the issue was known, the benchmarkers changed their program to not do a stupid repetitive test that would just get cached.)

      Of course this isn't an issue of cheating, but it sure feels like it. Makes you wonder what AMD is really worried about...

    3. Re:Once again... by hairyfeet · · Score: 5, Informative

      Well if they used the Intel compiler then it is for all intents and purposes useless as Intel has been rigging their compiler with a "Genuine_Intel" flag and if the flag isn't detected dropping all SSE and above optimizations and instead running in slow ass x87 mode. Last I read despite being ordered to change their behavior Intel is STILL putting out compilers with the evil bit on and haven't done anything to alert previous customers of their douchebaggery.

      So I wouldn't be so quick to just dismiss out of hand, after all, who would have thought that Intel would rig their own compiler to cheat? I can't even imagine how many programs out there have been compiled using the Intel compilers which makes every single program written using their tool chain rigged against AMD and Via.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    4. Re:Once again... by cynyr · · Score: 2

      you mean like GCC?

      AMD has contributed a lot to GCC in the past.

      --
      All of the above was encrypted with a Quad ROT-13 method. Unauthorized decryption is in violation of the DMCA.
    5. Re:Once again... by Anonymous Coward · · Score: 2, Informative

      The most recent versions of Intel's compiler clearly document the evil behavior in the description of the code generation options, so at least it's not hidden any more. You can also mostly disable the evil behavior, if you are willing to sacrifice the runtime code-path selection that allows you to use SSEx on hardware that supports it while retaining compatibility with earlier machines.

      Still, any benchmark using Intel's compiler can't be trusted unless it is fully open-source, including the exact compiler flags used.

  4. Hmm by Spykk · · Score: 3, Interesting

    It seems like AMDs biggest complaint is that the benchmark isn't offloading CPU intensive tasks to the GPU. It is pretty hard to take them seriously when they are complaining that the benchmark favors their competition by actually benchmarking the CPU.

    1. Re:Hmm by afidel · · Score: 3, Interesting

      Well, a benchmark with 2012 in the name certainly shouldn't be using two non-GPU accelerated web browsers and Acrobat 9! They really do have a point that currently released software is doing a much better job of using their more well rounded systems then the benchmark is. It's a system benchmark not a CPU benchmark (we have SPEC for that).

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    2. Re:Hmm by Billly+Gates · · Score: 2

      AMD is also betting big on Fusion and hardware accelerated HTML 5 with IE 10/Windows 8. They plan on making x86 tablets in which, some of their CPU's are barely faster than an Intel Atom but have a GPU inside as powerful as an ATI 6xxx HD. These benchmarks will be crap on the Llamo chip, but in real world use with Windows 8 and Flash 10.3 and higher you can run 1080p HD video fluidily without a sweat.

      I would be irrated and concerned too if I were AMD, as people would get a false impression on their low end Llamo netbook chipsets as non Windows 8 ready.

  5. Intel's compilers by KiloByte · · Score: 5, Interesting

    Quite a bit of Windows software is compiled using Intel's compilers, and they are intentionally made to sabotage performance on AMD chips. When looking at CPUID, instead of checking the features they want, they look for that _and_ the CPU being "GenuineIntel", and if not, the code chooses the worst possible implementation. This includes some major scientific math libraries and a part of popular benchmarks.

    --
    The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    1. Re:Intel's compilers by Rockoon · · Score: 3, Informative

      That's great! Why doesn't AMD go and write a compiler of thier own and give it away for free?

      Its called Open64.

      --
      "His name was James Damore."
    2. Re:Intel's compilers by Rockoon · · Score: 3, Interesting

      In recent tests Open64 is better than ICC at producing code that executes on the Pentium Dual Core T2370

      In fact, its not just better... its significantly better.

      Stop talking out your ass.

      --
      "His name was James Damore."
  6. AMD quit because it was losing. by blair1q · · Score: 2

    AMD has chosen an architectural roadmap that makes the GPU and CPU part of the same APU. SYSmark does not measure 3-D graphics performance. At all. So while AMD is pursuing a path that will give its APUs greater overall performance than the CPUs they contain, they are actually hamstringing themselves in the CPU-only testing arena, because the CPU portion of thier APUs will seem relatively lower in performance at the same price point.

    AMD's proper course of action should have been to promote an APU-specific benchmark. Instead, it tried to change SYSmark to do something it doesn't do.

    It was denied the right to twist the benchmark in its favor. Rather than coming up with the obvious solution of spinning off a new benchmark consortium to develop an APU-specific test, it started crying and ran to its room shouting, "I hate you! I hate you! I hate you!"

    AMD is, really, behind a major 8-ball right here. It has, again, put all of its eggs into a rather hopeful basket, and come up with fewer than expected. At least this time, unlike with the Barcelona debacle, it isn't doing it while roller-skating blindfolded through a car-wash. That time it cost them their fabs. They don't have much left to sell.

    It's little wonder that it's not having an easy time of finding a new CEO.

    1. Re:AMD quit because it was losing. by hedwards · · Score: 2

      So then the answer is to stop innovating unless everybody else is doing the same thing?

      I recently bought a laptop with a Llano chip in it, and I love it, the battery life is great, and the performance in terms of things that people normally do is great as well. This isn't about sour grapes, this is about a benchmark that's lost its way and isn't of particular use. If it's focusing so heavily in the way that it is, I'm not sure how I'd use the scores to figure out what processor to get.

  7. Re:AMD a bit lost by Anonymous Coward · · Score: 4, Insightful

    A benchmark that doesn't test realistic workloads is of little use for evaluation if a system is fit to purpose.

    A benchmark that isn't open about its methodology is at best worthless and at worst directly misleading.

    I think they are pissy because they dont stand up well to the competition.

    I think the complaints sound quite reasonable on the face of it. If it is true that Nvidia and VIA have also resigned, that just leaves Intel waving their cocks around at any rate.

  8. Re:Maybe AMD should get off their butts by Ogi_UnixNut · · Score: 4, Informative

    Um, they do have their own compiler: http://developer.amd.com/tools/open64/Pages/default.aspx

    Seems to be both free to download, and comes with source code so you can go over it if you wish.

  9. Re:A CPU benchmark absolutely should by Moridin42 · · Score: 2

    Okay, but SYSmark isn't a CPU benchmark.

    From BAPco's SYSmark page:

    SYSmark® 2012 is the latest version of the premier performance metric that measures and compares PC performance based on real world applications.

    As stated by the GP, there are CPU benchmarks such as SPEC's. But SYSmark isn't one and AMD alleges it isn't designed to benchmark what they say they're benchmarking.

    --
    I don't expect morality, equality, consistency, or justice from the law. I expect only legality.
  10. Re:I predict... by hedwards · · Score: 2

    Intel, you mean the same Intel that got caught paying integrators not to use AMD chips?

    It's a pretty gross mis-characterization to suggest that criticism of the size of Intel is based upon size rather than how they got to be so big.

  11. Re:AMD a bit lost by Moridin42 · · Score: 2

    I'm not sure you understand the point of benchmarking.
    You can benchmark a lot of stuff. But its pointless to benchmark HD read/write speeds when what you're interested in is FLOPS. So there are benchmarks which see how many floating point ops your system can do. And there are benchmarks about hard drive performance. But there tends not to be one benchmark to rule them all.

    BAPco say that SYSmark is a benchmark for real-world business app performance. But AMD say SYSmark doesn't utilize the GPU in any way.

    Given that modern operating systems go to GPUs for rendering, which they're good at, and freeing up CPU time for CPU stuff, SYSmark isn't benchmarking what they claim to be benchmarking.

    Which would make SYSmark a pointless benchmark.

    --
    I don't expect morality, equality, consistency, or justice from the law. I expect only legality.
  12. Re:Maybe AMD should get off their butts by compro01 · · Score: 5, Informative

    ...and make a compiler.

    They did. It's even GPL licensed.

    http://developer.amd.com/tools/open64/Pages/default.aspx

    --
    upon the advice of my lawyer, i have no sig at this time
  13. But, see, by Dremth · · Score: 2

    I don't care about SYSmark telling me whether any given Intel CPU is better than any given AMD CPU or vice versa. What I really care about is finding out if the newly released Intel/AMD [insert arbitrary name here] CPU/GPU is truly better than the old Intel/AMD [insert arbitrary name here] CPU/GPU. By the time I get to the point of looking into concrete numbers from benchmarks, I've already decided whether I'm going to get an AMD or an Intel processor. The real problem that I have with all this benchmarking crap is why these manufacturers don't just provide us with coherent naming schemes for their CPU's (and GPU's too) so we as customers can fully understand the product they're trying to sell us.