How to generate a constant request rate in k6 with the new scenarios API?

This v0.27.0 release includes a new execution engine and lots of new executors that cater to your specific needs. It also includes the new scenarios API with lots of different options to configure and model the load on the system under test (SUT). This is the result of 1.5 years of work on the infamous #1007 PR 😂.


This is a companion discussion topic for the original entry at https://k6.io/blog/how-to-generate-a-constant-request-rate-with-the-new-scenarios-api

Just curious in the summary, what does min:108, max:148 meant by?

vus........................: 148         min=108 max=148
vus_max....................: 148         min=108 max=148