topic Re: Consumed SAPS in DevOps and System Administration Forum

Consumed SAPS

former_member702356 — Mon, 14 Sep 2020 20:11:14 GMT

According to SAP, 100 SAPS is defined as 2,000 fully business processed order line items per hour. In technical terms, this throughput is achieved by processing 6,000 dialog steps (screen changes), 2,000 postings per hour in the SD Benchmark, or 2,400 SAP transactions.

From above definition it sound like 6,000 dialog steps/hour equates to 100 SAP. Thus, 1 SAP = 60 dialog steps/hour. Similarly 2,000 fully business processed order line items per hour equates to 100 SAPS. Thus 1 SAP = 20 fully business processed order line items per hour.
This checks out when you look at any benchmark published by any vendor. The benchmark shows Dialog Steps per hour and Fully Processed Line Item per hour. If you divide Dialog Steps/hour with 60 or Fully processed Line item per hour with 20 and it comes to the published SAPS for the setup.

Early Watch Report also provides Max Dialog Steps per Hour. If I divide this with 60 then wouldn't this give me SAPS being consumed on this system? Of course, have to make sure that Max CPU utilization is low to make sure that there is no CPU bottleneck and there is no paging going on.

Re: Consumed SAPS

dasistdochscheisse — Tue, 15 Sep 2020 06:31:24 GMT

I doubt that you can calculate it this way. Afair SD transactions utilize the CPU more then other transactions. For eample, calling SM50 would be one dialog step but it uses nearly nothing. Other transaction need a lot more data and through that more processing power. EWA does not differentiate the utilization of RAM/CPU of different transactions.

Re: Consumed SAPS

former_member644293 — Tue, 15 Sep 2020 06:34:07 GMT

Max Dialog Steps per Hour gives the steps for a particular period of EWA report and it does not mean that this is the limit for hardware nor this can be taken as SAPS to benchmark.

May be check for the peak for the longer period to get the benchmark.

Regards,