| |
| | Instructions per clock (John R. Mashey) |
 | | b) Over time, clock rates would tend to improve for everybody at about the same rate, simply because people tended to get the newest process technology at about the same times, and clock rates were often driven by access times to affordable SRAMs for off-chip L1 caches. |
 | | More often than not, one thinks of a cycle either as the time to do an ALU operation (specifically, an integer add), or maybe, a cache access. |
 | | In general, the scalability of a design (which was what IPC was trying to get at, i.e., what would be achieved by better processes) is *not* determined by the number of gate delays in most paths, but by the number of gate delays in the *slowest* path, and it only takes one. |
| yarchive.net /comp/instr_per_clock.html (946 words) |
|