3 ms·
This closely matches what happened to processor naming. It used to be that any two (CISC) CPUs with the same frequency were about on par with one-another, so we
by derefr 7y ago
This closely matches what happened to processor naming. It used to be that any two (CISC) CPUs with the same frequency were about on par with one-another, so we just called processors by their frequency. As soon as processors started adding things like SSE, though, that went out the window, since now “one cycle” could do arbitrary amounts of work, and also consume arbitrary amounts of electricity. So now we instead group processors by their manufacturer and model, and compare processors by “generation”, which ends up being a loose count of each time each vendor has done a large redesign that enabled efficiency increases beyond “just” a process-node shrink.
So: is there any analogous new convention for naming process nodes, now that you can’t just refer to them by their size? If there’s a dropdown select box on some form internal to e.g. Apple, where an engineer specifies what process-node of what fab they’d like to use to print a new chip—and said list has had some thought put into making it intuitively unambiguous—then what would the items in that list look like?
- neodymiumphish 7y agoYep, but now we refer to chips by their cost, instead. AMD Threadripper 3990X : $3990
- warrenm 7y agoThat's only true when it's first released
- Klinky 7y agoThat was never the case. Go back even to 386 days and AMD or Cyrix were not always on par with Intel clock for clock. This only really flipped when Athlon came out. You also had to think about DX vs SX, if you got L2 cache, 5x86 is really a 486, what is an Overdrive chip?, why does a PR166 CPU run at 100MHz, what is a Celeron, and why is 300A model so much faster than the original 300? Etc etc etc