Cycles per instruction
In computer architecture, cycles per instruction (aka clock cycles per instruction, clocks per instruction, or CPI) is one aspect of a processor's performance: the average number of clock cycles per instruction for a program or program fragment.[1] It is the multiplicative inverse of instructions per cycle.
Definition
The average of Cycles Per Instruction in a given process (CPI) is defined by the following weighted average:
Where is the number of instructions for a given instruction type , is the clock-cycles for that instruction type and is the total instruction count. The summation sums over all instruction types for a given benchmarking process.
Explanation
Let us assume a classic RISC pipeline, with the following five stages:
- Instruction fetch cycle (IF).
- Instruction decode/Register fetch cycle (ID).
- Execution/Effective address cycle (EX).
- Memory access (MEM).
- Write-back cycle (WB).
Each stage requires one clock cycle and an instruction passes through the stages sequentially. Without pipelining, in a multi-cycle processor, a new instruction is fetched in stage 1 only after the previous instruction finishes at stage 5, therefore the number of clock cycles it takes to execute an instruction is five (CPI = 5 > 1). In this case, the processor is said to be subscalar. With pipelining, a new instruction is fetched every clock cycle by exploiting instruction-level parallelism, therefore, since one could theoretically have five instructions in the five pipeline stages at once (one instruction per stage), a different instruction would complete stage 5 in every clock cycle and on average the number of clock cycles it takes to execute an instruction is 1 (CPI = 1). In this case, the processor is said to be scalar.
With a single-execution-unit processor, the best CPI attainable is 1. However, with a multiple-execution-unit processor, one may achieve even better CPI values (CPI < 1). In this case, the processor is said to be superscalar. To get better CPI values without pipelining, the number of execution units must be greater than the number of stages. For example, with six executions units, six new instructions are fetched in stage 1 only after the six previous instructions finish at stage 5, therefore on average the number of clock cycles it takes to execute an instruction is 5/6 (CPI = 5/6 < 1). To get better CPI values with pipelining, there must be at least two execution units. For example, with two executions units, two new instructions are fetched every clock cycle by exploiting instruction-level parallelism, therefore two different instructions would complete stage 5 in every clock cycle and on average the number of clock cycles it takes to execute an instruction is 1/2 (CPI = 1/2 < 1).
Examples
Example 1
For the multi-cycle MIPS, there are five types of instructions:
If a program has:
- 50% load instructions
- 25% store instructions
- 15% R-type instructions
- 8% branch instructions
- 2% jump instructions
then, the CPI is:
Example 2
[2] A 400MHz processor was used to execute a benchmark program with the following instruction mix and clock cycle count:
Instruction TYPE | Instruction count | Clock cycle count |
---|---|---|
Integer Arithmetic | 45000 | 1 |
Data transfer | 32000 | 2 |
Floating point | 15000 | 2 |
Control transfer | 8000 | 2 |
Determine the effective CPI, MIPS (Millions of instructions per second) rate, and execution time for this program.
since: and
Therefore:
See also
- Cycle per second (Hz)
- Instructions per cycle (IPC)
- Instructions per second (IPS)
- Megahertz myth
- MIPS
- The benchmark article provides a useful introduction to computer performance measurement for those readers interested in the topic.
References
- Patterson, David A.; Hennessy, John L. (1994). Computer Organization and Design: The Hardware/Software Interface. ISBN 9781558602816.
- Advanced Computer Architecture by Kai Hwang, Chapter 1, Exercise Problem 1.1