How HANA Takes 30 to 40 Times the Memory of Other Databases

Executive Summary

  • HANA takes extremely enormous levels of memory compared to competing databases.
  • HANA has continual timeout issues that are in part due to HANA’s problem managing memory.

Introduction to HANA’s Problems with Managing Memory

SAP’s database competitors like Oracle, IBM, and Microsoft, have internal groups that focus on memory optimization. Memory optimization (in databases) is how tables are moved into and out of memory. However, SAP tries to push more tables into memory that are necessary (but not as many tables as they state that they do, that is not “all the tables”). However, SAP does not have the optimization capabilities of the other database vendors.

High Memory Consumption with HANA

HANA’s high memory consumption is explained in their SAP HANA Troubleshooting and Performance Analysis Guide where they state the following.

“You observe that the amount of memory allocated by the SAP HANA database is higher than expected. The following alerts indicate issues with high memory usage.”

And..

“Issues with overall system performance can be caused by a number of very different root causes. Typical reasons for a slow system are resource shortages of CPU, memory, disk I/O and, for distributed systems, network performance.”

This is odd for SAP to observe shortages of resources. This is because HANA has the highest hardware specification of any other competing database. Also, the comparison is not even close. This is pointed out again by SAP regarding memory.

“If a detailed analysis of the SAP HANA memory consumption didn’t reveal any root cause of increased memory requirements it is possible that the available memory is not sufficient for the current utilization of the SAP HANA database.”

Conclusion

The same question arises, with so much memory usually part of the initial sizing, why is undersized HANA memory such an issue?

Brightwork Disclosure

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.

HANA & S/4HANA Question Box

  • Have Questions About S/4HANA & HANA?

    It is difficult for most companies to make improvements in S/4HANA and HANA without outside advice. And it is close to impossible to get honest S/4HANA and HANA advice from large consulting companies. We offer remote unbiased multi-dimension S/4HANA and HANA support.

    Just fill out the form below and we'll be in touch.

The Risk Estimation Book

 

Software RiskRethinking Enterprise Software Risk: Controlling the Main Risk Factors on IT Projects

Better Managing Software Risk

The software implementation is risky business and success is not a certainty. But you can reduce risk with the strategies in this book. Undertaking software selection and implementation without approximating the project’s risk is a poor way to make decisions about either projects or software. But that’s the way many companies do business, even though 50 percent of IT implementations are deemed failures.

Finding What Works and What Doesn’t

In this book, you will review the strategies commonly used by most companies for mitigating software project risk–and learn why these plans don’t work–and then acquire practical and realistic strategies that will help you to maximize success on your software implementation.

Chapters

Chapter 1: Introduction
Chapter 2: Enterprise Software Risk Management
Chapter 3: The Basics of Enterprise Software Risk Management
Chapter 4: Understanding the Enterprise Software Market
Chapter 5: Software Sell-ability versus Implementability
Chapter 6: Selecting the Right IT Consultant
Chapter 7: How to Use the Reports of Analysts Like Gartner
Chapter 8: How to Interpret Vendor-Provided Information to Reduce Project Risk
Chapter 9: Evaluating Implementation Preparedness
Chapter 10: Using TCO for Decision Making
Chapter 11: The Software Decisions’ Risk Component Model