ViktorBKK said:
walsufnir said:
ViktorBKK said: Let's take things from the start. Technically, CPU architecture refers to the instruction set of a CPU. Examples are, x86, ARM, MIPS etc. Both the 360 and Wii U use PowerPC architecture. There is no "exotic" architecture involved, like PS3's mixed-core solution. Now obviously, some people want to believe that there is immense untapped power in this system. The cold hard truth is that Nintendo's system is based on 40-45nm silicon and runs at 75 Watts during full blown game-play. 80 dollar video cards from the same process node run at 100-130 watts. If you understand the principles of semi-conductor size and power consumption, then you know what I'm talking about. There is barely any hardware inside that console. |
"Let's take things from the start. Technically, CPU architecture refers to the instruction set of a CPU. Examples are, x86, ARM, MIPS etc."
Right, this is called "ISA" (Instruction Set Architecture).
"Both the 360 and Wii U use PowerPC architecture."
Right, also PS3 (excluding the spes).
BUT: ISA means nothing. The way the instructions are implemented on the CPU, how the pipelining works, branch-prediction, cache-sizes... All this differs even with the same ISA.
Example: Pentium 4 and Pentium M. Both were "x86" but still Pentium M was faster at lower clock rates. Why? Read above.
"There is barely any hardware inside that console."
This disqualifies yourself for all future technical discussions.
|
1) The PS3 also has RISC co-processors, so it is not just PowerPC.
2) I am sure you agree that porting code to a system that shares the same instruction set, requires less work than porting it to one that doesn't.
3) You may not like my wording, but you know its true. Less than 100 watts for an entire system that runs on 40/45nm hardware is literally nothing these days.
|
1) As I said if you had read my post.
2) No I don't because if you want performant code you also have to keep in mind how the cache is structured and how the whole system is designed. This will change your code in a massive way if you want it to be fitting to the system. Cache-aware coding is time-consuming but profilers will help you, of course. Of course, if you are lazy and don't use the system properly you get ports as we see them now.
Just look at the slides from Guerilla Games what they said about the memory layout of PS4 - this has nothing to do with the cpu but with understanding how the memory works on this system.
3) But only power consumption is not telling the whole truth. PS4 and Xbox One won't use 300 Watts either, so they are also "nothing"? Is a smartphone which is able to run emulators for systems like n64 hardware-wise nothing?
I think there is a lot of brainpower in the WiiU which we all don't see by now. It is definitely not capable like PS4/Xbox One but it should definitely ahead of ps360 to me.