- intel® demand based switching
- wide dynamic execution
- intel dynamic wide execution
- intel® dynamic wide execution
- what is intel demand based switching
- power saving time
- go to power save
- most efficient core 2
- intel’s demand based switching
- xeon woodcrest 5160
- xeon woodcrest processor
- intel parallel processing
- xeon 5160 review
Partners
The Games selection
violent :
Interactive Buddy
Unwind on your interactive buddy: Do anything you want to him, it will earn you money, and you can buy other stuff to torture him with.
|
crazy :
PC Breakdown
What is worst than a Fatal Error occuring during a game you did not save? Unleash your rage at your PC in this game. Blow it to pieces, it feels so...
|
Sponsored links

Don't pay attention to the Core processor logo: We took this screenshot with an older version of CPU-Z (1.33.1), which did not identify the Xeon 5160 Woodcrest properly. However, it does show the clock speed reduction for Demand Based Switching: The multiplier goes from x9.0 to x6.0, causing the 3.0 GHz clock speed to drop to 2.0 GHz.
Wide Dynamic Execution

Wide Dynamic Execution summarizes the improvements that Intel made to execution width (four parallel processes rather than three) and to the efficiency of micro ops processing.
A greater execution width of four (partially even five) is maintained throughout the whole execution path, which represents an internal bandwidth increase. In other words the processor can fetch, dispatch, execute and return four instructions simultaneously.
In addition to that, the Core 2 architecture supports the techniques that the Pentium M applies to reduce the total number of micro-ops: Micro Ops are broken down x86 instructions that the processor understands. Two of these can be fused into another micro op in order to save time (and energy). According to Intel, roughly every 10th instruction can be merged with another one using Micro Ops Fusion.
The idea of fusing micro ops has also been applied to the instruction level (instruction level parallelism) by allowing for two independent instructions (e.g. a compare and a jump) to be merged for decoding and execution. This feature, which is called Macro Ops Fusion, can even be carried into the ALUs: These allow for overall single cycle instruction execution, whether that is a macro op that consists of two instructions or generic instructions.
Both fusion mechanisms together can help to increase the efficiency of each core considerably. Think about it as some sort of instruction or micro ops level.
