Skip to content
This repository has been archived by the owner on Sep 21, 2021. It is now read-only.

Dump logs kept in the memory to the local file during the Runtime #644

Closed
baflQA opened this issue Jul 6, 2018 · 3 comments
Closed

Dump logs kept in the memory to the local file during the Runtime #644

baflQA opened this issue Jul 6, 2018 · 3 comments
Labels

Comments

@baflQA
Copy link
Contributor

baflQA commented Jul 6, 2018

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:
zrzut ekranu 2018-07-06 o 13 21 55

The significant drop in the consumption was observed after using the cleanup functionality in the dashboard.

Actual behaviour is, quoting @diemol

the array is kept in memory and dump to a file when Zalenium shuts down

@pearj
Copy link
Collaborator

pearj commented Jul 8, 2018

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.

@diemol
Copy link
Contributor

diemol commented Jul 8, 2018

Right, to be more precise, the logs are not in memory, but the information shown in the dashboard, which could add up after running a lot of tests.

We should dump this to disk when it grows too much and then just append new entries.

@diemol
Copy link
Contributor

diemol commented Nov 27, 2018

Merged the fix into master and we will release it in ~1 week, together with other bug fixes.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants