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

Slow down of tests - Debugging #422

Open
whrostre opened this issue Apr 30, 2024 · 3 comments
Open

Slow down of tests - Debugging #422

whrostre opened this issue Apr 30, 2024 · 3 comments

Comments

@whrostre
Copy link

Hello,

since a few weeks we have a strange slow down of our Selenium tests on moon. Several test execution steps take much longer than before e.g. opening the browser, clicking on elements etc. The time increase ranges from a second to several seconds.

We have already ruled out a few things:

  • We don't expect that the test object is the problem. (Locally we couldn't see any time increase)
  • There was also no update with Selenium or moon.
  • Memory and cpu usage of the pods seem to be also ok.
  • There also seems to be no network issue.

Do you have any suggestions to better debug such an issue? I would like to determine where the additional time is used. So basically during test x moon communication or the real execution in the test pod.

@vania-pooh
Copy link
Member

@whrostre make sure you have all required firewall rules to static resources: styles, scripts, images and so on. Some pages could be loading such files from third-party resources and this could slow down things.

@whrostre
Copy link
Author

whrostre commented May 3, 2024

@whrostre make sure you have all required firewall rules to static resources: styles, scripts, images and so on. Some pages could be loading such files from third-party resources and this could slow down things.

Thanks for the hint, but we already ruled out that the webpage we are testing is the issue. Since just opening the browser takes more time than before, without loading a webpage

@vania-pooh
Copy link
Member

@whrostre in that case I would check browser pods with kubectl describe po chrome-XXXX -n moon. Investigate this output and check how much time it takes to schedule the pod, to pull browser images and so on. Moon basically just creates a pod and waits for it to switch to Running state.

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

No branches or pull requests

2 participants