On 11/29/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> In order to load testing the web application, I would like Jmeter
> to Increase the number of threads of a thread group, each 30 minutes.
Further to the other responses in this thread -- including the Include
Controller, which looks very nifty and I hadn't encountered yet -- I solved
this problem like so.
First, specify the number of threads in your Thread Group as a command line
parameter, e.g. ${__P(threads,0)}.
Second, add a "simple data writer" to your plan and tell it to output to
results.jtl.
Thirdly, set your sampler name to contain the number of threads, e.g.
"HTTP-${__P(threads,0)} threads"
Fourthly, write a batch command to invoke JMeter multiple times with varying
number of threads, pausing briefly between each run to let the server
recover:
del results.jtl
%JAVA_HOME%\bin\java.exe %JM_LAUNCH% %JVM_ARGS% %ARGS% -jar %JMJAR% -n -t
%TEST% -Jthreads=1
@ping 127.0.0.1 -n 5 -w 1000 > nul
%JAVA_HOME%\bin\java.exe %JM_LAUNCH% %JVM_ARGS% %ARGS% -jar %JMJAR% -n -t
%TEST% -Jthreads=2
@ping 127.0.0.1 -n 5 -w 1000 > nul
%JAVA_HOME%\bin\java.exe %JM_LAUNCH% %JVM_ARGS% %ARGS% -jar %JMJAR% -n -t
%TEST% -Jthreads=3
@ping 127.0.0.1 -n 5 -w 1000 > nul
copy results.jtl results_1.jtl
%JAVA_HOME%, %JM_LANCH%, %JVM_ARGS%, %ARGS%, %JMJAR% and %TEST% are the
location of java.exe, the various classes needed for JMeter, the
command-line arguments, the JVM options, and the location of the JMX file.
Then, the four successive JMeters run with various numbers of threads and
all append to the same output file. When the run is done, you can load that
output file into JMeter's Aggregate Report and you will get multiple lines
in the report, saying "HTTP 1 thread", "HTTP 2 threads", and so on.
I found this the neatest way I could think of.
