kill exadata
Finally, now IBM can starve out the leech Oracle Linux and kill exadata for good. FTW
64 publicly visible posts • joined 4 Nov 2012
Madmike
"Why would anyone want a huge P795 server, when they can get a small 8-socket M7 server? Tell me."
Because you you the term faster incorrectly. Your definition of faster is not yielding shorter response times. A lot of people actually has to open the branches in the morning and cannot wait indeterminately for EOD processing to finish. Telcos need to rate and bill transactions before raw data is discarded.
Couple slow processing of SPARC with anemic virtualization capabilities will allow these customers to do a lot more with POWER than SPARC M7 regardless of your definition of faster. And it will require a lot less Oracle licenses.
there is no M7, to hide the fact M7 development is cancelled after current M5/M6 fiasco Oracle renamed T7 to M7. (and suitably dropped T7). More interestingly this will allow to use the same server designs across the line and the M5/M6 monster can be take out the back. Oracle can finally fire the high end old Sun design team that did not produce a single viable server design for 10 years after E25k. One product (M5) in 10 year is not acceptable by any standard.
Look at the core strength, number and pitiful cache size it is clear that it will not be able to hold a candle against Power 8. Compression? Well POWER7+ and POWER8 already has HW assisted compression/decompression.
Unmatched 1024 core scalability? Well IBM already announced the "TrueNorth" 4096 core chip.
Captain Server Pants writes:
"Do you realize the 6 core chips in the 2 chip modules (remember 2x6=12) contain inactive cores? Why would this be the case? Maybe IBM fabs cannot manufacture the single part in high enough yields. Will Oracle follow IBM's lead and introduce 2x16 core (with deactivated cores) SPARC chip modules because it's a better solution? Sorry no, it's the opposite."
If you check the IBM POWER8 S824 Redbook you notice that all 4 IO buses are wired from each socket. So in fact what might look like a way to use broken chips, the 2x6 dual chip socket design increases the IO performance by 100% compared to a 1x12 core designs.
The SAMBA AD implementation used to be "broken" and requiring a Linux hack to increase the number of groups per user, thus making incompatible with UNIX. (Ie Solaris, AIX, NFS etc). Is this still the case? Or can SAMBA 4 actually be used on anything but Linux? Other SMB implementation would not directly map a UNIX group to a Windows group thus avoiding the issue of running Windows 2003 server in native AD mode.