5 ms·
Yes indeed but wrk2 or Vegeta is still better for this particular use case (unless k6 has support for setting a constant RPS rate, afaik it does not), as otherw
by hassy 4y ago
Yes indeed but wrk2 or Vegeta is still better for this particular use case (unless k6 has support for setting a constant RPS rate, afaik it does not), as otherwise the overhead of establishing a new TCP connection for a single HTTP request will dominate the benchmark.
- imiric 4y ago> unless k6 has support for setting a constant RPS rate, afaik it does not Yes it can, via the `constant-arrival-rate` executor[1]. > the overhead of establishing a new TCP connection for a single HTTP request will dominate the benchmark By default, k6 will reuse TCP connections, and you have to explicitly disable it[2]. I'm not saying that wrk2 or Vegeta wouldn't be a good fit for this test, but k6 is also capable of it, with some minor configuration changes. [1]: https://k6.io/docs/using-k6/scenarios/executors/constant-arrival-rate/ https://k6.io/docs/using-k6/scenarios/executors/constant-arr... [2]: https://k6.io/docs/using-k6/k6-options/reference#no-connection-reuse https://k6.io/docs/using-k6/k6-options/reference#no-connecti...