"....eans T2 is faster. But not to you IBM FUDers I suspect."
Now wipe your eyes and have a nice cup of tea and a piece of cake, my boy. Sorry you haven't been attending one of my classes here where I work, in my "Designing Solutions on UNIX", I use a 2-3 hours just explaning what the different vendors use of terms and what they mean with regards to threads,CPU's, Processors etc etc. U've been mixing it up since day one.
As for T3 crushing anything. Well it'll be the tables of Solaris sysadmins, when they have to have 500 inch monitors to be able to see all the threads. T3 is just more threads, 16 threads on 8 cores on one chip. That is 128 threads per CHIP.
A POWER 750 does 2410483 specJBB2005 on 4 sockets and 32 cores.
A Ora T5440 does 841380 specJBB2005 on 4 sockets and 32 cores.
So as for crushing.. what is that x2 the throughput ? Or just x 1.5 ?
So you are basically saying that a T3 based T5440 with 4 sockets and 32 cores will do around 3.5M-5M sepcJBB2005 ? So doubling the number of threads will give you a factor of 4-6 in throughput. You should really cut down on the psychedelic drugs.
"Ramblings about IBM is Microsoft and SUN is apple"
Listen. IBM isn't really copying anything from Niagara. Your whole premisses for your ramblins arewrong. Niagara and POWER7 are like night and day. The idea behind Niagara is many simpler cores with many threads for great efficiency. It's a good concept for the types of workloads it was designed for.
POWER7 is totally different it's 8 really really fat cores, each core has 12 execution units.
Sure IBM uses 4 threads on a POWER7 core and Niagara uses 8 (soon to be 16) but just cause they are
using >1 thread doesn't make it the same. Niagara uses statically round robin scheduled fine grained
multithreading. It's terrific when used for many light independent threads, and very efficient, for
that type of workload. But it sacrifices single threaded performance, and you need to have a lot of
threads that want to execute for it to be efficient.
POWER7 uses a SMT, with quite a few bells and whistles for example the OS can fold together
threads(virtual processors) , hence you actually don't have to have 4 threads executing at the same time, you can also have one that takes up the whole processor, the processor adapts to the workload that runs on it. So at 1-8 threads per chip it's a single threaded beast, and then as the number of threads increases up to 32 it becomes more and more of a throughput CHIP. Going from perhaps 800 units of work in throughput at 8 threads to 1440 units of work at 32 threads.
For the Niagara T2+ CHIP running the same workload it might do something like 85 units of work at 8 threads and 425 at 64 threads. With the T3 this might change to 100 units of work at 8 threads to something like 900 at 64 threads.
This little calculation is based on the 97 SPECint_rate2006 for one T2+ chip and 330 Specintrate2006 for one POWER7 chip, and from various papers that suggest that going from 1 thread per core to 8 threads give you something like a factor of 5 in throughput. And not a factor of 8.
This is a huge difference, and if you cannot see that then well... your loss.
"And all this false IBM marketing: one Mainframe can consolidate 1500 x86 servers - if they all idle. "
Problem is with servers is that most of them are idle... With a click of a mouse I have access to utilization data of thousands of thousands of servers... And guess what stand alone Wintel servers, do have lousy utilization. Often between 1-5%. Now how you then choose to consolidate and where is your own business. The premisses for their calculations are IMHO valid. I've have personally run consolidation projects where we consolidated hundreds of Wintel servers running Oracle DB's onto a single POWER server. HUGE savings.. HUGE saving.. And the fun part is when you talk with Wintel sysadmins, when they talk about utilization it's peak utilization... so 'My server is 50% utilized' normally mean that at peak times it uses 50%.