We've had the opportunity to work with HANA both as a Startup porting our application to HANA as well as with our SAP customers running HANA in production scale BW or ECC environments. In the R&D environment we have limited hardware capacity and thus resources, especially memory is always a constraint, so we learnt ways to monitor, and automate to optimize our performance and use of the system. In the customers' production environment, we have seen original architecture plans double in nodes and/or memory before they even got to performance testing phase.
Part of the reason for the above discrepancy is that for an in-memory environment, storage on disk and in memory are two completely different numbers and various factors (such as types of tables/data, access patterns, frequency, and application dynamics, just to name a few) will impact how much memory is consumed during run time as well as over time. It is equally important to plan sufficiently as well as operate intelligently in order to maximize the availability and performance of HANA.
If you're looking for examples of tools to help automate the monitoring and housekeeping of tasks such as above, check out our IT-Conductor solution.
We're proud to announce that the platform is now also offered through the AWS Marketplace as the only SaaS-based SAP monitoring and automation solution.
Do you have some additional useful tips to share?