Docs unclear

Hi,

maybe it’s just me, but after a few hours of using the tool (which is great btw), I’m still a little confused on what the options mean. In particular, I’m confused about the mismatch between cli options and yml options, e.g.

artillery quick --duration 60 --rate 10 -n 20 http://my.app.dev/api/resource

Is explained as “To create 10 virtual users every second for 60 seconds which will send 20 GET requests each”.

But when reading phases docs, I only see these options: arrivalRate, rampTo, arrivalCount and pause. Which one of those maps to nin the above (as I understand neither, how do I make each user make 20 requests then?). Also what's the difference betweenarrivalCountandarrivalRate` and how does that map to that cli example?

Perhaps a few more fleshed out examples could help. For example, that same CLI example “To create 10 virtual users every second for 60 seconds which will send 20 GET requests each” - how do you replicate that in yml?

How do I use artillery to keep ramping up until server/artillery crashes?

Sorry if this issue seems all over the place, just wanted to discuss how the docs could be improved (or perhaps it’s just me…).

[KidkArolis]

What’s the difference between “RPS Count” vs “Mean RPS”?

[hassy]

hi @KidkArolis

1. RPS count is the total number of requests made in a period. Mean RPS is the average number of requests per second during that period.
2. Check out the loop command: https://artillery.io/docs/testing_http.html#loop-through-a-number-of-requests

arrivalRate is indeed the number of users “added” every second (ie arriving to use the application) - that’s what --rate corresponds to.