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
{{ message }}
This repository has been archived by the owner on Sep 21, 2021. It is now read-only.
Zalenium Image Version(s):
3.12.0e
Env: K8S on AWS, deployed with the helm chart from the Zalenium repository.
Expected Behavior -
Zalenium saves the logs displayed in the Dashboard to the local file so that they are not stored in the memory during the runtime.
Actual Behavior -
While running a long suite of tests, a lot of RAM is being consumed by the Hub pod. The picture below shows the amount of RAM consumed by the pod with the video recording turned off:
The significant drop in the consumption was observed after using the cleanup functionality in the dashboard.
I’m pretty sure the actual logs themselves aren’t kept in memory, but rather the list of test sessions and related file names, ie log and video file names.
Zalenium Image Version(s):
3.12.0e
Env: K8S on AWS, deployed with the helm chart from the Zalenium repository.
Expected Behavior -
Zalenium saves the logs displayed in the Dashboard to the local file so that they are not stored in the memory during the runtime.
Actual Behavior -
While running a long suite of tests, a lot of RAM is being consumed by the Hub pod. The picture below shows the amount of RAM consumed by the pod with the video recording turned off:
The significant drop in the consumption was observed after using the cleanup functionality in the dashboard.
Actual behaviour is, quoting @diemol
The text was updated successfully, but these errors were encountered: