Symptom
Initial Sizing observations for SAP Suite on HANA
(SAP enhancement package 7 for SAP ERP 6.0, version for SAP HANA, SAP
enhancement package 3 for SAP CRM 7.0, version for SAP HANA, SAP
enhancement package 3 for SAP SCM 7.0, version for SAP HANA, SAP
enhancement package 3 for SAP Supplier Relationship Management 7.0,
version for SAP HANA).
Please refer to SAP Note 1872170 (Suite on HANA memory sizing), if you want to do a HANA memory sizing of an already productive system. This SAP Note implements a report to estimate the memory space requirement for the database tables of Suite on HANA systems. The program runs on non-HANA systems.
Please refer to SAP Note 1872170 (Suite on HANA memory sizing), if you want to do a HANA memory sizing of an already productive system. This SAP Note implements a report to estimate the memory space requirement for the database tables of Suite on HANA systems. The program runs on non-HANA systems.
Other Terms
Sizing, resource requirements, performance, update, hardware, enhancement packages, Suite on HANA
Reason and Prerequisites
Customers plan hardware expenditures prior to moving to HANA
Please note that SAP enhancement package 6 for SAP ERP 6.0, SAP enhancement package 2 for SAP CRM 7.0, SAP enhancement package 2 for SAP SCM 7.0, and SAP enhancement package 3 for SAP SRM 7.0 are prerequisites for this move. (You can use note 1723135 and related notes to plan the hardware requirements for the update to SAP ERP EHP6).
Please note that SAP enhancement package 6 for SAP ERP 6.0, SAP enhancement package 2 for SAP CRM 7.0, SAP enhancement package 2 for SAP SCM 7.0, and SAP enhancement package 3 for SAP SRM 7.0 are prerequisites for this move. (You can use note 1723135 and related notes to plan the hardware requirements for the update to SAP ERP EHP6).
Solution
Initial sizing observations are based on lab measurements, load tests
and measurements performed in customer test systems. This information
may change, if additional measurement results are available. This
information is only valid, if the system usage is not changed after the
move; intense additional reporting and OLAP processing is not taken into
account.
Initial Sizing
For initial (greenfield) sizings, you should use the HANA Quick Sizer at http://service.sap.com/hanaqs (please note that no other calculation/formulas need to be applied when using the HANA Quick Sizer).
Productive Sizing
For productive (brownfield) sizings, there are two different approaches possible. The first approach is very straight forward and can be applied as a first rough assessment, whereas the second approach (report) is much more detailed and therefore also more reliable. The recommendation from SAP is to apply the report.
You should not forget to consider your future data growth into your planning. SAP doesn't expect changes in memory requirements for applications using liveCache. If you are using SAP HANA Enterprise Search, you should add 20% memory resources on top.
If you want to estimate the HANA CPU requirements, then you should identify the CPU consumption of the database. You can for example look at the CPU consumption of the database process(es) using SAP's monitoring tools. To fully support the parallel processing capabilities of HANA for optimal response times for analytical applications SAP prefers a factor of 3 more CPU power for HANA than for disk based databases without parallelization of single statements. This also considers the load for running OLTP and Reporting simultaneously and includes a moderate use of SAP HANA Enterprise Search. Extensive usage of SAP HANA Enterprise Search capabilities might require additional CPU resources.
To give a prediction regarding the required HANA disk space (or: total net disk space), you have to take into consideration the net data size on disk (anyDB) and the disk space required for Delta Merges. During a Delta Merge, the affected tables are temporarily duplicated on disk for a short period of time. The disk space for merges is calculated by taking the sum of the two biggest tables and include this value into the calculation. On top, you should add 25GB for the space required by the statistics server, HANA metadata, etc. The final calculation looks as follows:
HANA disk space (Total Net Disk Space) = (Net Data Size anyDB + Disk Space for Merges) / 4 (compression) * 1,2 (20% safety buffer) + 25GB
If you are using SAP HANA Enterprise Search, you should add 20% disk resources on top.
More information regarding SAP HANA Storage Requirements can be found in this document (http://scn.sap.com/docs/DOC-62595 ).
Please note that SAP doesn't expect any changes concerning CPU, memory and network requirements for the ABAP application server. This means that the existing hardware and network infrastructure can still be used.
Please note that both further experiences from existing, productive HANA customers as well as optimizations in HANA may lead to changes regarding the sizing procedure for Suite on HANA.
Initial Sizing
For initial (greenfield) sizings, you should use the HANA Quick Sizer at http://service.sap.com/hanaqs (please note that no other calculation/formulas need to be applied when using the HANA Quick Sizer).
Productive Sizing
For productive (brownfield) sizings, there are two different approaches possible. The first approach is very straight forward and can be applied as a first rough assessment, whereas the second approach (report) is much more detailed and therefore also more reliable. The recommendation from SAP is to apply the report.
- Quick and easy approach
You should not forget to consider your future data growth into your planning. SAP doesn't expect changes in memory requirements for applications using liveCache. If you are using SAP HANA Enterprise Search, you should add 20% memory resources on top.
If you want to estimate the HANA CPU requirements, then you should identify the CPU consumption of the database. You can for example look at the CPU consumption of the database process(es) using SAP's monitoring tools. To fully support the parallel processing capabilities of HANA for optimal response times for analytical applications SAP prefers a factor of 3 more CPU power for HANA than for disk based databases without parallelization of single statements. This also considers the load for running OLTP and Reporting simultaneously and includes a moderate use of SAP HANA Enterprise Search. Extensive usage of SAP HANA Enterprise Search capabilities might require additional CPU resources.
To give a prediction regarding the required HANA disk space (or: total net disk space), you have to take into consideration the net data size on disk (anyDB) and the disk space required for Delta Merges. During a Delta Merge, the affected tables are temporarily duplicated on disk for a short period of time. The disk space for merges is calculated by taking the sum of the two biggest tables and include this value into the calculation. On top, you should add 25GB for the space required by the statistics server, HANA metadata, etc. The final calculation looks as follows:
HANA disk space (Total Net Disk Space) = (Net Data Size anyDB + Disk Space for Merges) / 4 (compression) * 1,2 (20% safety buffer) + 25GB
If you are using SAP HANA Enterprise Search, you should add 20% disk resources on top.
More information regarding SAP HANA Storage Requirements can be found in this document (http://scn.sap.com/docs/DOC-62595 ).
Please note that SAP doesn't expect any changes concerning CPU, memory and network requirements for the ABAP application server. This means that the existing hardware and network infrastructure can still be used.
- Sizing report for a more accurate sizing
Please note that both further experiences from existing, productive HANA customers as well as optimizations in HANA may lead to changes regarding the sizing procedure for Suite on HANA.
Header Data
| Released On | 27.04.2015 09:26:15 | ||
| Release Status | Released for Customer | ||
| Component | BC-EHP-INS Please use BC-UPG-TLS* | ||
| Other Components |
| ||
| Priority | Recommendations / Additional Info | ||
| Category | Performance |
Thanks for this amazing content. It is very useful and knowledgeable for us. Appreciable.
ReplyDeleteWe are also provide these services like: Alcohol and Drug Evaluation Diversion California
Substance Abuse Assessment California
SAP for DOT Evaluation
Substance Abuse Assessment
DUI Class
DUI Evaluacion
Thanks for considering us.
An Alcohol and Drug Evaluation Atlanta Decatur Marietta-Georgia allows a professional to determine whether an issue regarding the use of alcohol or drugs exists and therefore needs to be addressed with further attention or intervention. The alcohol and drug evaluation documents basic current and historic usage of substances along with the extent of effects. It is always better if an individual can get the help they need for substance abuse when first recognized, to avoid getting into any troublesome situations but this is not always the case. A certified addiction expert will guide you through all the necessary steps. This process typically involves a pre-screening, an evaluation, follow up meetings, and treatment referrals. The screening itself helps determine if there is a problem, while the evaluation assesses the depth of the problem.
ReplyDeleteThank you for sharing this useful knowledge on Sap Return To Work. This is one of the most brilliant pieces of writing I've ever come across. I read all of your blogs, but my favourite is this one. It's exactly what I was looking for, and I hope you'll continue to provide excellent content in the future.
ReplyDelete