Hi ,
I had put multiple IF controllers in Script like currently I had two IF
controllers ---
First IF controller --> Condition - "${__machineIP()}" == "172.16.60.44"
Second IF Controller --> Condition - "${__machineIP()}" == "172.16.60.188"
In the above two IF conditions I have parameters like no of threads , no of
input records to process with respect to the specific slave machine.
So when I ran the test with two slave machines with the mentioned IP addresses
above. Each slave machine should have picked up their parameters based on the
ip address condition but what was happening was that instead both the machines
picked up values/parameters from the last IF condition.
So what I could find was the IF condition were not validating.
Am I doing any error or some other way of handling the particular slave machine.
Regards,
SOumya
-----Original Message-----
From: Deepak Shetty [mailto:[email protected]]
Sent: Wednesday, January 17, 2018 12:20 AM
To: JMeter Users List <[email protected]>
Cc: [email protected]
Subject: Re: JMeter Distributed Load test Query
Hi
a. Please use separate threads for separate issues - it is difficult to follow
b. Please check JMeter logs for errors when things do not work c. Please
provide more useful descriptions of what you did , what did or did not work
etc. e.g. I put multiple IF controllers , it did not work is not useful.
In your case
a. First get a basic script to work with master - slave (hence eliminate any
connectivity , setup errors) -
https://jmeter.apache.org/usermanual/jmeter_distributed_testing_step_by_step.pdf
b. Then get the threads suggestion working if you want to vary load - However
consider why you want different slaves to generate different loads c. Then add
more complex steps into your script and resolve each issue as it arises.
As before use a separate topic for each distinct issue that you may run into
regards
deepak
On Mon, Jan 15, 2018 at 10:10 PM, Nayak, Soumya R. <[email protected]>
wrote:
> Also ,
>
> I am not getting the response data from slave machines to the master.
> I had put mode= Standard in user.properties in all slave machines but
> still not returning.
>
> Regards,
> soumya
>
> -----Original Message-----
> From: Nayak, Soumya R.
> Sent: Tuesday, January 16, 2018 11:19 AM
> To: 'JMeter Users List' <[email protected]>;
> [email protected]
> Subject: RE: JMeter Distributed Load test Query
>
> Hi,
>
> I tried with the below configurations putting IF condition for each
> slave machine, in that if condition I have declared User defined
> variables, But what is happening its picking up the last IF condition
> parameters irrespective of machine IP and machine name.
> So please let me know how to handle the condition ??
>
> Regards,
> Soumya
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Monday, January 8, 2018 4:44 PM
> To: [email protected]
> Subject: Re: JMeter Distributed Load test Query
>
> 1. You can choose how many threads will be started for this or that
> slave machine by setting the number of threads in Thread Group <
> http://jmeter.apache.org/usermanual/component_reference.html#Thread_Gr
> oup>
> (s) using __P() function
> <https://jmeter.apache.org/usermanual/functions.html#__P> like
>
>
> > ${__P(threads)}
>
>
>
> Once done you can define the desired number of threads on each slave
> in /user.properties/ file , i.e. on 1st slave:
>
>
> > threads=15
>
> on 2nd slave
>
>
> > threads=25
>
> 2. You can switch code execution lines depending on slave machine
> using If Controller <http://jmeter.apache.org/usermanual/component_
> reference.html#If_Controller>
> and __machineName()
> <https://jmeter.apache.org/usermanual/functions.html#__machineName> or
> __machineIP()
> <https://jmeter.apache.org/usermanual/functions.html#__machineIP>
> functions combination like:
>
>
> > - If Controller, condition: "${__machineIP()}" == "10.10.10.11"
> > - requests for slave with IP address 10.10.10.11
>
> 3. You can set *mode=Standard* property for all slaves, this way they
> will send full results to master as soon as they will be generated.
> This way you will be able to "normally" analyse the .JTL results file in the
> realtime.
> See Using a different sample sender
> <http://jmeter.apache.org/usermanual/remote-test.html#sendermode> for
> more
> details.
>
> Reference material:
>
> 1. Remote Testing
> <http://jmeter.apache.org/usermanual/remote-test.html>
> 2. How to Perform Distributed Testing in JMeter <
> https://www.blazemeter.com/blog/how-to-perform-
> distributed-testing-in-jmeter>
> 3. JMeter Distributed Testing Step-by-step
> <https://jmeter.apache.org/
> usermanual/jmeter_distributed_testing_step_by_step.pdf>
>
>
>
>
> --
> Sent from: http://www.jmeter-archive.org/JMeter-User-f512775.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
> ************************************************************
> ******************************
> This message may contain confidential or proprietary information
> intended only for the use of the
> addressee(s) named above or may contain information that is legally
> privileged. If you are not the intended addressee, or the person
> responsible for delivering it to the intended addressee, you are
> hereby notified that reading, disseminating, distributing or copying
> this message is strictly prohibited. If you have received this message
> by mistake, please immediately notify us by replying to the message
> and delete the original message and any copies immediately thereafter.
>
> If you received this email as a commercial message and would like to
> opt out of future commercial messages, please let us know and we will
> remove you from our distribution list.
>
> Thank you.~
> ************************************************************
> ******************************
> FAFLD
>
>
> ---------------------------------------------------------------------
> 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]
