concurrency - How to do stress test with Jmeter step by step -

i want stress test website. main aim find performance degrading point, in terms of number concurrent users , number of hits/sec (rps).

i have used ultimate thread group , set number users 200 ramp of 200 seconds. have added throughput shaping timer ultimate thread group , set number of request per second 8. (if have 1 sampler hits per second controlled , 8 hits/sec. if have more 1 sampler hits not controlled , reached 20, 25,40 etc.. ended using constant throughput timer)

let's go stress testing. find performance degrading point, in terms of number of concurrent users , hits per second, how should simulate load. eg: website's expected degradation point 300 users @ 12 requests per second, @ avg response time of site 800ms. support more users may 500 users , may 15 rps. if want add delay between each sample, should adding timers? thread group or samplers?

thanks.

timers have scope. timers documentation:

note timers processed before each sampler in scope in found; if there several timers in same scope, all timers processed before each sampler. timers processed in conjunction sampler. timer not in same scope sampler not processed @ all. apply timer single sampler, add timer child element of sampler. timer applied before sampler executed. apply timer after sampler, either add next sampler, or add child of test action sampler.

so:

• if want delay single request - put timer of choice child of request.
• if you're aiming delay requests - put timer @ same level requests go
• if want delay part of requests - move them under i.e. simple controller

the similar situation highlighted in how use jmeter assertions in 3 easy steps guide:

the difference timers being processed before sampler , assertions executed after.