Talk:Cycles per instruction

Computing Stub‑class

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
Stub	This article has been rated as Stub-class on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.
	This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the `\|auto=` parameter.

How to inform this is article is a stub ??? --Hgfernan 18:45, 1 September 2005 (UTC)[reply]

merge

I suggest merging Instructions Per Cycle into Cycles Per Instruction. Both talk about exactly the same thing -- after a bunch of clock cycles, how many instructions were executed?

Or does this googlefight result mean we should go the other way, merging everything into Instructions Per Cycle? --68.0.124.33 (talk) 18:28, 26 March 2008 (UTC)[reply]

They are entirely different things. CPI is for measuring the average amount of cycles it takes to complete one instruction, while IPC is used to measure the number of instructions that can be executed in one cycle. Rilak (talk) 05:01, 28 March 2008 (UTC)[reply]

Oppose, while historically C/I used to be reciprocal of I/C, since 1990s this is no longer true. Nowadays, C/I is all about increasing pipeline length to increase frequency, and I/C is all about instruction-level parallelism, multithreading, etc. They both tend to grow as technology develops. --Kubanczyk (talk) 09:19, 5 April 2008 (UTC)[reply]