SAP SIZING / SAP LIFE SIZING
SAP Application Performance Standard (SAPS)
The market is growing. Are you prepared? We possess unique possibilities to determine and predict the needed sizing of your hardware as well as structural solutions of the next 5 years.
CSE Support - SAP LIFE SIZING for successful cost cutting
SAP Life Sizing is a service, which, with the help of various parameters and measuring methods, is able to determine the necessary investment for hardware needed in the future and infrastructural solutions within a timeframe of up to 5 years with relatively high precision.
These measuring procedures are also at the same time able to unveil critical performance issues or general infrastructural problems (such as detection of programming errors or long running processes).
In the era of cloud solutions or virtualizations this implies that we can individually adjust the benchmark values (SAPS) with the usual so-called T-Shirt-Sizing.
By utilizing intelligent programs, we are able to show you software and hardware deficits. We identify the lot sizes of your SAP IT, which are to be redefined, so that you can focus on your core business and do not suffer any competitive disadvantages due to poor performance.
Sizing (SAP Sizing) is a general term in IT management correlated with the planning of IT resources for IT service delivery. Sizing relates to the determination of hardware requirements for this service in regards to network bandwidth, RAM, storage space, CPU Power in SAPS and the input-/output-capacity of the system. These resources are dependent on the nature of the service itself, in our case that would mean the minimum requirements of the SAP product and the load in dependence of the business requirements of the company, so for example how many users will be able to access these services at peak hours.
It is only after the sizing (SAP sizings) has been determined that an
IT landscape architecture will be set up. If through sizing it has been
detected that you have to save, read and process a lot of data, you
would be advised to install a storage attached network in order to be
able to quickly transfer the data. Or if you should notice that one of
the server systems in the server room is incapable of fulfilling the
determined hardware requirements, you would be either advised to acquire
a new system or to toggle multiple servers into a cluster. Of course,
there are exceptions to the rule: certain landscape decisions are
decided before the sizing (SAP sizing) – for example if you want to have
a high-availability system, servers that will act as a substitute when
another server fails, etc. This is taken into account in sizing (SAP
Sizing), in which, for example, the replacement servers must also meet
the hardware requirements.
SAP has introduced a new unit – SAP Application Performance Standard (SAPS), which is to be used for the evaluation of IT systems on which SAP-products are to be run. 100 SAPS is the (hardware) power of an IT system which is needed in order to fully process orders in business processes in the SAP module Sales and Distribution (SD) 2000 – in other words, it is to create the order and the delivery confirmation, to show the order, edit the delivery and create an invoice, etc. This performance, which a SAP system delivers, is simulated in this benchmark and tested. The same performance is needed for for example when SAP users want to perform 6,000 dialogue steps (screen switching on frontend), 2,000 postings per hours in the SD module or 2,400 SAP transactions. This unit is, so to speak, an indicator on how efficiently a SAP product on this system will run. The number of SAPS for a system can be detected via a benchmark, which is provided by SAP.
Furthermore, there are also other metrics that can be used to
evaluate IT systems. As is also known from business administration,
these measures are called key performance indicators (KPI). In the field
of IT architecture, KPIs such as throughput or server response time for
single processes are generally known. SAP likes to measure systems with
the KPI Single Computing Unit Performance (SCU performance), which was
introduced by SAP itself. The SCU speaks for the processing power of a
single computer unit in a system. Such a unit can be: a single thread in
a multi-threaded CPU, a core in a multi-core processor or any other
individual unit that makes up a CPU. Until the year ~ 2006, a single SCU
of a processor became more and more powerful - we remember: back then
the clock speeds of the CPUs continued to increase. For around 5-8
years, however, the possibilities of increasing the clock rate of the
individual SCUs have been stagnating, which is why process manufacturers
specialize in being able to operate several SCUs parallelly - which is
why multithreading and multicore processors are being manufactured
increasingly.
Depending on the SAP product used, it scales very well with an increasing number of SCUs or not so well. The less well the product scales, the more important the performance of a single SCU becomes. There are processes that can’t be handled well by multi-core architecture, rather it depends on the performance of an SCU. Otherwise, you could simply add up the SAPS that a single SCU creates (current systems create over 2,000 SAPS per SCU) and see whether you meet the total SAPS number that is required for the system. Unfortunately, it's not that simple.
Depending on the SCU performance, the SAP products are divided into following classes:
A - the SAP product benefits from good SCU performance
AA - the SAP product benefits from very good SCU performance
AAA - the SAP product benefits from excellent SCU performance.
further information:
http://service.sap.com/sizing
Contact us – we’d love to assist you!
CSE IT-Consulting & Software Engineering GmbH
Im Paradies 46
34253 Lohfelden
E-Mail: vertrieb@cse-gmbh.com
Tel: +49 561 70838867
 |