Skip to Content
Technical Articles
Author's profile photo Rajarajeswari Kaliyaperumal

How to read the performance trace :HANAAdmin tool

Performance trace Vs HANAAdmin tool

If you have tried to collect a performance trace , and have ended up in a file *.tpt which is not human readable, note that performance trace can be decoded by using a tool called HANAAdmin.

Below information is only specific to how to invoke it and other possible functionality at a basic level. We used this tool to check if all our nodes of production environment has god network using test function at a graphic level.

How to access this tool?

Location:

Use:

This tool is mostly used to analyze performance trace and also network issues with respect to intra node communication.

To Open it:

Set the DISPLAY variable in you HANA server. Post that execute the below to open the HDBAdmin tool in the above specified location.

./HDBAdmin.sh

Screen:

 

In above click on TEST button to get the output to and from master node to slave node and slave to master node.

To Analyze Performance trace:

Capture the performance trace in HANA studio trace and when it is turned off we will get the output file as perftrace.tpt .

For more information you can refer the below links:

https://blogs.sap.com/2014/01/14/how-to-use-hdbadmin-to-analyze-performance-traces-in-sap-hana/..

 

Thanks for reading!
Follow for more such posts by clicking here => https://people.sap.com/rajarajeswari_kaliyaperumal

Like and leave a comment or suggestion if any!

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Lars Breddemann
      Lars Breddemann

      Hmm... this post seems written hastily and presents an unsupported tool with a link to a blog post that is already more than six years old.

      Instead of screenshots where I don't see what it is you want to show I'd be much more interested in reading about how you used this tool to solve a performance issue.

      What conclusions did you draw from the data you found with the tool?

      How did you go about analysing a performance problem?

      Simply getting the tool to display something isn't really all that much to write about.