AVX-512 can benefit the average Joe, it appears.

  • Mike1576218@lemmy.ml
    link
    fedilink
    English
    arrow-up
    12
    ·
    10 hours ago

    Hand written assembly is pretty common in video, no matter what they say. All modern video codecs have hand written assembly for all modern SIMD extensions, even on ARM. They didn’t say anything about where these numbers come from. Likely compared against unoptimized C code. There will never be a case where having AVX-512 will give you that kind of speedup, because there will be fallbacks for more common extensions.

    • xan1242@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      4
      ·
      8 hours ago

      It’s mostly because AVX-512 doesn’t get used too well by compilers even today.

      However, what makes this impressive for me is that it is x86 after all. ARM is way easier to write assembly for.

  • BrikoX@lemmy.zipOPM
    link
    fedilink
    English
    arrow-up
    25
    ·
    edit-2
    11 hours ago

    Sadly, Intel takes another loss here.

    There is an issue, though: Intel disabled AVX-512 for its Core 12th, 13th, and 14th Generations of Core processors, leaving owners of these CPUs without them.

      • deegeese@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        1
        ·
        35 minutes ago

        Probably some BS market segmentation move.

        I imagine they noticed only certain server customers were using those extensions, so decided to limit them to high margin server SKUs.

        It would have been a smart move if there weren’t competitors putting that instruction in every CPU.

        • BrikoX@lemmy.zipOPM
          link
          fedilink
          English
          arrow-up
          2
          ·
          9 hours ago

          True, though it’s worth noting that AMD focus efficiency means that there isn’t a lot of extra performance you can get from their modern CPUs with overclocking.

          • boonhet@lemm.ee
            link
            fedilink
            English
            arrow-up
            8
            ·
            9 hours ago

            I think it’s less because of their efficiency focus and more because the chips already auto-overclock to reasonably high levels.

            • BrikoX@lemmy.zipOPM
              link
              fedilink
              English
              arrow-up
              3
              ·
              9 hours ago

              I meant more of the whole approach of designing chips with efficiency as a top priority which means they get the best performance they can within their efficiency targets, which is always more optimal than users tinkering on their own. Efficiency and performance are kind of different sides of the same coin.

    • dev_null@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      6 hours ago

      It’s handwritten assembly as opposed to bytecode generated by a compiler, from handwritten higher level language.

    • BrikoX@lemmy.zipOPM
      link
      fedilink
      English
      arrow-up
      4
      ·
      9 hours ago

      It’s about code optimization and efficiency. Most assembly code these days just relies on compilers for optimization as hand optimizing is extremely time-consuming work.

      • propter_hog [any, any]@hexbear.net
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 hours ago

        To add to this, it’s also very easy and very likely to write assembly that has zero speedup or even significant slowdown versus what the compiler will write.