WIXLIB

3.2Sizing Guideline3.2.1Application Server SizingCPU Sizing for Application ServerThe "number of scenarios per hour" is calculated out of the target response time, the average think time, the 8scenario dialog steps and the number of concurrent users.SAP recommends a minimum 800 SAPS hardware capacity for SAP ABAP Server to guarantee good responsetimes. This is sufficient to handle up to 20 concurrent users with a good distribution of UI navigations, i.e. noresonance effects, such as for example all users do a click at the very same moment. These numbers are valid forthe SAP Hybris Marketing applications (please see specific application server sizing when usingthe Campaign Content functionality below) and must to be added to the requirements of all othercomponents running on the same server (e.g. NetWeaver plus additional Addons.).Table 4 - CPU Sizing Application ServerUp to ConcurrentUsersUp to Scenariosper HourABAP Server SAPSwith Small DataVolumeABAP Server SAPS withMedium Data VolumeABAP Server SAPSwith Large 0016002400 100Contact SAPCampaign Automation delivered with release 1508With the Campaign Content functionality it is possible to send Emails/SMS to a group of Contacts that areassigned to Campaigns. The send mechanism is realized using the application server and therefore the load canbe much higher than for other SAP Hybris Marketing applications depending on the number of Contacts of asingle Campaign.We calculate with a standard package size of 100 and 10 work processes in parallel (result: 1000 Emails/SMSsend out in parallel).The following table will show different cases for average sizes:10 KB estimated average size of an SMS50 KB estimated average size of an Email100 KB estimated average size of a bigger Email, e.g. a NewsletterSizing SAP Hybris MarketingFehler! Verwenden Sie die Registerkarte 'Start', um Heading 1 dem Text zuzuweisen, der hierangezeigt werden soll.CUSTOMER 2017 SAP SE. All rights reserved.11

Table 5 - CPU Sizing for Campaign AutomationThroughputABAP Server SAPS foraverage SMS size of 10 KBABAP Server SAPS foraverage Email size of 50 KBABAP Server SAPS foraverage Email size of 100 h8.50025.00080.000Product Recommendation delivered with release 1511In case of SAP Product Recommendation Intelligence it is safe to assume that the complexity of a model does notinfluence the resource requirements of the Application Server.SAP recommends a minimum of 1200 SAPS per Core hardware capacity for the SAP ABAP Server to guaranteereasonable response times.This capacity is sufficient to handle up to 500 concurrent users (or 120.000 recommendations per hour) with agood distribution of those requests over time, i.e. no significant peaks. With higher number of users andrecommendations per hour, apply ratio and calculate the required SAPS. For example with 1000 concurrent users(or 240.000 recommendations per hour), CPU capacity of 2400 SAPS would be sufficient.Offer Recommendation delivered with release 1602In case of SAP Offer Recommendation Intelligence, the complexity of a model depends on the number of steps inthe model and the number of rules per step. The more rules the model comprises, the more resources arerequired. The numbers shown in table 9 are based on a one-step scenario with 5 rules.Memory Sizing for Application ServerThe memory requirements are only for the concurrent users which execute the SAP Hybris Marketing scenarios,and come on top of the memory which is required for initializations such as program buffers, shared memory andso on of ABAP server or required for applications which run on the same system in parallel. The minimum ABAPMemory requirements are addressed in the Installation Guide of ABAP Server.Table 6 - Memory Sizing Application Server12Concurrent UsersABAP Server Memory (MB)204005010001002000 100Contact SAPCUSTOMER 2017 SAP SE. All rights reserved.Sizing SAP Hybris MarketingFehler! Verwenden Sie die Registerkarte 'Start', um Heading 1 dem Text zuzuweisen, der hierangezeigt werden soll.

