Tool : PerfAnalyzer

-
Tool : PerfAnalyzer
This tool developed internally for analyzing the output of Glance, nmon and GC Logs.

The tool has three tabs:
1.       Glance Analyzer
2.       Nmon Analyzer
3.       GC Analyzer

Glance Analyzer:
This is used to analyze the output of Glance command.
It is sub-divided into two tabs:

1.       Off-line Mode : 

To analyze the saved Glance output

2.       Online Mode :
To analyze the Glance Logs online while the test is running. (Enhancements in Progress)

Inputs required: Glance output file.
Output obtained :
Graph outputs of CPU Utilization, Memory Utilization, Disk Utilization and Swap Utilization.
Also gives Min, Max and Avg values for CPU, Memory and Disk Usage.

Nmon Analyzer:
This is used to analyze the output of nmon command.
Inputs required: nmon output file.
Output obtained :
Graph outputs of CPU Utilization, Memory Utilization, Disk Utilization and Network Utilization.
System summary gives CPU Info, Memory Info and Partition Info.

GC Analyzer:
This is used to analyze the output of GC Logs of Sun java.
Inputs required: GC output file.
Output obtained :
Graph outputs of Used Heap, GC Time, Full GC lines, Used Young Generation, Total Young Generation and Total Heap.

Outputs:
1.       All the Graphs can be copied directly to clipboard or Save Image.
2.       Zoom out/In functionality is available.
3.       Show Point Values functionality is also available.
4.       Change the Scale and Reset back to original scale.


Click on the below Link to access the zip file for the setup.
https://sites.google.com/site/nonfunctionaltestingtools/perf-analyzer

Once the zip file is downloaded. Run the Setup.exe to start the tool.

Post any comments/Suggestions for further enhancements or doubts.

Comments

Post a Comment

Popular posts from this blog

Steps to Analyze AWR Report in Oracle

-
Image
Steps to Analyze AWR Report in Oracle AWR -   Automatic   workload repository is a collection of persistent   system performance   statistics   owned by SYS. It resides in SYSAUX   tablespace . By default snapshot are generated once every 60 min and maintained for 7 days . Each snapshot has a unique ID know as "snap_id". Snapshot detail can be found in " dba_hist_snapshot " view.   If we have Database performance issue and not the Database machine, then AWR Report is the place to look at. AWR is not used for real-time performance monitoring like the v$ tables. It is used for historical analysis of performance. AWR complements, but doesnot replace real-time monitoring. Once AWR Report is generated in Oracle, the next task is to analyze it. By going through the AWR Report we can easily solve issues like slow database, high wait events, slow query and many more issues. Even though the report is lengthy, Analyzing or Reading relevant part of AWR Report can
Read more

Vmstat Output explained

-
vmstat : vmstat is a tool in Unix/Linux which is used to Report virtual memory statistics. It shows how much virtual memory there is, how much is free and paging activity. Most important, you can observe page-ins and page-outs as they happen.   vmstat   reports   information about processes, memory, paging, block IO, traps, and cpu activity.   > vmstat procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu-----   r   b    swpd    free    buff   cache         si    so     bi     bo    in    cs us sy id wa st   0   0   21688 12797396 850716 15372668     0     0      3     35     0     0   1   0 99   0   0   0   0   21688 12789292 850716 15372668     0     0      0   1355   883   744   1   0 99   0   0   1   0   21688 12784648 850716 15372676     0     0      0     15 1934 1292   6   0 93   0   0   2   0   21688 12781356 850716 15372736     0     0      0     16 2222 2094   8   1 92   0   0   0   0   21688 12809992 850716 15376880     0
Read more

Verifications and Error Handling in LoadRunner *Web_reg_find and Web_reg_save_param*

-
Verification's and Error Handling Verification points must be inserted into the scripts to verify the application being tested with the load. Verification function that are used in our application are:  Web_reg_find, web_reg_save_param These verification should be outside towards the end of the transaction. Mandatory verification points: ■          Login – whenever there is a login, verification points must be added to verify that the user logged in correctly. ■          Update Transactions – transactions that update the database must be verified that they are successful. ■          Each page should be verified using Web_reg_find function Using Web _ reg_find for verifications. Example: web_reg_find("Text= Main Package","SaveCount=Verify_Count1",LAST); Verification: if (strcmp(lr_eval_string("{Verify_Count1}"),"0")==0) { lr_end_transaction("AddMainPackage", LR_FAIL);  lr_error_message(&q
Read more