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

[Bug]: Webkit tests are 2-3x slower than Chrome or Firefox #31481

Closed
pascalknupper opened this issue Jun 28, 2024 · 4 comments
Closed

[Bug]: Webkit tests are 2-3x slower than Chrome or Firefox #31481

pascalknupper opened this issue Jun 28, 2024 · 4 comments

Comments

@pascalknupper
Copy link

Version

1.45.0

Steps to reproduce

Tests in Webkit seem to be slower than usual recently. The same set of tests takes round about 2-3x in webkit than running in chrome.

Tests are running in "mcr.microsoft.com/playwright:v1.45.0-jammy" docker container. We are also heavily make use of the visual comparison.

I´ll see if I can prepare a repo for reproduction.

image

Expected behavior

Performance in Webkit is improved

Actual behavior

Tests in Webkit are 2-3x slower than in Chrome or Firefox

Additional context

No response

Environment

System:
    OS: Linux 5.15 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
    CPU: (6) arm64 unknown
    Memory: 6.55 GB / 7.67 GB
    Container: Yes
  Binaries:
    Node: 20.15.0 - /usr/bin/node
    Yarn: 1.22.22 - /usr/bin/yarn
    npm: 10.7.0 - /usr/bin/npm
  Languages:
    Bash: 5.1.16 - /usr/bin/bash
  npmPackages:
    @playwright/test: ^1.45.0 => 1.45.0
@StanislavGrishaev
Copy link

take a look at this - #18119 (comment)
it helped me

@pavelfeldman
Copy link
Member

There isn't much we can do without the repro. Are you saying it is a regression relative to 1.44?

@pascalknupper
Copy link
Author

thanks @StanislavGrishaev I´ll see whether this configuration change will improve our test performance in webkit

@mxschmitt
Copy link
Member

I'll close it for now, if you have a reproduction repository, feel free to re-file and linking to this one. Thanks for your understanding!

(re above, we recommend tracing over video, since its much more powerful and requires less CPU/memory).

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

4 participants