-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Cypress performance issues #8297
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
Comments
There have not been any reports of performance issues starting in 4.11.
|
I have also experienced the "slowness". It is related to Chrome update and not Cypress update. |
I agree that it most likely is a chrome issue - when I downgrade to even 4.8, everything is just as bad. But there's just no easy way to downgrade chrome. |
We have a tool to help track down previous versions of Chromium to download so you can run Cypress within them and track down any newer bugs: https://chromium.cypress.io/ I wouldn't really be able to track down a Chrome bug without being given a reproducible example to run against to see this specific performance issue. If this is also happening in Electron on previous versions, then you could isolate it to a specific version as well - since those are set to a specific version for each Cypress release. |
I was able downgrade for a few tests to 79 [stupid chrome updates itself even with auto updates turned off]. and 100% it was waaaay snappier, faster and more reliable.... until it updated to 84 again. |
FYI 5.0 is experiencing the same slowness @jennifer-shehane how do I specify for the cypress to use an older chromium version from the link that you provided?
This is what I'm getting every time. |
I haven't been able to upgrade to higher versions since 4.8.0 because of slow typing which causes my tests to fail. I tried the 4.12.1 and it seems that the slow typing still persists, however, it only happens on the first time the tying command is executed. On subsequent typing commands, the typing occurs at the normal speed (fast). I have witnessed this in both headed and headless test runs. Regarding the issues with CPU usage: Here is CPU usage for 4.12.1 CPU usage for 4.8.0 As we can see in both cases the CPU usage is quite high for chrome browser. |
@alexmonteirocastro hmm so it doesn't slow down in 4.8 for you? That's odd, because the only thing that SEEMED to help was when I downgraded my chrome for a few seconds. 4.8 with newest chrome is behaving just like on 4.12. |
also having troubles with significant slower testruns.. (about ~2x slower) |
After a LOT of testing the issue is moving from cypress 4.8 to 4.9 - this wasn't chrome's fault after all. |
I use Cypress 5.0 with Chrome 84 on OSX and cannot reproduce any of the above issues. Memory consumption and overall speed is consistent with what we have seen for the last 6 months or so, regularly updating Cypress when a new release is available. EDIT: Just noticed that you said Mac. Nevermind the question below. @Jacek-fstack are you on a Windows box by any chance? The only times we have had performance issues it has been on those, and almost always due to an external program (antivirus etc) of some sort. |
Also, people struggling with this, have you tried a clean install of Cypress along with Chrome and Nodejs? |
@csvan nope, I'm on mac and running from my host edit: just noticed, you noticed, ignore the answer, lol |
This is a huge problem... with cypress 5.0.0 we have like 2k requests and with 4.8.0 we have like 100 requests... |
After some research it looks like this issue started in 4.9 and is related to asset requests being cancelled and retried a bunch of times. We see it in the dev console on both electron and chrome. Downgrading to 4.8 or using Firefox we do not see this issue. |
@jennifer-shehane can you maybe have a look into it? |
I am experiencing the same issue. We are having to rollback our upgrade. |
Also affects 5.1 |
👍 ill follow this thread for a resolution I'm seeing the same issue re: clicks etc |
Hi everyone, I have been reading through this thread, and it sounds like the main issue is that CPU is being maxed out to 100% for the duration of the test run. This can lead to other strange behavior, including requests being canceled, Cypress commands taking too long and timing out, and video compression being throttled to take a really long time. There was a CPU performance regression introduced in version 4.9.0 of Cypress that has been identified in #8012 and will be fixed in the next release of Cypress. That is probably the reason behind the issues described in these comments. Since this issue is effectively a duplicate of #8012, I'm going to close this thread. If, after upgrading to a version of Cypress newer than 5.1.0, your issue is not fixed, please open a new issue describing the problem and we can investigate further. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Since about version 4.11 our cypress has become insanely slow.
It hogs network like crazy [any page I'm trying to load, like this github post is taking forever when tests are running]
Failed video compression takes AGES
it logs progress every few seconds, and all I'm seeing are 1-5% increments in that time
Typing has been insanely slow as well.
Tests in general got exponentially longer.
Is it only our instance or did anyone else experience it?
I'm not really sure where to look for a fix for this.
Anything you guys can point me to would help! thanks!
Also: headless seems to be WAY SLOWER then the non-headless, which is already really slow.
All in CHROME - electron doesn't seem to be affected by this.
Versions
4.11, 4.12
The text was updated successfully, but these errors were encountered: