Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory leak on load generator running large test #3822

Closed
Nova1hhh opened this issue Jul 1, 2024 · 3 comments
Closed

Memory leak on load generator running large test #3822

Nova1hhh opened this issue Jul 1, 2024 · 3 comments
Assignees
Labels

Comments

@Nova1hhh
Copy link

Nova1hhh commented Jul 1, 2024

Brief summary

I'm observing a memory leak on a virtual machine running a k6 test. The test is launched through a script file that imports one script and uses it in scenario with ramping-arrival-rate executor. There are two stages: 1 - from zero to 17,000 rps over 2 minutes, 2 - from 17,000 to 17,000 rps for 24 hours. The script is a simple GET request to a service that responds in about 5 ms, with a check for a 200 response code.
I tried using constant-vus to achieve approximately 17k rps - the result was the same.

Using k6 0.51.0 + xk6-output-influxdb v0.4.3 + xk6-kafka v0.26.0.
Sending messages to Kafka and metrics to InfluxDB are not used.

k6 version

0.51.0

OS

Astra Linux (16 cpu\64 ram)

Docker version and image (if applicable)

No response

Steps to reproduce the problem

Run a k6 scenario that successfully generates 17k rps to the service.

Expected behaviour

Get constant resource utilization of the generator under constant load.

Actual behaviour

64 GB of memory is gradually utilized over approximately 6 hours of load at 17k rps. The response time of the targeted service, the number of requests, and resource utilization are normal.

@Nova1hhh
Copy link
Author

Nova1hhh commented Jul 1, 2024

additional: GET requests are sent to the same URL.

@mstoykov
Copy link
Collaborator

mstoykov commented Jul 2, 2024

Hi @Nova1hhh, I see that you are using two different outputs, but are you also setting --no-thresholds --no-summary as recommended in the Running large tests.

You can also see #2367 and the linked issues in the first comment (among others).

@mstoykov mstoykov added awaiting user waiting for user to respond and removed triage labels Jul 2, 2024
@mstoykov
Copy link
Collaborator

mstoykov commented Aug 6, 2024

I am closing this issue - I expect that the above comment by me is the case and it has been a month since the last communicaiton by @Nova1hhh

@mstoykov mstoykov closed this as not planned Won't fix, can't repro, duplicate, stale Aug 6, 2024
@mstoykov mstoykov removed the awaiting user waiting for user to respond label Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants