[prev in list] [next in list] [prev in thread] [next in thread] 

List:       grinder-development
Subject:    Re: [Grinder-development] Automating a Distributed Grinder Test
From:       Philip Aston <philipa () mail ! com>
Date:       2011-07-10 7:29:26
Message-ID: 4E1954D6.3070608 () mail ! com
[Download RAW message or body]

I'm not sure I have any answers here, just comments on the approach 
taken by the standard console.

The console statistics recording is based only on the time period set by 
the user. Worker processes may be started or stopped independently of 
the recording, but are typically started before the recording and 
stopped afterwords.

When used with the console, the worker processes are usually configured 
to run "for ever" (until they are manually stopped from the console). 
Agent processes should definitely run for ever - they should not need 
restarting unless you need to change fundamental things like classpaths 
etc. The "grinder.duration" property is most useful in simple, single 
agent scenarios where the console is not being used.

A conceivably useful feature (not implemented) would be for the console 
to have an option to automatically stop the workers when the statistics 
recording finishes. This needs to be optional because there are valid 
testing techniques which keep the load on (the worker processes running) 
while taking a series of statistics recordings.

- Phil

On 20/06/11 15:35, Kelvin Ward wrote:
> Hi
>
> I've been working on automating the running of a grinder test with 
> distributed load injectors (agents) programming with jython.
>
> I used ssh to automatically distribute the files to the injectors. I 
> also successfully used the experimental console API to connect to the 
> console, start and stop the worker processes managed by the 
> distributed agents.
>
> My problem at this point is deciding when I should tell the 
> workers/agents to stop running. If the test is meant to have an 
> infinite amount of runs I can just wait until the grinder.duration 
> property limit is reached. Can anyone suggest a block of code that 
> would allow my jython process to listen to the status of the remote 
> worker processes (what the process number is, state - started | 
> running | finished )? I think the console must have some code like 
> this, but I'm rather lost browsing the grinder source code knowing 
> what objects to instantiate and connect together.
>
> Cheers.
>
>


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Grinder-development mailing list
Grinder-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/grinder-development
[prev in list] [next in list] [prev in thread] [next in thread]