sebb-2-2
this make perfect sense.
I have searched all test steps in tree view in all possible ways
but there seems not to be any value of id.
I find id e.g. as
type hidden; name id; value //
in the test steps.
any hint where I can search and find the value.
the browser must be getting the
Thank you very much! It worked like you said, I just didn't saw the file in
the jmeter bin.
I have another question though: I need the file to be overwritten at each
test run...is it posibile to do it like this?
I can't have a new file each time because I have to read from that file
later in the
THX @ALL
the problem is solved.
All I had to do was to
add s* HTTP URL Re-writing Modifier and set its Session Argument to id*
no regEx needed anymore,...works great now
--
View this message in context:
On 21 September 2011 11:59, freesky h...@windowslive.com wrote:
Hi, I want to create a variable 'id', the default value is 0. If there is a
specific request, such as submit data request, then the variable 'id' will
plus 1. Then the 'id' will plus 1 in the next request, so now the value of
id
Hello,
For the reputation of JMeter it would be nice from you
kootsoophttp://jmeter.512774.n5.nabble.com/template/NamlServlet.jtp?macro=user_nodesuser=256137to
update this with last news :
http://jmeter.512774.n5.nabble.com/JMeter-GUI-vs-JMeter-Server-td4822852.html
As you updated this one:
I will update, but after I have gone through many different settings, I
still believe JMeter has a problem in server mode. It's better with
batching (or holding), but still not as good as running the applicaiton
standalone (in either GUI or non-GUI form).
Thanks for the feedback!
Ciao,
Peter
Hello,
You must know that SamplerSender is pluggable :
- mode can also be the class name of an implementation of
org.apache.jmeter.samplers.SampleSender
We for example developped an inhouse SampleSender that makes it as and even
more efficient than GUI.
Regards
Philippe Mouawad
On Wed,
JMeter doesn't have a 'problem' as such, it just takes longer to write to a
file that is on a different machine as compared to doing the same thing for
a local file. Any computer program will experience the same issue. And ot's
logical that if this takes longer then the processing of a request
Thanks for the feedback!
Oliver Lloyd wrote:
Do you also get different response times?
Yes, I get different response times because the system under test is taking
longer to respond when under higher load.
Oliver Lloyd wrote:
And are you pacing these requests using timers or are they
Oliver Lloyd wrote:
JMeter doesn't have a 'problem' as such, it just takes longer to write to
a file that is on a different machine as compared to doing the same thing
for a local file. Any computer program will experience the same issue. And
ot's logical that if this takes longer then the
On 21 September 2011 14:08, kootsoop koots...@gmail.com wrote:
Thanks for the feedback!
Oliver Lloyd wrote:
Do you also get different response times?
Yes, I get different response times because the system under test is taking
longer to respond when under higher load.
Oliver Lloyd
I'll try to manage with the file, I am thinking of deleting it after the test
run..
Is there posbile to force the threads to run in a specific order?
I have 3 threads, admin, user and the admin again: the first admin creates a
user, in the second thread the user performs some actions and the 3rd
Couldn't you have 1 Thread Group?
Like this:
Thread group
+Admin create
+User
+Admin delete
Then you could change the 'Number of Threads' for that particular thread
group
ZK
--
View this message in context:
On 21 September 2011 16:38, ZK stevesenio...@gmail.com wrote:
Couldn't you have 1 Thread Group?
Like this:
Thread group
+Admin create
+User
+Admin delete
Then you could change the 'Number of Threads' for that particular thread
group
Or, use the new setUp and tearDown Thread Groups in
Ah, that's different. It's true (or at least I have experienced the same
thing) that if you have JMeter running in Distributed (master_slave) mode
then you can potentially hit an IO bottleneck where JMeter cannot write
multiple results streams to one file quick enough. The workaround - as you
have
sebb-2-2 wrote:
The JMeter server sends back the samples to the client after the
sample has finished, but before the next sample can occur, so any
delays in returning the sample to the client will slow down the rate
at which the thread can issue requests to the server. This is
equivalent
Oliver Lloyd wrote:
Ah, that's different. It's true (or at least I have experienced the same
thing) that if you have JMeter running in Distributed (master_slave) mode
then you can potentially hit an IO bottleneck where JMeter cannot write
multiple results streams to one file quick enough.
17 matches
Mail list logo
