Newbie, need help in designing test plan in jmeter for concurrent API calls












0















We have a Rest Server talking to 128 devices. I need to send 10 API calls to each device and to all 128 devices at the same time. So the Rest server needs to handle 1280 at a time every 15 mins. I am using jmeter and can create 1280 threads to make each API call unique to go to all 128 devices manually. Is there a better way to do it other than manually typing and populating the threads?



Basically, I am looking to automate the process of creating the threads through a script and load the jmx to GUI, or better/faster way using GUI itself










share|improve this question

























  • Basically, I am looking to automate the process of creating the threads through a script and load the jmx to GUI, or better/faster way using GUI itself.

    – Swamy Bale
    Nov 28 '18 at 23:45
















0















We have a Rest Server talking to 128 devices. I need to send 10 API calls to each device and to all 128 devices at the same time. So the Rest server needs to handle 1280 at a time every 15 mins. I am using jmeter and can create 1280 threads to make each API call unique to go to all 128 devices manually. Is there a better way to do it other than manually typing and populating the threads?



Basically, I am looking to automate the process of creating the threads through a script and load the jmx to GUI, or better/faster way using GUI itself










share|improve this question

























  • Basically, I am looking to automate the process of creating the threads through a script and load the jmx to GUI, or better/faster way using GUI itself.

    – Swamy Bale
    Nov 28 '18 at 23:45














0












0








0








We have a Rest Server talking to 128 devices. I need to send 10 API calls to each device and to all 128 devices at the same time. So the Rest server needs to handle 1280 at a time every 15 mins. I am using jmeter and can create 1280 threads to make each API call unique to go to all 128 devices manually. Is there a better way to do it other than manually typing and populating the threads?



Basically, I am looking to automate the process of creating the threads through a script and load the jmx to GUI, or better/faster way using GUI itself










share|improve this question
















We have a Rest Server talking to 128 devices. I need to send 10 API calls to each device and to all 128 devices at the same time. So the Rest server needs to handle 1280 at a time every 15 mins. I am using jmeter and can create 1280 threads to make each API call unique to go to all 128 devices manually. Is there a better way to do it other than manually typing and populating the threads?



Basically, I am looking to automate the process of creating the threads through a script and load the jmx to GUI, or better/faster way using GUI itself







jmeter






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 29 '18 at 1:51









Kingsley

3,47731428




3,47731428










asked Nov 28 '18 at 23:43









Swamy BaleSwamy Bale

1




1













  • Basically, I am looking to automate the process of creating the threads through a script and load the jmx to GUI, or better/faster way using GUI itself.

    – Swamy Bale
    Nov 28 '18 at 23:45



















  • Basically, I am looking to automate the process of creating the threads through a script and load the jmx to GUI, or better/faster way using GUI itself.

    – Swamy Bale
    Nov 28 '18 at 23:45

















Basically, I am looking to automate the process of creating the threads through a script and load the jmx to GUI, or better/faster way using GUI itself.

– Swamy Bale
Nov 28 '18 at 23:45





Basically, I am looking to automate the process of creating the threads through a script and load the jmx to GUI, or better/faster way using GUI itself.

– Swamy Bale
Nov 28 '18 at 23:45












1 Answer
1






active

oldest

votes


















0














Normally the following test elements are being used:




  1. Recording: using HTTP(S) Test Script Recorder for automation of the HTTP Request samplers creation. The idea is that you execute your test scenario on mobile device and JMeter captures the traffic and creates the relevant requests.


  2. Parameterization: if your want to use different data for different virtual users you can configure JMeter to read it from external sources (files, databases, etc.), the most commonly used test element is CSV Data Set Config


  3. Synchronizing Timer: this guy ensures that samplers it its scope are executed at exactly the same moment. Normally JMeter executes requests as fast as it can, but it doesn't guarantee that requests will happen at exactly the same moment unless you use the Syncrhonizing Timer.






share|improve this answer
























  • Thanks. I tried and it is only reading one device and fire one request per thread, basically doing consecutive rather than concurrent. It is a challenge and jmeter don't have the capacity to read from a file and make all the requests concurrent. For the time being I will create 1000+ threads manually with each API request and fire them as concurrent.

    – Swamy Bale
    Nov 30 '18 at 19:35














Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53529780%2fnewbie-need-help-in-designing-test-plan-in-jmeter-for-concurrent-api-calls%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Normally the following test elements are being used:




  1. Recording: using HTTP(S) Test Script Recorder for automation of the HTTP Request samplers creation. The idea is that you execute your test scenario on mobile device and JMeter captures the traffic and creates the relevant requests.


  2. Parameterization: if your want to use different data for different virtual users you can configure JMeter to read it from external sources (files, databases, etc.), the most commonly used test element is CSV Data Set Config


  3. Synchronizing Timer: this guy ensures that samplers it its scope are executed at exactly the same moment. Normally JMeter executes requests as fast as it can, but it doesn't guarantee that requests will happen at exactly the same moment unless you use the Syncrhonizing Timer.






