The Pixel 8 and Pixel 8 Pro have now turned up on the FCC's database, just over a month before their official launches alongside the Pixel Watch 2. So far, the FCC has outlined five model number variants, all without rumoured Wi-Fi 7 connectivity.

So according to an FCC filing the Pixel 8 and Pixel 8 Pro will support Wi-Fi 6E but not the newer Wi-Fi 7.

For a comparison, you can get a max speed of 9.6 Gb/s with Wi-Fi 6E, while Wi-Fi 7 can reach a speed of 46 Gb/s.

  • zephyreks@programming.devEnglish
    2·
    10 months ago

    There’s no way the in order A53 from 2012 gets even close to the performance of the OoO A78 from 2020.

    • StarDreamer@lemmy.blahaj.zoneEnglish
      1·
      10 months ago

      Didn’t know one is in-order and the other is OoO. The A53 is still being used for new products by Nvidia in 2020 (Bluefield-2). So there must be some merit to it or Nvidia is cheaping out on stuff

      The BlueField-3 uses the A78 and unfortunately I don’t have one to test. I’m basing everything I know based on conference talks. I do know apparently the A78 does not have working performance counters for perf which makes it a pain to debug.

      That being said, a 2023 Mid-end Xeon gets you up to 60Gbps TCP single flow (100Gbps ConnectX-6 NIC) So maybe that’s a better comparison? Might need to account for all the other x86 optimizations

      Also, I think the bottleneck for TCP processing is branching, not memory access. So I’m not sure if OoO execution would help much. Would the A78 have improved branch predictors?

      • zephyreks@programming.devEnglish
        2·
        10 months ago

        A53 is used for low-power and low-cost applications… It’s a “good enough” CPU that has really good performance/area.

        Perfect performance counters for OoO is really hard.

        OoO also makes BP more useful. An OoO processor without BP isn’t very useful because there aren’t that many instructions between branches… So, generally, modern OoO processors dedicate far more resources to BP.