Agent specific reports?

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Agent specific reports?

Puneet Monga
I had a look at the detail CSV generated after the test execution. I am trying to generate more graphs out of the csv. However, I don't see any agent specific information in it. Is there a way to identify the agent that reported the statistics?

One use case could be to see the graphs for a given agent.
Reply | Threaded
Open this post in threaded view
|

RE: Agent specific reports?

junoyoon
Administrator

All agents do the best to run the script and controller aggregate the results from agents.. That's how nGrinder and The Grinder work. 

 

Statistic per agent is meaningful to you?  

Could you tell me the reason?

 

If you want to selectively run the agents, you can turn off uninterested agents by clicking unapproval button in the agent management page.

 

-----Original Message-----
From: "Puneet Monga [via ngrinder]"<[hidden email]>
To: "junoyoon"<[hidden email]>;
Cc:
Sent: 2013-03-05 (화) 10:04:33
Subject: Agent specific reports?

I had a look at the detail CSV generated after the test execution. I am trying to generate more graphs out of the csv. However, I don't see any agent specific information in it. Is there a way to identify the agent that reported the statistics?

One use case could be to see the graphs for a given agent.


If you reply to this email, your message will be added to the discussion below:
http://ngrinder.642.n7.nabble.com/Agent-specific-reports-tp403.html
To start a new topic under ngrinder-user-en, email [hidden email]
To unsubscribe from ngrinder-user-en, click here.
NAML
Reply | Threaded
Open this post in threaded view
|

RE: Agent specific reports?

Puneet Monga
One use case is to have couple of agents. One deployed in U.K and other in U.S. Application that is under load test is deployed in Korea. Load test results may differ because of the location. If it is possible to view the results/statistics based on the agent, then it may help in analysis of the load test results from the geography point of view or network specific delays.
Reply | Threaded
Open this post in threaded view
|

RE: Agent specific reports?

junoyoon
Administrator

We're handling this issue with nGrinder cluster mode.

Each member of cluster handles agents in one region.

We run the test multiple times in each region and compare the regionally different result 

and find out what's the issue in the specific region.

 

Refer to following document.

 

http://www.cubrid.org/wiki_ngrinder/entry/cluster-architecture 

 

 

-----Original Message-----
From: "Puneet Monga [via ngrinder]"<[hidden email]>
To: "junoyoon"<[hidden email]>;
Cc:
Sent: 2013-03-05 (화) 13:05:19
Subject: RE: Agent specific reports?

One use case is to have couple of agents. One deployed in U.K and other in U.S. Application that is under load test is deployed in Korea. Load test results may differ because of the location. If it is possible to view the results/statistics based on the agent, then it may help in analysis of the load test results from the geography point of view or network specific delays.


If you reply to this email, your message will be added to the discussion below:
http://ngrinder.642.n7.nabble.com/Agent-specific-reports-tp403p407.html
To start a new topic under ngrinder-user-en, email [hidden email]
To unsubscribe from ngrinder-user-en, click here.
NAML
Reply | Threaded
Open this post in threaded view
|

RE: Agent specific reports?

junoyoon
Administrator
In reply to this post by Puneet Monga
Or... if you refer the agent process log in the ngrinder report panel, you can see the logs passed from agents.

It contains the statistics of "only one process" per agents at the end of the log like followings.

It might help you.
================================================================================

             Tests        Errors       Mean Test    Test Time    TPS          Mean         Response     Response     Mean time to Mean time to Mean time to
                                       Time (ms)    Standard                  response     bytes per    errors       resolve host establish    first byte  
                                                    Deviation                 length       second                                 connection                
                                                    (ms)                                                                                                    

Test 1       916          0            107.05       110.50       3.83         0.00         0.00         0            0.13         0.43         106.69        "Test1"

Totals       916          0            107.05       110.50       3.83         0.00         0.00         0            0.13         0.43         106.69      

  Tests resulting in error only contribute to the Errors column.          
  Statistics for individual tests can be found in the data file, including
  (possibly incomplete) statistics for erroneous tests. Composite tests  
  are marked with () and not included in the totals.