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
We should create standard benchmark to test memory usage, startup time, and cpu usage among all of our browsers and platforms. This will help us catch memory leaks, upstream performance regressions, and just in general have a better sense of how the browsers are doing.
As of right now I know our WebKit for Windows leaks memory. I'll continue to update this issue with more findings.
The text was updated successfully, but these errors were encountered:
Just piggybacking on this idea. I think this would be really helpful when folks are planning to provision VM instances for tests. If there are benchmarks, it helps understand how much time will be spent in the setup and thus can be the deciding factor between running tests in serial vs creating a new container for each test suite.
for what it's worth, when I run chromium via playwright in a 512mb limited docker container, it can't make a screenshot within 30 seconds. So I added a linux swap file of 4GB to the docker host, and that solved the issue for me (makes screenshots with no issue.)
We should create standard benchmark to test memory usage, startup time, and cpu usage among all of our browsers and platforms. This will help us catch memory leaks, upstream performance regressions, and just in general have a better sense of how the browsers are doing.
As of right now I know our WebKit for Windows leaks memory. I'll continue to update this issue with more findings.
The text was updated successfully, but these errors were encountered: