- Comments about HANA’s performance normally does not account the much newer and larger hardware footprint versus that HANA replaces.
- It is necessary to isolate the performance of the software from the hardware.
- HANA has a difficulty in addressing the giant footprint it is normally used with.
Introduction to the Performance Impact of Hardware
SAP has made a number of highly aggressive claims about HANA.
Our research into HANA, and has shown that the claims to HANA are on shaky ground.
- We conclude that there is no evidence that HANA can outperform either Oracle 12c or IBM DB2 Blu in either transaction processing or analytics.
- HANA still has not been shown to perform well in transaction processing at any data point — that is in benchmarks or customer observations.
A major problem is a lack of benchmarking data and the fact that vendors benchmark their databases without any outside party to perform the test. Benchmarking scientifically would be expensive, and as the buyers don’t look very deeply into marketing claims, there is a limited market for it. That is SAP customers would not pay an independent entity to do it.
We cover these topics in detail in the article What is the Actual Performance of HANA.
What is HANA?
HANA is two things, and a third thing that is an emergent property of the first two things:
- The Hardware: New hardware, using both high-end RAM and SSDs to push out any spinning disks.
- The Software: A database designed with column-oriented data table store, which is customized for reading access (i.e., for analytics).
- The Hardware Software Interaction: The interaction between the column-oriented data and the memory. This is a well-known feature of the interaction between memory and data stored in as columns which we cover in the article How HANA is Such a Fast Database (For Analytics).
But a major issue, which should be obvious, is that SAP is a software company, and makes none of the hardware that HANA uses. However, SAP is taking credit for performance increases that don’t have anything to do with SAP. And they have nothing to do with the work or innovation of any other database vendor either. However, SAP is the most aggressive in combining the hardware improvement story with the changed software (the database) and allocating all of the credit to SAP, or to the software vendor.
Yes, Adding More Expensive Hardware Increases Performance
Also, this is not to say that any system or database that is placed onto more expensive hardware will not improve in speed.
That is always the case.
And here arises the problem in differentiating just what the hardware “bump” is doing versus the overall HANA “bump.” HANA is a combination of hardware (RAM and SSD replacing spinning disks) with a column-oriented table design.
Our Interaction with HANA’s Performance
Recently we received the following message on HANA performance from someone with first-hand experience with HANA.
“I rather like HANA. We migrated from Oracle to HANA… and I like it very much, although I think it would be so much better on different hardware than what we have.”
There was particular hardware that was purchased that our contact would have preferred to be from another vendor. We won’t get into the hardware as that would be a different article.
Our contact when on to laud HANA’s performance for planning runs. The software that was residing on HANA, in this case, was supply chain planning software. And our contact reported a 30 to 50% improvement in planning runtimes.
Isolating the Performance Benefit of the Hardware from the Performance Benefit of the Software
Upon consideration of this improvement, I began to think of what we know that HANA improves regarding performance. And its primary benefit is read access.
Read access is very intensively used in analytics. However, with a planning system. The load is to the memory and the processor for a planning run.
Therefore the question is why would HANA’s column-oriented design improve the performance of this type of processing?
I asked if it was not likely that the performance was not due to the columns oriented design (which only provide a performance benefit in reading operations) but is instead due to the hardware (the extra RAM and SSD?)
Our contact commented that
“Performance management in the past consisted of optimizing the data flows between CPU, memory, and disk. With in-memory computing, disk I/O has become irrelevant and things that plagued us in the past like disk-layout, RAID configuration, I/O hot-spots, redo-log I/O performance, concurrent/direct I/O and tricky OS settings like IBM’s I/O queue depth have all gone away now.”
But we would point out that these things are true when any system is moved to being entirely in memory.
That is when the more expensive hardware is added.
HANA Efficiency Level with Hardware
There is a lot of discussion by SAP how HANA is so fast. But there is very little information around how well HANA addresses the hardware that it is given. SAP stated that it had the developed the fastest database in the world, and done so on the first version of HANA. But then, HANA has been continually “innovated” since its introduction. HANA is known as one of the most patched databases, and this along with several other factors has to lead to HANA being maintenance heavy, which is accounted for in the Brightwork research A Study into SAP HANA’s TCO.
Information from a number of sources indicates that HANA requires significantly more hardware than do competing databases to return similar performance results. This would indicate that HANA was not designed as well as competing databases regarding how it addresses hardware resources. And these data points that are available to us are recent, so it can be argued that it was because HANA is in its first version. But let us remember, SAP claimed that HANA was the world’s fastest database in its first release. This performance promoted Jon Appleby of Bluefin Solutions (an SAP consultancy) to state that
“Oracle if finished on SAP,”
..as we coved in the article How SAP Has Quietly Changed its Strategy on HANA and Oracle.
This fits into comments that SAP uses regarding HANA’s “innovation.”
SAP has converted the term “innovation” into the frequent updates required to patch problem areas, basically to try to catch up to other databases.
Why Hasso Would Like Customers to Upgrade their Hardware
SAP, and Hasso Plattner, in particular, have made a significant point of emphasis that companies need to upgrade their hardware. In four books on in-memory computing, Hasso has stated that companies don’t understand how much it is beneficial to have all of this performance. However, it should be remembered that all of this advice regarding adding hardware is within the context of adding expensive hardware to SAP in particular.
However, the observations cataloged up to this point demonstrate that HANA is not as capable at using more expensive hardware than competing offerings. Furthermore, the inefficiency with which HANA can do things like utilize processors is quite weak. Therefore, the question arises whether SAP is prompting customers to buy such high hardware specifications to compensate for this issue.
Hasso and SAP Oversimplifying
Furthermore, Hasso and SAP are providing an oversimplified perspective on hardware, speed and decision making. Hasso has stated that decisions in health care, surgeons must be made instantaneously, and HANA will be part of that. This is untrue as is covered in the article How Accurate Was Hasso Plattner and Fortune on HANA?. Even in an ER environment, the orientation is to stabilize the patients. Scheduling operating rooms and the right personnel for specialized procedures takes weeks. There is a whole chain of events that take place that the database will not speed up much. I happen to perform extensive forecasting testing, which is very processing intensive, but I can simulate a forecasting scenario for a large company’s data set using just a well-powered laptop. I think I cost me around $1500 at the time. The software I use makes excellent use of quite inexpensive hardware.
Many examples could be provided. And for those that are less interested in the details per se, the result is that more complexities go into the performance equation that what SAP presents to corporate buyers.
One cannot observe the benefit of HANA without taking into account the more expensive and more modern hardware that HANA brings along with it. SAP proposes that its combination of using column-oriented tables along with more modern and costly hardware leads to a number of different performance benefits. However, adding more expensive equipment to any solution does not require SAP. That is high-speed RAM, and SSD can be purchased without contacting SAP. It can be installed without contacting SAP. And the performance will improve. Furthermore, switching out old hardware for new hardware is one of the fastest ways to improve performance, and not only do you not need SAP, but you also don’t need Deloitte or Accenture, etc..
As a control, one must know the benefits of HANA versus the benefits of adding more expensive hardware to an existing solution, and not employing HANA. Companies that allow SAP to take credit for what is a premium hardware configuration are fooling themselves.
Furthermore, the hardware component is the lowest cost portion of HANA.
- Migrating a current solution to new hardware is the lowest effort of migrations.
- It does not require a reimplementation of software.
- It does not require purchasing a new database license from SAP.
- It is the fastest migration. The data points we have indicated that a HANA implementation takes on average 1.25 years. But a pure hardware upgrade is a small fraction of that time.
Why put off what will be in many cases over 1/2 of the benefits of HANA for 1.5 years?
A substantial portion of the overall benefit of HANA can be obtained by simply installing HANA type hardware with the existing database.
Financial Bias Disclosure
This article and no other article on the Brightwork website is paid for by a software vendor, including Oracle and SAP. Brightwork does offer competitive intelligence work to vendors as part of its business, but no published research or articles are written with any financial consideration. As part of Brightwork’s commitment to publishing independent, unbiased research, the company’s business model is driven by consulting services; no paid media placements are accepted.
I cover Gartner in depth in the following book.
The Gartner Book
How to Figure Out How to Effectively User Gartner
Whether you are a software buyer, a large or small vendor, or are wondering how Gartner can help you make better investment decisions, this book will give you new insights to Gartner’s research. By studying the methodology behind such popular analytical tools like the Magic Quadrant, you will understand how a vendor earned its rating and whether or not the ratings are justified!
Understanding Gartner, It’s History, and It’s Incentives
Starting with the history of Gartner and how it compares to other IT analyst firms, this book gives a realistic assessment of the value of Gartner research to a company and provides ideas about other resources that could complement Gartner’s analysis. You will also have the tools to level the playing field between large, medium and small vendors when using Gartner’s analysis in selecting software.
- Chapter 1: Introduction
- Chapter 2: An Overview of Gartner
- Chapter 3: How Gartner Makes Money
- Chapter 4: Comparing Gartner to Consumer Reports, the RAND Corporation, and Academic Research
- Chapter 5: The Magic Quadrant
- Chapter 6: Other Analytical Products Offered by Gartner
- Chapter 7: Gartner’s Future and Cloud Computing
- Chapter 8: Adjusting the Magic Quadrant
- Chapter 9: Is Gartner Worth the Investment?
- Chapter 10: Conclusion
- Appendix a: How to Use Independent Consultants for Software Selection
- Appendix b: What Does the History of Media Tell Us About This Topic
- Appendix c: Disclosure Statements and Code of Ethics