Skip to content

Add MacBook Pro 14 M1 Pro #539

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

zuziaka
Copy link

@zuziaka zuziaka commented Nov 10, 2024

Checklist

  • I performed all steps to correctly run XcodeBenchmark.
  • I used Xcode 15.0 or above.
  • I attached a screenshot with a compilation time and other fields
  • I confirm that Time column is still sorted.
  • The content in cells is centered.

CleanShot 2024-11-10 at 11 01 57@2x

@devMEremenko
Copy link
Owner

Hi @zuziaka,
Thanks for your input!
Could you clarify that you did not use your device during the testing, and that low power mode was off?

I am asking because M2 performs better than M1 Pro, which is generally performant.

Screenshot 2024-11-12 at 18 40 33

@bananafish911
Copy link

Hi! @devMEremenko, I think results can be valid, I have same hardware and got same issue... I came here to find relevant reports from others, because I also got weird results on m1 pro 6p2e - 237s. Previous benchmarks were made more than year ago and results were fine, something around 110-150 seconds, , so IDK what caused the issue, osx or xcode update.

Preconditions: low power mode off, no extra devices connected, just charger and mouse, reboot, startup apps are not launched or even force-closed before benchmark.

I think maybe apple has changed something in how mac os prioritise usage of hardware resources, eg. they limited max performance to avoid overheating or supress other issues at full cpu load on some models. Attaching extras screenshots of asitop, is says peak cpu wattage was ~20w during test.

results during testing before testing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants