Announcement

Collapse
No announcement yet.

Apple M1 is being recognized as a 4 core 8 thread CPU on asahi linux

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Apple M1 is being recognized as a 4 core 8 thread CPU on asahi linux

    As stated in the title. When running Performance Test in Asahi Linux it recognizes the CPU as an 4 cores, 8 threads CPU @2064 Mhz (which is the E-core clock frequency if i am not mistaken)
    and i get about half the CPU mark that i would get running the same test under mac OS
    Is this expected behavior? i provided screens from both results on both OS

    Attached Files

  • #2
    Both screen shots show 8 threads. So the benchmark results should be valid in both cases.

    The M1 cores are not all the same. Maybe that is why Asahi Linux identifies it as 4C/8T.
    4 cores are designated for efficiency, while the other 4 remain destined for performance.

    PerformanceTest doesn't control the clock speed. So even if the O/S and thus PerformanceTest are reporting 2064Mhz, all the core might not run at that speed.

    So likely there is some other explanation for the score difference. Maybe Asahi doesn't have full support for all the power states for this CPU?

    Comment


    • #3
      Thanks for your quick answer.
      I should have explained myself better
      Both test run on the same dual boot machine so hardware is the same
      if checking clock speed with htop on linux i can confirm that all cores at being used at full speed during benchmark
      Only hardware i assume is not being used in asahi linux is the NPU

      Comment


      • #4
        Sorry for the double posting as i cannot edit unapproved posts apparently. I now get (and was aware of) what you mean when saying not all cores are the same (E-core vs P-core), which is why i further stated that both tests were run on the same machine

        Comment


        • #5
          You can try running a series of the benchmarks on each and see if the results are consistent. Perhaps background activity was occurring during the testing that may have affected one of the runs.

          Comment

          Working...
          X