ramp-up outputs

gistfile1.txt

@RampUp(startRps = 1, targetRps = 60, durationInMins = 1)
ohne max. connection und mit 1 sec response zeit, 
würde sowas erwarten:
   10s  20s  30s  40s  50s  60s
   55   210  465  820  1275 1830

weil pro Sekunde, +1 request Anstieg:
   1s 2s 3s ... 10s 
   1  2  3      10 = 55 total
   
   
Test Setup1:

http.maxConnections=10
http.readTimeout=15000
@RampUp(startRps = 1, targetRps = 60, durationInMins = 1)
withFixedDelay(1000)

Output (per 10 secs):
   10s  20s  30s  40s  50s  60s
+  62   166  261  360  460  559 

Was passiert?
Sobald die Simulation 10rps erreicht, bleibt dort, weil max. connection = 10, 
d.H pro sec max. 10 request, 100 per 10 sec

Test Setup2:

http.maxConnections=10
http.readTimeout=15000
@RampUp(startRps = 1, targetRps = 60, durationInMins = 1)
withFixedDelay(10000)

   10s  20s  30s  40s  50s  60s
+  10   20   30   40   50   60

Was passiert?
10 sec pro request delay, d.H für max.conn=10, 10 rp10secs

Test Setup3:

http.maxConnections=10
http.readTimeout=15000
@RampUp(startRps = 1, targetRps = 60, durationInMins = 1)
withFixedDelay(5000)

Ramp-up will be limited by maxConnection * (10 period / 5sec)
   10s  20s  30s  40s  50s  60s
+  20   40   60   80   100  120 

Was passiert?
max. conn = 10, und 5 secs per request delay. d.H max 20 rp10secs, 
statt 55/62 wir haben nun 20, für erste 10 sec.

Test Setup4:

http.maxConnections=50
http.readTimeout=15000
@RampUp(startRps = 1, targetRps = 60, durationInMins = 1)
withFixedDelay(1000)

Ramp-up will be limited by maxConnection * (10 period / 5sec)
   10s  20s  30s  40s  50s  60s
+  63   226  491  857  1324 1823 <- read      max. connection limitiert nicht mehr rps.
   55   210  465  820  1275 1830 <- expected