K6 stops generating load for a short time during long test

[codebien]

Hi @Nesodus,
I need more details for understanding your real problem and providing a solution.

Can you share the following points, please?

• Which executor are you using and ideally more about your test code.
• Is the graph shared showing k6’s RPS collected with InfluxDB or is the RPS got from your server?
• Do you see any dropped iteration?
• Are you setting other options for InfluxDB output?
• Are running k6, InfluxDB and the service under test on dedicated machines? If not, what is the distribution?

@Nesodus

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.

This is expected. Increasing K6_INFLUXDB_PUSH_INTERVAL will only help if the problem would be the raw number of HTTP requests received by InfluxDB but this isn’t the real problem most of the time. What makes pressure on InfluxDB is the number/complexity of metrics to handle for each request so increasing the push interval generates HTTP requests that contain more metrics so probably more load for InfluxDB.

You can check The flush operation took higher than the expected set push interval - #3 by codebien - Grafana k6 - Grafana Labs Community Forums for the available options for improving the situation with InfluxDBv1 performance.