Jmeter : Adding Perfmon Metrics to Jmeter

-
To add Perform Plugins into Jmeter we need to copy "JMeterPlugins-Standard.jar" under lib/ext directory. This brings some more features of Perfmon as below:


More details about the plugin can be found @ http://jmeter-plugins.org/wiki/PerfMonAgent/

Using this we can capture the Server side metrics like CPU, Memory,Disk I/O, Network I/O ..etc.

To collect all the Metrics using PerfMon we need to add On TestPlan -> Add -> Listener -> "jp@gc - PerfMon Metrics Collector".

Specific the Host/IP, Port, Metric to Collect and filename to store the results as shown below:

We can also add other Listeners also.
Some important ones to add are as below:



Comments

  1. jagadeeshSeptember 22, 2015 at 10:49 PM

    I want to measure CPU and Memory usage of my server during load test using Jmeter. For this i added "jp@gc - PerfMon Metrics Collector" listener with my scripts in jmeter GUI and configured jmeter perfmon plugin in my server. I got the graph in jmeter GUI correctly without any errors.

    Now i want to run my same jmeter script via Maven and jenkins for continuous Integration (Without opening jmeter GUI).

    My question is, How can i see the CPU and memory usage of the server in graph without opening jmeter GUI after test execution completes.

    Is it possible to generate CPU and Memory graph once my test script completes execution in Jenkins? If so please guide me how to do this.
    And also please let me know if any plugin needs to be added in my pom.xml file inorder to get CPU and Memory usage graph.

    ReplyDelete
  2. RajJune 4, 2019 at 6:17 PM

    Hi, I want to do the same @Jagadeesh instead of Jenkins I'm using bamboo. Did you find out if any dependency are added to pom.xml file inorder to get Perfmon Metrics Monitoring working.

    ReplyDelete

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