12/17/2008
13
© 2008 Hewlett-Packard GmbH (SAPCC Germany)
The information contained herein is subject to change without notice
•
The following block diagram is user based. A user based sizing can be done by HP Sizer
or SAP
Quicksizer. Quantity based (requires expert know-how) sizing can only be done by SAP
Quicksizer
or SAP CC. The description refers to concurrent users; that means SAP users effective
working on the system and
not
the number of SAP licenses or logged-on users. This is a good
approximation; and this is verified by our experience; is a ratio of one concurrent user for two SAP
licenses (50%).
•
As every SAP system has to be customized to the individual customer requirements, it creates
variable load. To provide for adequate system reserves, we estimate a minimum of 10 SAPS (SAP
Application Performance Standard) for each concurrent user that is equivalent to a medium SAP SD
(Sales & Distribution) user.
•
The performance of the servers (CPUs) has increased during the last years; you have to put
adequate memory into the servers. A rational starting base for production systems is to calculate 4-
until up to 8 GB per Core. Be aware that you only get the feasible SAPS values of the respective
servers when using sufficient memory (for instance 32 GB for 2-
socket-
& 64 GB for 4-
socket
servers).
•
The size of the database is based on our experience and best practices. On smaller databases we
have to prioritize performance instead of capacity.
SAP ECC & CRM Sizing Considerations
Directory
Applications
Technology
Solutions