share|improve this answer
























  • Thanks. I tried and it is only reading one device and fire one request per thread, basically doing consecutive rather than concurrent. It is a challenge and jmeter don't have the capacity to read from a file and make all the requests concurrent. For the time being I will create 1000+ threads manually with each API request and fire them as concurrent.

    – Swamy Bale
    Nov 30 '18 at 19:35


















0














Normally the following test elements are being used:




  1. Recording: using HTTP(S) Test Script Recorder for automation of the HTTP Request samplers creation. The idea is that you execute your test scenario on mobile device and JMeter captures the traffic and creates the relevant requests.


  2. Parameterization: if your want to use different data for different virtual users you can configure JMeter to read it from external sources (files, databases, etc.), the most commonly used test element is CSV Data Set Config


  3. Synchronizing Timer: this guy ensures that samplers it its scope are executed at exactly the same moment. Normally JMeter executes requests as fast as it can, but it doesn't guarantee that requests will happen at exactly the same moment unless you use the Syncrhonizing Timer.






share|improve this answer
























  • Thanks. I tried and it is only reading one device and fire one request per thread, basically doing consecutive rather than concurrent. It is a challenge and jmeter don't have the capacity to read from a file and make all the requests concurrent. For the time being I will create 1000+ threads manually with each API request and fire them as concurrent.

    – Swamy Bale
    Nov 30 '18 at 19:35
















0












0








0







Normally the following test elements are being used:




  1. Recording: using HTTP(S) Test Script Recorder for automation of the HTTP Request samplers creation. The idea is that you execute your test scenario on mobile device and JMeter captures the traffic and creates the relevant requests.


  2. Parameterization: if your want to use different data for different virtual users you can configure JMeter to read it from external sources (files, databases, etc.), the most commonly used test element is CSV Data Set Config


  3. Synchronizing Timer: this guy ensures that samplers it its scope are executed at exactly the same moment. Normally JMeter executes requests as fast as it can, but it doesn't guarantee that requests will happen at exactly the same moment unless you use the Syncrhonizing Timer.






share|improve this answer













Normally the following test elements are being used:




  1. Recording: using HTTP(S) Test Script Recorder for automation of the HTTP Request samplers creation. The idea is that you execute your test scenario on mobile device and JMeter captures the traffic and creates the relevant requests.


  2. Parameterization: if your want to use different data for different virtual users you can configure JMeter to read it from external sources (files, databases, etc.), the most commonly used test element is CSV Data Set Config


  3. Synchronizing Timer: this guy ensures that samplers it its scope are executed at exactly the same moment. Normally JMeter executes requests as fast as it can, but it doesn't guarantee that requests will happen at exactly the same moment unless you use the Syncrhonizing Timer.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 29 '18 at 5:52









Dmitri TDmitri T

74.9k33765




74.9k33765













  • Thanks. I tried and it is only reading one device and fire one request per thread, basically doing consecutive rather than concurrent. It is a challenge and jmeter don't have the capacity to read from a file and make all the requests concurrent. For the time being I will create 1000+ threads manually with each API request and fire them as concurrent.

    – Swamy Bale
    Nov 30 '18 at 19:35





















  • Thanks. I tried and it is only reading one device and fire one request per thread, basically doing consecutive rather than concurrent. It is a challenge and jmeter don't have the capacity to read from a file and make all the requests concurrent. For the time being I will create 1000+ threads manually with each API request and fire them as concurrent.

    – Swamy Bale
    Nov 30 '18 at 19:35



















Thanks. I tried and it is only reading one device and fire one request per thread, basically doing consecutive rather than concurrent. It is a challenge and jmeter don't have the capacity to read from a file and make all the requests concurrent. For the time being I will create 1000+ threads manually with each API request and fire them as concurrent.

– Swamy Bale
Nov 30 '18 at 19:35







Thanks. I tried and it is only reading one device and fire one request per thread, basically doing consecutive rather than concurrent. It is a challenge and jmeter don't have the capacity to read from a file and make all the requests concurrent. For the time being I will create 1000+ threads manually with each API request and fire them as concurrent.

– Swamy Bale
Nov 30 '18 at 19:35






















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53529780%2fnewbie-need-help-in-designing-test-plan-in-jmeter-for-concurrent-api-calls%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Lallio

Futebolista

Jornalista