• atrielienz@lemmy.world
    link
    fedilink
    English
    arrow-up
    78
    ·
    edit-2
    16 hours ago

    Someone else already explained (after watching the video) why this test is flawed.

    "This is purely from a broken test. Watch the video and you’ll see that its not testing with the same power limits.

    17w tests are actually 16w vs 20w+ and 35w test is 25w vs 35w

    This leads to drastically higher clock speeds on both cpu and gpu as seen in the video and thus higher fps (and power draw, so lower battery life)

    https://vger.to/lemmy.dbzer0.com/comment/22164759

    • Dnb@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      19
      ·
      14 hours ago

      Thanks for linking my post, it’s a shame Tom’s hasn’t updated their post as it’s discussed in the comments there too.

      • atrielienz@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        8 hours ago

        I tried to make sure it got quoted but my app doesn’t do well with copying the user so I did it this way so people would know it certainly wasn’t me who saw the flaw.

        If it helps UFD tech on YouTube also reported off the Tom’s Guide article, spouting the same flawed data as the headline.

    • NuXCOM_90Percent@lemmy.zip
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      13 hours ago

      Heh, my money was on it being shaders like most times this comes up. Steam+Proton gets a downloaded shader precache. Windows does it live.