[QUOTE="Mordred19"][QUOTE="subrosian"] No, clock-speed and number of cores are not genuine indicators of performance. The Core 2 Duo, running at a slower clock speed, with fewer cores, still outperforms the Xenon by a wide margin. There are a large number of factors that determine processor power.
Short answer - architecture
Medium answer- work per-clock cycle
Long answer - no
subrosian
what does architecture entail, and how is that a difference between the Xenon and the Core 2 Duo?
Does architecture include cache? What are standard memory caches on PCs versus the Xenon's cache?
Architecture includes a lot of things, cache (which is just a fancy way of saying "super fast memory attached to the processor"), internal bandwidth (how many lanes is the "highway" connecting the different parts of the processor? how fast are those lanes? how do they handle traffic?), external bandwidth, et cetera.
Architecture also includes how basic commands "work". If you think of a task for a processor to perform, say "add 2 + 2 and output the result", it has to break those down into binary operations. In the real world, that means breaking that down something as simple as "add 2 plus 2" into lots of little operations like "take the value "2" and store it in cache", "move the value in the cache into the ALU (the CPU's calculator)".
So, how powerful a processor is depends also on how well it performs those tasks.
On top of that (not to make this more complicated), a processor receives requests to perform many tasks at once, often with one task depending on the result of another task (think of a math problem like "2 + (2 * 4)" you need to calculate that 2 * 4 = 8 before you can add it to the value of 2). So, a processor's "architecture" needs to have an efficient scheduler - basically the processor's air traffic controller. Not only does it need to make sure the tasks happen in the right order, it needs to *anticipate* upcoming tasks, and make sure as much of the processor's "power" is in use at once.
-
I know it's a bit complicated, but basically "clock speed" is simply something used to "sync" the tasks, actually the same way we use clocks. If you told your friend to meet you at Starbucks at 7pm to work on some homework with you, you have a far better chance of actually meeting up to work than if you say "I'll meet up to work on the homework at Starbucks whenever". The "clock" in a CPU works the same way - if your friend were to wear a watch that "ticks" twice as often as yours, does that give him more time in the day? Of course not.
Cores are a different issue. What we do with "cores" is create distinct, seperate processors, group them together, and use some form of scheduling (either software or hardware) to divide work amongst them. It actually isn't too much different than the traditional CPU in that we think in the same way - efficient scheduling, and efficiency matter. The only thing that's changed is that there is now a software-side to it - the people building the games have to think about how to use those seperate cores efficiently.
However, the "power" of the total processor still depends on how good each core is, so, a Core 2 Duo, which has two very-efficient, very-powerful cores in the CPU is stronger than the Xenon, which has three older, less-powerful, less-efficient cores.
Well, you definetly cleared things up for me. Thanks. :D
Log in to comment