View Full Version : Why no 2.3ghz Air?

Jul 21, 2011, 12:19 PM

My friend is new to Mac after 20 years with PC. He wanted to know why Apple can't/won't put in a 2.3ghz chip in the Macbook air. Is it because Apple wants to stratify their lineup or is it because of chip size in such a compact machine?

I thought it was because the chip would be too big, use too much power and generate too much heat in such a small machine. I think it's a matter of time before they put it in.

Whaddaya you say?

Jul 21, 2011, 12:22 PM
because there are no 2.13ghz in the sandybridge series which have the 17W TDP as the ones currently offered in the MBA lineup. Apple is basically not giving up battery life/heat.
for your friend, advise him to read the first page of this site where the new mba's compare to 2.67ghz i7's from last year.

Jul 21, 2011, 12:26 PM
Clock speed is not that important, the architecture is. The sandy bridge is over 2x more powerful than last year's higher clocked c2d model's.

Also the sandy bridges have a turbo boost mode, IIRC the 1.7 can turbo boost to 2.7ghz.

Jul 21, 2011, 12:26 PM
Just tell your friend, that more MHz doesn't mean more power. A 3GHz Pentium 4 with 3GHz and crappy Netburst-architecture would be nice, hmmm? ;) It was Intels greatest move to kill the MHz-race with the dead of Pentium 4.

Jul 21, 2011, 02:23 PM
Yeah, the clock speed might make them sound slow-ish, but they are much faster than the previous gen! http://scottty.com/imgs/signature_silverapple.jpg

Jul 21, 2011, 02:39 PM
here's a clock speed analogy. In the P4, you have that really long pipeline and periodically, there'd be pipeline flushes that empty out the pipeline and the CPU becomes idle waiting for the pipeline to fill up again. Think of each pipeline flush as a "mistake."

Basically, the P4 while it runs really fast, it makes tons of "mistakes" and thus has to waste lots of time to correct them and it only does one task at a time. The Sandy Bridge architecture while running slower clock speed wise, makes far fewer mistakes, has a much shorter pipeline so when it does make a mistake, the time to correct it is much shorter, and it can carry out 4 tasks at a time, and runs way cooler as well.