Hello to k6 community and devs!
I’ll try to be quick about my issue.
I need to run a long test (around 8 hours), so I’ve prepared my scenario which worked perfectly fine on a shorter duration and launched it.
What I’ve witnessed after some time:
I thought that might be the issue with me sending metrics to InfluxDB, and yes, I got a warning which looked like this:
The flush operation took higher than the expected set push interval. If you see this message multiple times then the setup or configuration need to be adjusted to achieve a sustainable rate. output=InfluxDBv1 t=4.53481258s
After tweaking and increasing
PUSH_INTERVAL in k6 ENV’s problem didn’t disappear, unfortunately and I still see those warnings, matters not if there’s a 1 second interval or 3 seconds. All the same.
So I have two questions:
About that screenshot, I’ve checked system metrics as well (to see if I am right about my thoughts, that it’s just a metric thing). Exactly at moments of those RpS falls, system received less load (less CPU utilization on system side). It happened quite frequently as you can see. What would possibly stop load generation from k6 for a second-two?
To clarify, CPU consumption on a generator machine was around 20-25% (where k6 docker container resides) and I’m not using same Influxdb for system metrics, just for k6. System metrics are provided by Prometheus, to exclude metric issue.
What can I possibly do with that annoying warning? How can I fix the issue?
Thank you a lot in advance!