11 comments

  • GeekyBear 55 minutes ago
  • asimovDev 28 minutes ago
  • galad87 1 hour ago
    Cool, but Apple didn't announce any M6 Pro yet, so where is this coming from?
    • fartfeatures 1 hour ago
      I thought they were skipping the M6 pro chips (or is that just the max and ultra?) to accelerate AI focused M7.
      • reitzensteinm 33 minutes ago
        If they’re rushing the M7, it’s possible the M6 Pro and Max will be MacBook Ultra only. It would certainly give it quite a halo.
      • GeekyBear 43 minutes ago
        The word was that they weren't going to ship systems with the M6 Pro, Max or Ultra.

        The M7 generation has updated the tensor instructions in the GPU cores and they want to ship that ASAP.

      • SXX 45 minutes ago
        This was just rumors like 99% of other Apple-related news.
    • mdp2021 1 hour ago
      Probably internal tests?

      The software identifies the hardware, performs the benchmarks, and sends the heading and results to the Geekbench DB. Somebody who had the machine at hand must have run it.

    • tristanj 1 hour ago
      Internal leaks, these happen frequently. Employees have access to these devices for months prior to launch. Someone ran a benchmark and uploaded it on a machine they weren't supposed to.
      • gizajob 52 minutes ago
        I find that hard to believe at Apple. Not even possible that it’s accidental. They have their own internal tools, all packets leaving the network will be interrogated, leaking data is a sackable offence… if it’s in the geekbench database then it’s there because they put it there.
        • discordance 4 minutes ago
          It’s happened in the past. Like that employee who left the unreleased iPhone in a bar by accident.
        • swiftcoder 47 minutes ago
          > Not even possible that it’s accidental. They have their own internal tools, all packets leaving the network will be interrogated, leaking data is a sackable offence

          This is a story that folks like to tell, but it's not really how things work - at least since they stopped letting Steve Jobs lock all his engineers in the conference venue.

          Leaks are a sackable offence at every tech firm, deep packet inspection firewalls are used all over the place, information leaks like this still happen pretty much every single product cycle.

          • VerifiedReports 26 minutes ago
            People love to tell stories about how stuff is done at Apple, which are often utter bullshit.

            Not to mention that Apple has a huge number of teams, and no absolute standards across them. People would be shocked at the things Apple DOESN'T do.

            Then again, with the current state of their QA, I think it's becoming clear what Apple doesn't do much of anymore.

        • dainiusse 34 minutes ago
          +1 . The only case it is allowed is Apple's own marketing team.
    • shim__ 1 hour ago
      How does Geekbench even verify what CPU I'm using? Couldnt you inject forged data and add a even faster M100?
  • a3w 1 hour ago
    >4k? Thought not would barely twice that of an 15 year old CPU, but it of course is geekbench 7, not 6 or 5!

    So this is different and faster than such a result in the old scoring would have implied.

    • fsh 16 minutes ago
      It is not quite twice the score of a 6 year old Apple M1 though. And this is with much higher clock speeds (4.8 GHz vs. 3.2 GHz).
  • leptons 1 hour ago
    Under exactly what cooling conditions? And for how long did it sustain this speed?
  • mdp2021 1 hour ago
    And how much would it cost?

    In the current times performance/price seems to be increasingly important.

    (Not to mention several other factors that once did not even exist, or were irrelevant.)

  • aurareturn 1 hour ago
    Wait. What?

    This is actually the M6 Pro and not the M6. It has 18 CPU cores to the M6's 12. The scores line up as well.

    Reports have said all along that Apple is skipping M6 Pro/Max to focus on M7 generation.

    I can't remember the last time an Apple chip got leaked like this.

  • hnd9q09qk4 51 minutes ago
    [dead]
  • hncbw02z5a 58 minutes ago
    [flagged]
    • rrr_oh_man 56 minutes ago
      Load-bearing comment
    • danaris 45 minutes ago
      Would you mind elaborating, for those of us who don't live and breathe this stuff?
  • wartywhoa23 1 hour ago
    [flagged]
    • ErneX 1 hour ago
      Title is “highest single core score” so it’s the highest of every cpu tested on geekbench so far, not just of the subset of Apple CPUs.
    • zer0zzz 1 hour ago
      Highest among all CPUs. This isn’t new for Apple. Their stuff frequently bests ryzens etc at single threaded perf
    • nottorp 1 hour ago
      I noticed a whiff of panic at the iphone 18 launch. Opened macrumors and there like 6 articles in a row about preordering the phone, how soon you can get the phone when you preorder, how long the queues are etc.

      Guess they didn't get the expected # of preorders.

      • JSR_FDED 13 minutes ago
        I doubt Macrumors knows what the iPhone 18 preorder numbers are.
      • ErneX 1 hour ago
        That might be true but they do all those pieces with every iPhone launch. They just churn out content a lot during iPhone launch period.
        • nottorp 33 minutes ago
          I've never seen 6 in a row before. And that's not counting the "feature list" articles.
  • OsrsNeedsf2P 1 hour ago
    I'm currently in the middle of porting a game from 2004 to run on MacOS via wine. On a 5000$ Macbook Pro, I'm getting about 4 FPS. This has multiple causes, including the game being single threaded and running through Rosetta, but damn is it hard to get good single core performance out of Macbooks.

    Out of curiosity, I also ported the game to arm Linux with fex + upstreamed the wine patches in about a third the time and there's no FPS issues

    • mirsadm 1 hour ago
      If anything it's the exact opposite. They're ridiculously powerful with more memory bandwidth than pretty much any equivalent PC. It is easy to make sloppy software because you can get away with so much.
    • CJefferson 36 minutes ago
      Something is going horribly wrong. I don't know what it is (without your code I don't know), have you profiled where it's going wrong? There's no way a game for 2004 would be that slow.

      If you want help, I've done some similar work, you could pop it up on a github repo or something. What is the game?

    • SXX 55 minutes ago
      What porting you talking about exactly? Packaging existing binaries? Compiling source code making it more compatible with Wine?

      In my experience as game developer and porting C++ code tells such difference usually mean there are something really wrong with syncronization primitives. So 99.99% of the time code does nothing just waiting for something to unlock.

    • galad87 41 minutes ago
      Running something with "Wine" doesn't usually mean "porting", "porting" means making a native binary that doesn't run through an emulation layer.

      Anyway, probably you are trying to run a 32-bit executable with Rosetta, that won't be fast, because Rosetta was never meant to run 32-bit things and has got a lot of pitfalls.

    • logicallee 37 minutes ago
      Thanks for sharing your experience.

      I recommend you try giving your AI an open ended task like, "it's at 4 fps even though it's a 22 year old game and the raw hardware performance is many orders of magnitude higher. Maybe due to running under Wine and Rosetta. Please figure out the simplest way you can unlock usable performance (30-60 FPS) short of decompiling, reverse engineering, and reimplementing the full game yourself natively. Maybe there is something else you can figure out for the performance unlock. The hardware is definitely there, so there has to be a way. The game is running so make sure you don't break it. Keep the same game behavior."

      Regardless of which AI you're using, it will be able to figure something out in a few hours. 2004 pc's were 500-800 mhz, 128 MB RAM, and if they had a GPU at all it was 16-32 MB, 0.2-1 GLOP.

      Your AI should be able to figure out a way to get it running in realtime.