3.2.2SAP HANA SizingScale-Up vs. Scale-OutSAP HANA is offered in a number of ways - in the form of an on premise appliance, delivered in a number ofdifferent configurations and "sizes" by certified hardware partners or by using the tailored data center integrationmodel, and as part of a cloud-based service. This creates different system design options with respect to scale-upand scale-out variations.To maximize performance and throughput, SAP recommends that you scale-up as far as possible (acquirethe configuration with the highest processor and memory specification for the application workload). Do notuse scale-out today!Dedicated hardware should be preferred over virtualized SAP HANA installations when CPU performance isof high importance.CPU Sizing for SAP HANAAs this document is valid for all SAP Hybris Marketing applications, it will provide average calculations. Ourdifferent applications will have different requirements regarding CPU usage.Segmentation in specific, is a highly parallelized application that will have much more requirements withrespect to CPU than e.g. the Target Group. As for Segmentation, a lot of parameters will influence theworkload on HANA:o Number of modeled data sources (number of Views that are processed with one segmentation profile)o Number of exposed attributeso Modeling approach of the data sources (SAP recommends the usage of graphical CalcViews)o Number of end users working in parallelo Complexity of the segmentation modelo number of segments per modelo depth of segmentation treeo usage of expensive segmentation operations (e.g. Exclude operations, random split groups, "ByReference Object" operations (very expensive))o Necessity to recalculate entire segmentation models (very expensive)o Complexity of the executed SQL queries in generalo Data volume (size of segmentation population)When using Segmentation, SAP recommends a minimum hardware of 54.400 SAPS to guarantee goodperformance for simple models. Depending on the complexity it could be much more.Please use the Excel Template to calculate the CPU consumption when usingSegmentation (worksheet "CPU Sizing when using Segmentation"). Click to open Excel TemplateSizing SAP Hybris MarketingFehler! Verwenden Sie die Registerkarte 'Start', um Heading 1 dem Text zuzuweisen, der hierangezeigt werden soll.CUSTOMER 2017 SAP SE. All rights reserved.13

Table 7 - Assumptions for CPU sizing when using SegmentationParameterSize S54400SAPSSize M68000SAPSSize L136000SAPSSize XL204000SAPSSize XXL272000SAPSNumber of parallel Users1-23-56-1011-19 19Datasources123-56-10 10Attributes per Profile1-1011-2021-4041-80 80Base Population (in millions) 0,50,5-2 2-10 10-30 30Complexity of the segmentation model ( 1 less complexity, 5 very high complexity)12345Number of expensive Operations1234 4Nonetheless it is necessary during the implementation project to check performance regarding to theimplemented segmentation models and the user behavior on how they will work with the system.Before deciding on the final sizing of the productive system, it is recommended to first implement thebusiness scenarios, views and models on a comparable data volume in a test environment and carefullymonitor performance of the entire system!Table 8 - Assumptions for CPU sizing when using Product RecommendationUp to Concurrent UsersHANA SAPS with "onestep recommendation"HANA SAPS with "twosteps recommendation"10 (or up to 2.500 recommendations per hour)1.7001.700100 (or up to 25.000 recommendations per hour)15.30022.1001000 (or up to 250.000 recommendations per hour)73.100107.1002000 (or up to 500.000 recommendations per hour)146.200212.500Table 9 - Assumptions for CPU and memory sizing when using Offer Recommendation14Up to Concurrent UsersHANA SAPS with "onestep recommendation"SAP HANA memory[MB] with "one-steprecommendation"10 (or up to 2.500 recommendations per hour)6.800100CUSTOMER 2017 SAP SE. All rights reserved.Sizing SAP Hybris MarketingFehler! Verwenden Sie die Registerkarte 'Start', um Heading 1 dem Text zuzuweisen, der hierangezeigt werden soll.

