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

Coordinator report memory performance improvements on long bombing runs #733

Open
daveharris1 opened this issue Sep 16, 2024 · 1 comment
Labels
5.9 new feature New feature or request
Milestone

Comments

@daveharris1
Copy link

NBomber version: 5.7.0
.NET version: 8.0

After speaking to Anton he believes the Coordinator memory usage can be be more performant when collating and producing the final reports:

The Coordinator do not keep logs in memory, it writes them on disk. The coordinator keep Realtime stats in memory which btw shouldn't be a huge problem. When JSON serialization happens for building HTML, it requires allocating a lot of RAM for long-running scenarios.

This can cause issues such as OOMKIlled on the Coordinator.

@AntyaDev AntyaDev added the 5.9 label Sep 16, 2024
@AntyaDev AntyaDev added the new feature New feature or request label Oct 30, 2024
@AntyaDev AntyaDev added this to the 5.9.0 milestone Oct 30, 2024
@AntyaDev
Copy link
Contributor

Hi @daveharris1
We added many new memory optimizations. Could you please try the latest 5.9 beta?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5.9 new feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants