Jmeter: Scenario to test 5 users with ramp up 1 hour to trigger 10 thousand requests












0














Jmeter: We have a scenario where 5 users should trigger 10 thousand requests in 1 hour, to achieve this below configurations have been done.




  1. Thread group - users - 5; ramp up - 3600 (secs); loop count - 1

  2. Loop controller value: 10000

  3. Request is under this Loop Controller


When executed the above scenario, Jmeter is executing/triggering 5 users in 1 second only.



Are these configurations correct to achieve our scenario load testing output.



Please suggest and guide.






jmeter







share|improve this question



























    0














    Jmeter: We have a scenario where 5 users should trigger 10 thousand requests in 1 hour, to achieve this below configurations have been done.




    1. Thread group - users - 5; ramp up - 3600 (secs); loop count - 1

    2. Loop controller value: 10000

    3. Request is under this Loop Controller


    When executed the above scenario, Jmeter is executing/triggering 5 users in 1 second only.



    Are these configurations correct to achieve our scenario load testing output.



    Please suggest and guide.






    jmeter







    share|improve this question

























      0












      0








      0







      Jmeter: We have a scenario where 5 users should trigger 10 thousand requests in 1 hour, to achieve this below configurations have been done.




      1. Thread group - users - 5; ramp up - 3600 (secs); loop count - 1

      2. Loop controller value: 10000

      3. Request is under this Loop Controller


      When executed the above scenario, Jmeter is executing/triggering 5 users in 1 second only.



      Are these configurations correct to achieve our scenario load testing output.



      Please suggest and guide.






      jmeter







      share|improve this question













      Jmeter: We have a scenario where 5 users should trigger 10 thousand requests in 1 hour, to achieve this below configurations have been done.




      1. Thread group - users - 5; ramp up - 3600 (secs); loop count - 1

      2. Loop controller value: 10000

      3. Request is under this Loop Controller


      When executed the above scenario, Jmeter is executing/triggering 5 users in 1 second only.



      Are these configurations correct to achieve our scenario load testing output.



      Please suggest and guide.






      jmeter




      jmeter






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 13 at 5:24









      la1

      9819




      9819
























          1 Answer
          1






          active

          oldest

          votes


















          1














          Your configuration is a little bit incorrect. In your setup




          1. JMeter will start with one user which will execute 10 000 requests as fast as it can

          2. In 12 minutes another user will start and execute 10 000 requests as fast as it can

          3. In 12 minutes another user will start and execute 10 000 requests as fast as it can

          4. etc.


          You will not get 10 000 requests evenly distributed for 1 hour, instead you will have 50 000 requests in "spikes"



          Instead I would suggest the following configuration:





          • Thread Group (Number of Users: 5, Ramp-Up Period : 1, Loop Count: Forever, Duration: 3600)



            enter image description here





            • Request





              • Constant Throughput Timer with Target Throughput: 166.6666666667



                enter image description here



                Constant Throughput Timer will limit JMeter to the desired rate which will give you 10 000 requests in hour (assuming your application will be able to handle the requests fast enough)









          In the majority of cases it's easier to use custom Thread Groups such as Ultimate Thread Group. It's easier to configure as it provides a graph demonstrating anticipated virtual users behaviour.



          enter image description here



          You can install custom thread groups using JMeter Plugins Manager



          enter image description here






          share|improve this answer





















          • Thanks a lot for detailed information. Just small query so Target Throughput: 166.6666666667 formula is (10000/60 mints) which gives 166 value. Our one more scenario is, 1,00,000 requests per hour per 1 user so Target Throughput should be: 1666.666666667 (1,00,000/60) and the duration would remain 3600 with users 1. Please suggest. And thanks a lot for guidance.
            – la1
            Nov 13 at 6:39






          • 1




            It should be sufficient to change Calculate Throughput Based On to this thread only
            – Dmitri T
            Nov 13 at 6:52










          • Thanks for confirming, however when ran for 1 hour (1,00,000 requests, Target Throughput - 1670 requests per minute) , the execution got stopped after 1 hour and the requests triggered are 67,000 only. It could not complete 1,00,000 and stopped the execution. Please guide if doing something wrong here.
            – la1
            Nov 14 at 5:29






          • 1




            You might need to increase the number of threads (virtual users) in the Thread Group as Constant Throughput Timer can only pause the requests in order to limit JMeter to the specified throughput. As an alternative you can try Throughput Shaping Timer and Concurrency Thread Group combination, they can be connected via feedback function
            – Dmitri T
            Nov 14 at 5:34






          • 1




            So JMeter will kick off extra threads if current amount is not enough in order to conduct the required load
            – Dmitri T
            Nov 14 at 5: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%2f53274333%2fjmeter-scenario-to-test-5-users-with-ramp-up-1-hour-to-trigger-10-thousand-requ%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









          1














          Your configuration is a little bit incorrect. In your setup




          1. JMeter will start with one user which will execute 10 000 requests as fast as it can

          2. In 12 minutes another user will start and execute 10 000 requests as fast as it can

          3. In 12 minutes another user will start and execute 10 000 requests as fast as it can

          4. etc.


          You will not get 10 000 requests evenly distributed for 1 hour, instead you will have 50 000 requests in "spikes"



          Instead I would suggest the following configuration:





          • Thread Group (Number of Users: 5, Ramp-Up Period : 1, Loop Count: Forever, Duration: 3600)



            enter image description here





            • Request





              • Constant Throughput Timer with Target Throughput: 166.6666666667



                enter image description here



                Constant Throughput Timer will limit JMeter to the desired rate which will give you 10 000 requests in hour (assuming your application will be able to handle the requests fast enough)









          In the majority of cases it's easier to use custom Thread Groups such as Ultimate Thread Group. It's easier to configure as it provides a graph demonstrating anticipated virtual users behaviour.



          enter image description here



          You can install custom thread groups using JMeter Plugins Manager



          enter image description here






          share|improve this answer





















          • Thanks a lot for detailed information. Just small query so Target Throughput: 166.6666666667 formula is (10000/60 mints) which gives 166 value. Our one more scenario is, 1,00,000 requests per hour per 1 user so Target Throughput should be: 1666.666666667 (1,00,000/60) and the duration would remain 3600 with users 1. Please suggest. And thanks a lot for guidance.
            – la1
            Nov 13 at 6:39






          • 1




            It should be sufficient to change Calculate Throughput Based On to this thread only
            – Dmitri T
            Nov 13 at 6:52










          • Thanks for confirming, however when ran for 1 hour (1,00,000 requests, Target Throughput - 1670 requests per minute) , the execution got stopped after 1 hour and the requests triggered are 67,000 only. It could not complete 1,00,000 and stopped the execution. Please guide if doing something wrong here.
            – la1
            Nov 14 at 5:29






          • 1




            You might need to increase the number of threads (virtual users) in the Thread Group as Constant Throughput Timer can only pause the requests in order to limit JMeter to the specified throughput. As an alternative you can try Throughput Shaping Timer and Concurrency Thread Group combination, they can be connected via feedback function
            – Dmitri T
            Nov 14 at 5:34






          • 1




            So JMeter will kick off extra threads if current amount is not enough in order to conduct the required load
            – Dmitri T
            Nov 14 at 5:35
















          1














          Your configuration is a little bit incorrect. In your setup




          1. JMeter will start with one user which will execute 10 000 requests as fast as it can

          2. In 12 minutes another user will start and execute 10 000 requests as fast as it can

          3. In 12 minutes another user will start and execute 10 000 requests as fast as it can

          4. etc.


          You will not get 10 000 requests evenly distributed for 1 hour, instead you will have 50 000 requests in "spikes"



          Instead I would suggest the following configuration:





          • Thread Group (Number of Users: 5, Ramp-Up Period : 1, Loop Count: Forever, Duration: 3600)



            enter image description here





            • Request





              • Constant Throughput Timer with Target Throughput: 166.6666666667



                enter image description here



                Constant Throughput Timer will limit JMeter to the desired rate which will give you 10 000 requests in hour (assuming your application will be able to handle the requests fast enough)









          In the majority of cases it's easier to use custom Thread Groups such as Ultimate Thread Group. It's easier to configure as it provides a graph demonstrating anticipated virtual users behaviour.



          enter image description here



          You can install custom thread groups using JMeter Plugins Manager



          enter image description here






          share|improve this answer





















          • Thanks a lot for detailed information. Just small query so Target Throughput: 166.6666666667 formula is (10000/60 mints) which gives 166 value. Our one more scenario is, 1,00,000 requests per hour per 1 user so Target Throughput should be: 1666.666666667 (1,00,000/60) and the duration would remain 3600 with users 1. Please suggest. And thanks a lot for guidance.
            – la1
            Nov 13 at 6:39






          • 1




            It should be sufficient to change Calculate Throughput Based On to this thread only
            – Dmitri T
            Nov 13 at 6:52










          • Thanks for confirming, however when ran for 1 hour (1,00,000 requests, Target Throughput - 1670 requests per minute) , the execution got stopped after 1 hour and the requests triggered are 67,000 only. It could not complete 1,00,000 and stopped the execution. Please guide if doing something wrong here.
            – la1
            Nov 14 at 5:29






          • 1




            You might need to increase the number of threads (virtual users) in the Thread Group as Constant Throughput Timer can only pause the requests in order to limit JMeter to the specified throughput. As an alternative you can try Throughput Shaping Timer and Concurrency Thread Group combination, they can be connected via feedback function
            – Dmitri T
            Nov 14 at 5:34






          • 1




            So JMeter will kick off extra threads if current amount is not enough in order to conduct the required load
            – Dmitri T
            Nov 14 at 5:35














          1












          1








          1






          Your configuration is a little bit incorrect. In your setup




          1. JMeter will start with one user which will execute 10 000 requests as fast as it can

          2. In 12 minutes another user will start and execute 10 000 requests as fast as it can

          3. In 12 minutes another user will start and execute 10 000 requests as fast as it can

          4. etc.


          You will not get 10 000 requests evenly distributed for 1 hour, instead you will have 50 000 requests in "spikes"



          Instead I would suggest the following configuration:





          • Thread Group (Number of Users: 5, Ramp-Up Period : 1, Loop Count: Forever, Duration: 3600)



            enter image description here





            • Request





              • Constant Throughput Timer with Target Throughput: 166.6666666667



                enter image description here



                Constant Throughput Timer will limit JMeter to the desired rate which will give you 10 000 requests in hour (assuming your application will be able to handle the requests fast enough)









          In the majority of cases it's easier to use custom Thread Groups such as Ultimate Thread Group. It's easier to configure as it provides a graph demonstrating anticipated virtual users behaviour.



          enter image description here



          You can install custom thread groups using JMeter Plugins Manager



          enter image description here






          share|improve this answer












          Your configuration is a little bit incorrect. In your setup




          1. JMeter will start with one user which will execute 10 000 requests as fast as it can

          2. In 12 minutes another user will start and execute 10 000 requests as fast as it can

          3. In 12 minutes another user will start and execute 10 000 requests as fast as it can

          4. etc.


          You will not get 10 000 requests evenly distributed for 1 hour, instead you will have 50 000 requests in "spikes"



          Instead I would suggest the following configuration:





          • Thread Group (Number of Users: 5, Ramp-Up Period : 1, Loop Count: Forever, Duration: 3600)



            enter image description here





            • Request





              • Constant Throughput Timer with Target Throughput: 166.6666666667



                enter image description here



                Constant Throughput Timer will limit JMeter to the desired rate which will give you 10 000 requests in hour (assuming your application will be able to handle the requests fast enough)









          In the majority of cases it's easier to use custom Thread Groups such as Ultimate Thread Group. It's easier to configure as it provides a graph demonstrating anticipated virtual users behaviour.



          enter image description here



          You can install custom thread groups using JMeter Plugins Manager



          enter image description here







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 13 at 6:25









          Dmitri T

          68.7k33458




          68.7k33458












          • Thanks a lot for detailed information. Just small query so Target Throughput: 166.6666666667 formula is (10000/60 mints) which gives 166 value. Our one more scenario is, 1,00,000 requests per hour per 1 user so Target Throughput should be: 1666.666666667 (1,00,000/60) and the duration would remain 3600 with users 1. Please suggest. And thanks a lot for guidance.
            – la1
            Nov 13 at 6:39






          • 1




            It should be sufficient to change Calculate Throughput Based On to this thread only
            – Dmitri T
            Nov 13 at 6:52










          • Thanks for confirming, however when ran for 1 hour (1,00,000 requests, Target Throughput - 1670 requests per minute) , the execution got stopped after 1 hour and the requests triggered are 67,000 only. It could not complete 1,00,000 and stopped the execution. Please guide if doing something wrong here.
            – la1
            Nov 14 at 5:29






          • 1




            You might need to increase the number of threads (virtual users) in the Thread Group as Constant Throughput Timer can only pause the requests in order to limit JMeter to the specified throughput. As an alternative you can try Throughput Shaping Timer and Concurrency Thread Group combination, they can be connected via feedback function
            – Dmitri T
            Nov 14 at 5:34






          • 1




            So JMeter will kick off extra threads if current amount is not enough in order to conduct the required load
            – Dmitri T
            Nov 14 at 5:35


















          • Thanks a lot for detailed information. Just small query so Target Throughput: 166.6666666667 formula is (10000/60 mints) which gives 166 value. Our one more scenario is, 1,00,000 requests per hour per 1 user so Target Throughput should be: 1666.666666667 (1,00,000/60) and the duration would remain 3600 with users 1. Please suggest. And thanks a lot for guidance.
            – la1
            Nov 13 at 6:39






          • 1




            It should be sufficient to change Calculate Throughput Based On to this thread only
            – Dmitri T
            Nov 13 at 6:52










          • Thanks for confirming, however when ran for 1 hour (1,00,000 requests, Target Throughput - 1670 requests per minute) , the execution got stopped after 1 hour and the requests triggered are 67,000 only. It could not complete 1,00,000 and stopped the execution. Please guide if doing something wrong here.
            – la1
            Nov 14 at 5:29






          • 1




            You might need to increase the number of threads (virtual users) in the Thread Group as Constant Throughput Timer can only pause the requests in order to limit JMeter to the specified throughput. As an alternative you can try Throughput Shaping Timer and Concurrency Thread Group combination, they can be connected via feedback function
            – Dmitri T
            Nov 14 at 5:34






          • 1




            So JMeter will kick off extra threads if current amount is not enough in order to conduct the required load
            – Dmitri T
            Nov 14 at 5:35
















          Thanks a lot for detailed information. Just small query so Target Throughput: 166.6666666667 formula is (10000/60 mints) which gives 166 value. Our one more scenario is, 1,00,000 requests per hour per 1 user so Target Throughput should be: 1666.666666667 (1,00,000/60) and the duration would remain 3600 with users 1. Please suggest. And thanks a lot for guidance.
          – la1
          Nov 13 at 6:39




          Thanks a lot for detailed information. Just small query so Target Throughput: 166.6666666667 formula is (10000/60 mints) which gives 166 value. Our one more scenario is, 1,00,000 requests per hour per 1 user so Target Throughput should be: 1666.666666667 (1,00,000/60) and the duration would remain 3600 with users 1. Please suggest. And thanks a lot for guidance.
          – la1
          Nov 13 at 6:39




          1




          1




          It should be sufficient to change Calculate Throughput Based On to this thread only
          – Dmitri T
          Nov 13 at 6:52




          It should be sufficient to change Calculate Throughput Based On to this thread only
          – Dmitri T
          Nov 13 at 6:52












          Thanks for confirming, however when ran for 1 hour (1,00,000 requests, Target Throughput - 1670 requests per minute) , the execution got stopped after 1 hour and the requests triggered are 67,000 only. It could not complete 1,00,000 and stopped the execution. Please guide if doing something wrong here.
          – la1
          Nov 14 at 5:29




          Thanks for confirming, however when ran for 1 hour (1,00,000 requests, Target Throughput - 1670 requests per minute) , the execution got stopped after 1 hour and the requests triggered are 67,000 only. It could not complete 1,00,000 and stopped the execution. Please guide if doing something wrong here.
          – la1
          Nov 14 at 5:29




          1




          1




          You might need to increase the number of threads (virtual users) in the Thread Group as Constant Throughput Timer can only pause the requests in order to limit JMeter to the specified throughput. As an alternative you can try Throughput Shaping Timer and Concurrency Thread Group combination, they can be connected via feedback function
          – Dmitri T
          Nov 14 at 5:34




          You might need to increase the number of threads (virtual users) in the Thread Group as Constant Throughput Timer can only pause the requests in order to limit JMeter to the specified throughput. As an alternative you can try Throughput Shaping Timer and Concurrency Thread Group combination, they can be connected via feedback function
          – Dmitri T
          Nov 14 at 5:34




          1




          1




          So JMeter will kick off extra threads if current amount is not enough in order to conduct the required load
          – Dmitri T
          Nov 14 at 5:35




          So JMeter will kick off extra threads if current amount is not enough in order to conduct the required load
          – Dmitri T
          Nov 14 at 5: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.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • 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%2f53274333%2fjmeter-scenario-to-test-5-users-with-ramp-up-1-hour-to-trigger-10-thousand-requ%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

          Guess what letter conforming each word

          Image
          6 $begingroup$ This is an entry in the Fortnightly Topic Challenge #41: Short and Sweet. 1 letter only could be mean anything . With an additional letter in front , could be used as medicine component and something you definitely learn or at least heard once. Add another letter in front , you would possibly hear that many times . Add an additional letter in front , you would found an independent country . With an additional letter, in the end , you would found something related to apple . Add another letter in the end , you would found something bad . Hint: Each letter is unique . word knowledge letters chemistry share | improve this question ...
          Read more

          Run scheduled task as local user group (not BUILTIN)

          Image
          0 I am trying to run a scheduled task with User Group (not a single user). This is working fine when I in the field "when running a task, use the following user account:" insert BUILTIN User Group (for example: Administrators or Users). But when I try it with the created Local User Group (example: TestGroup) it is not working. The Users in the TestGroup are the same as in the Administrators group. What could be the problem? Are there some restrictions to the Created User Group compared to BUILTINUsers? scheduled-tasks taskscheduler windowstaskschedule share | improve this question asked Nov 15 '18 at 15:36 Far...
          Read more

          Port of Spain

          Image
          For ports in the country of Spain, see List of ports in Spain. City in City of Port of Spain, Trinidad and Tobago Port of Spain City City of Port of Spain Top to bottom (left to right): Skyline of Port of Spain from Gulf of Paria; National Academy for the Performing Arts, Independence Square, Eric Williams Plaza; MovieTowne, Port of Port of Spain Motto(s):  "We Gather Strength As We Go Along" Port of Spain Coordinates: 10°40′N 61°31′W  /  10.667°N 61.517°W  / 10.667; -61.517 Coordinates: 10°40′N 61°31′W  /  10.667°N 61.517°W  / 10.667; -61.517 Country   Trinidad and Tobago Jurisdiction City of Port of Spain Settled 1560 Incorporated (town) 1853 Incorporated (city) 1914 Government  • Mayor Joel Martinez  • Governing body City Corporation Area [1]  • City 12 km 2 (5 sq mi) Elevation [2] 66 m (217 ft) Population (2011) [1]  • City 37,074  • Rank 3rd  • Density 3,090/km 2 (8,000/sq mi)...
          Read more