Up to Concurrent UsersHANA SAPS with "onestep recommendation"SAP HANA memory[MB] with "one-steprecommendation"100 (or up to 25.000 recommendations per hour)47.6003001000 (or up to 250.000 recommendations per hour)464.1003.000The above numbers are based on a one-step recommendation scenario with 5 rules.For other hybris Marketing applications, SAP recommends a minimum SAP HANA hardware of 26.000 SAPS toguarantee good response times for all features benefitting from parallelization with some excuses.This is sufficient to handle up to 20 concurrent users with a good distribution of UI navigations with any datavolume; they are also sufficient to handle up to 100 concurrent users with small data volume.The SAP HANA CPU requirements are provided for those dialog steps of SAP Hybris Marketing scenarios whichcause a high parallel load on HANA.Table 9 - CPU Sizing SAP HANAUp to ConcurrentUsersHANA SAPS with SmallData VolumeHANA SAPS with MediumData VolumeHANA SAPS with LargeData 6.00050.00085.000 100Contact SAPMemory Sizing for SAP HANAMemory is a fundamental resource of the SAP HANA database! The total amount of memory used by SAP HANAis referred to as used memory. It includes program code and stack, all data and system tables and the memoryrequired to temporary computations.You always have to consider, that the physical memory of a SAP HANA DB will not be completely usable by theapplications. The OS system (10% of available memory) as well as the HANA code stack (50 GB) will blockmemory. Furthermore, only half of the left memory must be blocked by application tables.Please check details in the SAP HANA administration guide:http://help.sap.com/hana/sap hana administration guide en.pdfSizing SAP Hybris MarketingFehler! Verwenden Sie die Registerkarte 'Start', um Heading 1 dem Text zuzuweisen, der hierangezeigt werden soll.CUSTOMER 2017 SAP SE. All rights reserved.15

The following example based on a medium size SAP HANA DB with 512 GB memory will showthe available memory for the application tables:Total physical memory 10% blocked for OSBlocked for CodestackHalf of left memory512 GB- 51 GB- 50 GB- 205 GBCalculated Memory ofthe HANA DB 461 GB 411 GB 206 GB (available forapplication tables)Depending on the application, the memory consumption will be influenced on replicated SAP ERP/SAP CRMdatabase tables or those database tables the SAP Hybris Marketing applications will use internally. A complete listof tables and the expected memory consumption can be found in chapter 6 Appendix.The attached Template will help to calculate expected memory for SAP HANAhybris marketing applications! There're 2 alternatives offered. Memorycalculation based on number of contacts and memory calculation based onabsolute values. In addition, worksheets for product recommendation expertsand detailed sales transaction related sizing are available as well. Please use thespecific worksheets and answer the questions! Click to open Excel TemplateThe following table will list the needed memory for all data in the different SAP Hybris Marketingapplications. A description of the details is available in the calculation Template.For the calculation of the memory needed for the replicated database tables, we offer twodifferent approaches.1. SAP Quick Sizer Tool:We recommend using Quick Sizer for customers that start from scratch - installing a new SAP System.Quick Sizer is a web based tool to calculate initial sizing. It is to attend quickly hardware estimations of SAPsystems. You need to have a valid customer number as well as access to the SAP Marketplace.To use the Quick Sizer tool, please find detailed Instructions here: Link to Quicksizer InstructionsHow to transfer sizing numbers from Quick Sizer?Table 10 - Mapping of Quick Sizer Results to SAP HANA16Result in Quick SizerSizing hybris MarketingCalculation FactorsEstimated database sizeInput for: HANA memoryDB size (traditional DB) / 2 20%Estimated CPU requirements forthe DB serverInput for: HANA CPUDB SAPS * 4Estimated database sizeInput for: HANA Disk SpaceDB size / 2Estimated CPU requirements forthe App serverCan be used 1:1-Estimated memory requirementsfor the App serverCan be used 1:1-CUSTOMER 2017 SAP SE. All rights reserved.Sizing SAP Hybris MarketingFehler! Verwenden Sie die Registerkarte 'Start', um Heading 1 dem Text zuzuweisen, der hierangezeigt werden soll.

