1. Skip to Menu
  2. Skip to Content
  3. Skip to Footer>

Expert Sessions!

Understanding STAD - Part 1

Friday, 10 August 2012 11:53

Written by Prakash Palani

Print E-mail

Introduction

STAD is the transaction used to understand the performance of a given transaction/program in SAP, it helps you to understand every step of the transaction in detail.  When you are asked to perform an analysis of a particular transaction, this is the first and foremost transaction must be used to decide whether performance of the transaction/program in question has issue due to expensive db access, exhausted system hardware, RFC communications, poor buffer configuration, etc.,  This will you to move forward with necessary subsequent steps that are needed to identify the bottleneck/root cause.

In this article, I have described the architecture and few of the important settings that is needed for STAD to give optimum results, watch out this space for subsequent articles focusing on every details that you would be interested to know about STAD.

The records those you view in STAD transaction are recorded in shared buffer (in memory as indicated in below picture) before it gets written to the file located at the operating system level and the same can be controlled using the parameters given below.

 

 

Below are few important profile parameters related to STAD functionality

  • stat/bufsize  - Size of buffer [bytes] for records before transfer to dataset
  • stat/as_bufsize - Buffer size [bytes] for appl. records bef. transf. to dataset
  • stat/file - Dataset for transfer of stat. records
  • stat/as_file - Dataset for transfer of appl. stat. records
  • stat/max_files - Max. no. of stat files to be kept
  • stat/as_max_files - Max. no. of appl. stat files to be kept
  • stat/level -  Activate/Deactivate the data collection
Understanding STAD - Part 1