You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: