2008 Feb 02 5:33 PM
Hi
what is the ideal graph for performance analysis of a report in SE30.
It shows green color for ABAP and SYSTEM and red color for DATABASE.
It also shows 90% red and only 5 % green.
What does this indicate about my report?
What should be the ideal graph?
Thank you.
2008 Feb 02 9:32 PM
Check this Blogs for The ABAP Runtime Trace (SE30) - Quick and Easy
/people/siegfried.boes/blog/2007/11/13/the-abap-runtime-trace-se30--quick-and-easy
Runtime Analysis checks program execution time in microseconds. When you go to se30.if you give desired program name in performance file. It will take you to below screen. You can get how much past is your program.
In SM30(Runtime Analysis), Abap, database and System are the three rows which indicate the performance of our program.
These indicate the load on them by the program, which is determined by the length of the bar beside them.
For better performance, abap should be around 90% +, database should be 10% - and system can be around 20% - 45%.
This means that if the load on the database is less , performance is more. For abap the % should be more indicating the fine tuning of the coding so that DB load can be reduced to improve the performance.
Also check this thread.
/thread/404067 [original link is broken]
Hi
what is the ideal graph for performance analysis of a report in SE30.
It shows green color for ABAP and SYSTEM and red color for DATABASE.
It also shows 90% red and only 5 % green.
What does this indicate about my report?
What should be the ideal graph?
Thank you.
2008 Feb 02 7:18 PM
Hi SRK
check this link:
/people/siegfried.boes/blog/2007/11/13/the-abap-runtime-trace-se30--quick-and-easy
your answer is at 2. Trace Results Overview in the weblog.
System and database may be very small, or even zero, but should not be too large. For system, 10% is already too large, and for the database, 50% is quite large. The argument why database should be considerably larger than ABAP is the following: after the data has been read from the database, some kind of processing should occur on the records, so that a ratio of 20 to 40% for database is desirable. Programs with very special tasks can of course have very special percentage distributions.
2008 Feb 02 9:32 PM
Check this Blogs for The ABAP Runtime Trace (SE30) - Quick and Easy
/people/siegfried.boes/blog/2007/11/13/the-abap-runtime-trace-se30--quick-and-easy
Runtime Analysis checks program execution time in microseconds. When you go to se30.if you give desired program name in performance file. It will take you to below screen. You can get how much past is your program.
In SM30(Runtime Analysis), Abap, database and System are the three rows which indicate the performance of our program.
These indicate the load on them by the program, which is determined by the length of the bar beside them.
For better performance, abap should be around 90% +, database should be 10% - and system can be around 20% - 45%.
This means that if the load on the database is less , performance is more. For abap the % should be more indicating the fine tuning of the coding so that DB load can be reduced to improve the performance.
Also check this thread.
/thread/404067 [original link is broken]
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |