Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

ST12 measurements keep changing for same input data (was:Performance check)

Former Member
0 Likes
544

Hello everyone,

i am using Tcode ST12 for runtime analysis of a transaction. But the problem is that everytime i execute the trace, the statistics keep changing for the same input data. (especially d/b times). I guess this must be because the data gets buffered after the first time and the data is fetched from the buffer next time the transaction is run.

Is there a way to avoid this so i can get accurate statistics?

Regards,

Xineohpi.

Edited by: Thomas Zloch on Jun 14, 2011 1:23 PM - subject enhanced by moderator

1 ACCEPTED SOLUTION
Read only

yuri_ziryukin
Product and Topic Expert
Product and Topic Expert
0 Likes
480

No, there is no easy way to avoid it. In general we (at SAP) always analyze the second execution of the transaction to make sure that the buffers are filled. In a well-tuned system the data that are more or less often accessed are staying in the buffer.

And in case the data is displaced from the DB buffer, you have to live with the disk reads.

Hello everyone,

i am using Tcode ST12 for runtime analysis of a transaction. But the problem is that everytime i execute the trace, the statistics keep changing for the same input data. (especially d/b times). I guess this must be because the data gets buffered after the first time and the data is fetched from the buffer next time the transaction is run.

Is there a way to avoid this so i can get accurate statistics?

Regards,

Xineohpi.

Edited by: Thomas Zloch on Jun 14, 2011 1:23 PM - subject enhanced by moderator

2 REPLIES 2
Read only

yuri_ziryukin
Product and Topic Expert
Product and Topic Expert
0 Likes
481

No, there is no easy way to avoid it. In general we (at SAP) always analyze the second execution of the transaction to make sure that the buffers are filled. In a well-tuned system the data that are more or less often accessed are staying in the buffer.

And in case the data is displaced from the DB buffer, you have to live with the disk reads.

Read only

0 Likes
480

thanx!!

take care