Note: For further details, please check SAP note 1793345 "Sizing for SAP Suite on HANA".2. SAP Note 1872170 "SAP HANA memory sizing"We recommend to implement this note for customers that will migrate an already existing ERP/CRM systemto SAP HANA !The note offers a report to estimate the memory space requirement for the all relevant database tables. Theprogram runs on non-HANA systems like ERP or CRM and has to be implemented manually in all relevant SAPsystems. The output of the report will give a summery on how much memory will be needed on the HANA systemfor the current state of the ERP/CRM tables after they got replicated.Please check note 2101146 "CEC - Customer 'Engagement and Commerce Sizing recommendations on SAPHANA" for a list of all relevant SAP ERP-tables as well as a list of relevant SAP CRM-tables. They can be usedas selection criteria for the report!Features of the report: Estimates the maximum memory consumption of the database if migrated to SAP HANA Is independent of the source database provider Considers distribution of tables to row/column store Considers de-clustering / de-pooling Considers differences for secondary indexes Considers compression of legacy database, Unicode conversion because the calculation are based onuncompressed theoretical sizes. The report ignores the size in bytes of the data in the source system Runs on SAP BASIS 620 an above Is suitable for sizing of all Business Suite products such as SAP ERP and SAP CRMNote: The report can be implemented in the customer namespace as a Z-report and will also be available inST-PI 2008 1 *SP09 (where * is 620 and higher) under the name /SDF/HDB SIZING. RTC was 10.03.2014!Considering future Data GrowthYou need to anticipate the year-on-year growth of your current data volume.For example, if you expect a 10% volume growth for the next 3 years, you will have to multiply the calculatedHDB memory by factor 1.33. The data growth for the next 3 years will also be considered in the mentionedtemplate.Sizing SAP Hybris MarketingFehler! Verwenden Sie die Registerkarte 'Start', um Heading 1 dem Text zuzuweisen, der hierangezeigt werden soll.CUSTOMER 2017 SAP SE. All rights reserved.17

4Co-Deployment of SAP Customer RelationManagement (CRM) and SAP HybrisMarketing on the same HANA DBIn case of co-deployment of SAP Hybris Marketing and SAP CRM on same SAP HANA DB, the sizing is acombination of SAP Hybris Marketing sizing and SAP CRM sizing.Usually the concurrent users would work either with SAP CRM functionality or with SAP Hybris Marketingfunctionality, i.e. the same user cannot work on both SAP CRM and SAP Hybris Marketing at the very samemoment. For this reason, to avoid oversizing, the sizing for SAP CRM should be done for the average % ofconcurrent users which execute SAP CRM functions, and the sizing for SAP Hybris Marketing should be done forthe average % of the concurrent users which execute SAP Hybris Marketing functions. Then, for ApplicationServer, add the sizing results from SAP Hybris Marketing and SAP CRM. Same applies for the CPU sizing for SAPHANA, that is, add the sizing results from SAP Hybris Marketing and SAP CRM.Memory Sizing for SAP HANA: since in the co-deployment-scenario, SAP Hybris Marketing will directly access theSAP CRM-data without replication, only the replicated data from SAP ERP and the local SAP Hybris Marketingdata need to be added to the memory sizing from SAP CRM.For more details regarding hardware see epx18CUSTOMER 2017 SAP SE. All rights reserved.Sizing SAP Hybris MarketingFehler! Verwenden Sie die Registerkarte 'Start', um Heading 1 dem Text zuzuweisen, der hierangezeigt werden soll.

5Comments and FeedbackBoth are very welcome! Please, address your questions to OSS component under the appropriate subcomponentof CA-MKT-CEI.Sizing SAP Hybris MarketingFehler! Verwenden Sie die Registerkarte 'Start', um Heading 1 dem Text zuzuweisen, der hierangezeigt werden soll.CUSTOMER 2017 SAP SE. All rights reserved.19

6AppendixMemory sizing for hybris Marketing tablesApplicationDetail of applicat

Figure 1: Architecture of SAP Hybris Marketing User Interface Operational Systems SAP Systems Non-SAP Systems SAP LT Replication Server SAP Data Services / Others Process Integration SAP Solution Technical Operations Manager SAP HANA SAP JAM Internet Mobile SMP Mobile Network/ Internet OData HTML 5 / SAPUI 5 SBOP