If you look at the current 2020 macbook pro 16” offerings you’ll see that the 2.3ghz build is more expensive than the 2.6ghx. This is because this is the base speed that all cores sustain. The 8-core can sustain a lower frequency but there are more cores. However if not all cores are needed the boost speed is up to 4.8.
Your 2018 intel processor probably is a 6-core, so it has higher base frequencies but fewer cores, but likely can only sustain lower frequencies for the same amount of cores when compared to the 2019 2.3ghz.
I also did some benchmark using webpack and my node stack against a 64gb ram 2.3ghz i9 macbook (2019) and the M1 macbook was on par or faster. Node was compiled natively for darwin arm.
Both machines were from the same time machine restore, and to simulate a normal environment I had safari with about 30 tabs, VS Code, and a mongodb instance running in both.
Also as a bonus Safari loads up about 5+ seconds slower on the 64gb ram macbook 16”.
I believe the way the M1 works means memory usage will work differently too. I wouldn’t go so far as to assume you would need 32gb to maintain any performance advantages... certainly doesn’t help the 16” here.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If you look at the current 2020 macbook pro 16” offerings you’ll see that the 2.3ghz build is more expensive than the 2.6ghx. This is because this is the base speed that all cores sustain. The 8-core can sustain a lower frequency but there are more cores. However if not all cores are needed the boost speed is up to 4.8.
Your 2018 intel processor probably is a 6-core, so it has higher base frequencies but fewer cores, but likely can only sustain lower frequencies for the same amount of cores when compared to the 2019 2.3ghz.
I also did some benchmark using webpack and my node stack against a 64gb ram 2.3ghz i9 macbook (2019) and the M1 macbook was on par or faster. Node was compiled natively for darwin arm.
Both machines were from the same time machine restore, and to simulate a normal environment I had safari with about 30 tabs, VS Code, and a mongodb instance running in both.
Also as a bonus Safari loads up about 5+ seconds slower on the 64gb ram macbook 16”.
I believe the way the M1 works means memory usage will work differently too. I wouldn’t go so far as to assume you would need 32gb to maintain any performance advantages... certainly doesn’t help the 16” here.