Honestly those numbers are miserable and not in-line with what I have experienced with M1 (or M2). The numbers make me think it's using the 'efficiency' cores,

Honestly those numbers are miserable and not in-line with what I have experienced with M1 (or M2). The numbers make me think it's using the 'efficiency' cores, or might indicate a lot of memory pressure issues (which seems unlikely at 16GiB) There's a better write-up about compilation performance here: https://build2.org/blog/apple-m1-compilation.xhtml https://build2.org/blog/apple-m1-compilation.xhtml For macOS there is a `taskpolicy` command to set the usage of efficiency and high performance cores. I'd expect that it's using high performance cores by default but you can force it by running `taskpolicy -c utility <program>`. You can also force it to be run on efficiency cores by running `taskpolicy -c background <program>`