ABAP Profiling gives a holistic view of execution with the overview. It also provides Hit List, Call-sequence, Call-timelines, and DB accesses information. Analysing information provided by Profiling helps to understand Performance Bottlenecks.
ABAP Profiling in Eclipse is equivalent to old SE30 or SAT transactions in SAP GUI. SAP dedicated a separate perspective for ABAP Profiling. This Perspective can be opened using Menu > Window > Perspective > Open Perspective > Others > ABAP Profiling
Profiling Setting can be accessed via Menu > Window > Preferences > ABAP Development > Profiling:
A Developer can set preference before doing ABAP Profiling.
Let’s understand ABAP Profiling Step by Step:
Go to ABAP Perspective > Right click on Program > Profile As > ABAP Application (or Use Shortcut Ctrl + Shift + F9)
Go to ABAP Profiling Perspective: Go to ABAP Traces Tab > Refresh Project > Double click performed Trace entry > Analyse Trace with different Profiling tools
Go to Hit List tab > Select Trace event > Double click > Stack can be reviewed in Properties view > Drill down possible for further information
Go to Call sequence tab > Select Trace event > Double click > Stack can be reviewed in Properties view
Go to Call timeline tab > Select Required Timeline> Double click > Stack can be reviewed in Properties view
Go to Database Accesses tab > Select DB hit entry > Double click
HANA is made for performance. It is a good programming practice to Profile every custom development and remove performance bottlenecks. Profiling becomes more important when ABAP logic is made for complex business logic and fine-tuning of code can result in a better turn around time.