Hi there,
I’m hoping to be able to record, as live output, the number of iterations started per second by k6. This GitHub issue comment indicates that the iteration counter metric is emitted at the end of the corresponding iteration, meaning it cannot serve as a reliable indicator of the actual request rate (instead it acts as a response rate).
This is within the context of the use of a ramping-arrival-rate executor, where it is desirable to compare a changing request rate to the various performance metrics of the SUT. I am not interested (in this case) in the number of requests that have received responses per second (which is what the http_req/iteration counters can get you), but simply the number started per second regardless of whether a response has been received.
One way I figure I could infer this information would be to calculate something akin to response.timings.duration + response.timings.connecting, and then get the approx. request start time by subtracting this value from the current time, and then get my requests-started-per-second metric from there. Is there something more straightforward than this I can do?
3 posts - 2 participants