Hi Adrian and Eric,
maybe I'm missing some point, but to me the total duration of the test is
rarely important nor predictable.
If you need it as a baseline, you can use an aggregate result listener, run
some test (maybe with one or two users) and then
you can multiply the number of samples (eventually divided the number of loops
executed) by the average execution time.
So you can easily have the net time you need to do a single loop.
This is net of time spent on timers.
But when you start having 1000 users, you have a lot of parallelizaton, but
obviously not the 100% (that would be ideal).
Also in some case, you have to add the ramp-up time.
In my experience, we usually end up measuring the behaviour of few key transactions (e.g. submit the order, or login/logout), under
different situations and loads,
The relationship between average, mean, 90nth % and max return an idea of the
way things go.
Note that these transactions are also the longest.
A static page or an image takes few msec to download, and most of the time
spent is due to the network latency,
which is not something we can easily optimize.
This is my point of view, feel free to share your thoughts.
best regards
Sergio
Il 20/03/2012 17:55, Erik Pragt ha scritto:
Hi Adrian,
Thanks for the super quick reply. I'm a bit surprised by your first
remark though, so maybe I'm having a wrong approach here.
I'm currently developing an application which might have some
performance issues. Our current target is around 1000 simultaneous
logged in users, and around 10 concurrent 'clicks'. My current
approach was to sort of simulate that behavior in JMeter, check how
long it takes for the simulated users to finish their flows, make some
adjustments, test again, and check if my simulated users are faster
than before. Based on this, I need the total execution time, but
apparently this is not the usual approach, else it would certainly
have been in there somewhere.
Could you recommend what would be a better way to test my scenario?
I'm not a performance rock star at all, so I'm very curious what would
be an effective way in improving the application and using JMeter as
the load generator in that.
Kind regards,
Erik Pragt
On Tue, Mar 20, 2012 at 5:44 PM, Adrian Speteanu<[email protected]> wrote:
Hi Erik,
A very interesting idea.
You can find start / stop time in jmeter's log. When running from a console
in non-gui mode, you also get some more statistics then in GUI (how long
the test ran). You can also schedule a test to run for a certain amount of
time, or starting / stopping at certain hours (so you don't have to worry
about this stuff).
If you are interested in response times, however, the sum of all requests,
then things get more complicated.
Adrian
On Tue, Mar 20, 2012 at 6:21 PM, Erik Pragt<[email protected]> wrote:
Hi all,
I've created a test plan to put some load on a flow of pages we have.
I'm quite new to JMeter, and I have a small question on how to get the
information I'm looking for. I've got a working test plan, I can see
the samples, the throughput, etc, but I can't find anywhere what the
time was to execute this testplan, or a single loop of this testplan
when I execute it multiple times.
Can someone give me a small heads up how I can record and view this time?
Kind regards,
Erik Pragt
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Ing. Sergio Boso
In caso di erronea ricezione da parte di persona diversa, siete pregati di eliminare il messaggio e i suoi allegati in modo
definitivo dai vostri archivi e di volercelo comunicare immediatamente restituendoci il messaggio via e-mail al seguente
[email protected] <mailto:[email protected]>
L’interessato può, inoltre, esercitare tutti i diritti di accesso sui propri dati previsti dal decreto 196/2003, tra i quali i
diritti di rettifica, aggiornamento e cancellazione, inviando un messaggio all’indirizzo:[email protected]
<mailto:[email protected]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
