JMeter Thread Group setting, what does Rump-Up period mean?

Question

stress testing

Hello.
I am mastering JMeter, and in the process of smoking the manual and running trial tests, there was a misunderstanding of one point.
We have parameters:
Number of Threads - this is the number of users who will visit the site
Rump-Up period - this is the period after which our users will be launched
Loop Count - this is the number of cycles of execution by users of actions in the Thread Group

For testing, data was taken from ceiling
Number of Threads = 10
Rump-Up period =15 sec
Loop Count = 100
Further, what I did not fully understand:
We have 10 users "going" to the site within 15 seconds and this will all be repeated 100 times and as a result we have 1000 requests will go?
Those. the script should take 1500 seconds to go through, but 150 seconds pass.
I can not understand what and why it starts to run and how long it takes.

Answer 1

You have both loop count and schedule configured. Do not do it this way. In general, within 15 seconds you will have 10 virtual users on the site and during the whole time each of them (including the Rump-up period) will execute your request 100 times. That's all the magic. Over the time the script is executed, this practically does not correlate in any way, it all depends on how quickly the answers come

Answer 2

How can you use these options.
Let the intensity of execution of the scenario "Authentication, Creation and download of a document" equal to 8 per sec. And so that the test runs in this mode for 30 minutes or 1800 seconds.
That is, it is necessary that 8 threads (virtual user / thread) run in 1 second.
This means that 80,000 threads should start in 10,000 seconds.
This is if each thread will do one iteration of the test.
Set the settings:
If, however, it is permissible for one user to log in twice in a cycle, create and download a document, then the settings can be changed - users now need 2 times less, for the required intensity of work:
And if it is acceptable that 8 scenarios are executed in a cycle, then you can do this:
Due to the multiplicity of Users and Rump-Up, this is already equivalent to:

• Users - 4000
  
• Rump Up - 4000
  
• Loop Count - 8
  
• Duration - 1800
  
• Startup Delay - 0