Moonshot vs. Metrics
Some of you may know that last week I was on some college visits. I love this time of info sessions, tours, cafeterias, classrooms, and dorms. I even got to stay in a real dorm one night. Funny, it was not any dorm I had ever been in, not at a college that I had ever been at, and not even a section of a city I had ever been to – but the cooking smells brought me right back to senior year.
Anyway, one thing I’ve noticed with these visits is how important statistics are. At first I was so tired of asking/hearing the same questions on metrics. I mean, isn’t it the feel of the campus that matters? But I found that the really key questions are ones like these: What percent of freshmen live in dorms, what is the student to professor ratio, what is the placement rate 6 months after graduation in the field of study? The answers to these questions which are backed by real data really matter because in the end that’s what the big bucks are paying for.
I’ve been feeling that way this week as I look at some of the latest IT news. I see Moonshot claims, backed by “internal HP engineering.” I see Fujitsu M10 and Oracle faster performance claims that don’t even go that far. If I don’t have any data maybe if I don’t include a footnote nobody will notice.
Meanwhile, IBM this week published a new #1 SAP Sales and Distribution 3-tier benchmark result. 266K users, over 1.4M SAPS, over 29M line items per hour, over 88M dialog steps per hour, on the POWER7+ IBM Power 780 with DB2 10.5.(1) With more metrics available than you probably even want to know about.
I hope HP’s alternative thinking with Moonshot was referring to the United States Apollo program — and not the abortive Soviet moonshot or the defunct beer with caffeine.
(1)IBM Power 780 three-tier SAP SD standard application benchmark on SAP enhancement package 5 for SAP ERP 6.0 achieved 266,000 SAP SD benchmark users. Configuration: 8 processors / 64 cores / 256 threads, POWER7+ 3.72 GHz, 512 GB memory, running AIX 7.1, DB2® 10.5; dialog resp.: 0.84s, line items/hour: 29,433,670, dialog steps/hour: 88,301,000, SAPS: 1,471,680, DB time (dialog/ update): .036s/.061s, DB CPU utilization: 97%, average application server CPU utilization: 88%. Certification #2013010.
Source: http://www.sap.com. Results current as of 4/10/13.
SAP, mySAP and other SAP product and service names mentioned herein as well as their respective
logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all
over the world.
The postings on this site solely reflect the personal views of the author and do not necessarily represent the views, positions, strategies or opinions of IBM or IBM management.