• conciselyverbose@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    3
    ·
    edit-2
    1 month ago

    the team dives into game telemetry data (from Oodle) that shows Intel CPUs represent 70% of the error logs compared to AMD with just 30%.

    Uh, what’s the market share? You can’t really provide the one number without the other.

    lol IDK how to link to a user on this app, but look at mox right below me. It’s just presented in a confusing way.

    • mox@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      41
      ·
      edit-2
      1 month ago

      70/30% of the logs, not of the errors. It’s equivalent to what you’re thinking of as market share. (I can’t really blame you for misunderstanding, though; this article is poorly written.)

      The proportion of errors is better explained in another article:

      In fact, for one particular type of error (decompression, a commonly performed operation in games), there was a total of 1,584 that occurred in the databases Level1Techs sifted through, and an alarming 1,431 of those happened with a 13900K or 14900K. Yes – that’s 90% of those decompression errors hitting just two specific CPUs.

      As for other processors, the third most prevalent was an old Intel Core i7 9750H (Coffee Lake laptop CPU) – which had a grand total of 11 instances. All AMD processors in total had just 4 occurrences of decompression errors in these game databases.

      In case you were thinking that AMD chips might be really underrepresented here, hence that very low figure, well, they’re not – 30% of the CPUs in the database were from Team Red.

      • barsoap@lemm.ee
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        They still might very well be over-represented because looking at decompression errors doesn’t isolate the CPU, could also be the disk, or RAM. Or even download though that tends to have independent checksumming. And it might not even be he components it could be cosmic rays, if you run code often enough on enough boxes errors are unavoidable, at least on hardware that isn’t space-grade and/or buried underground.