-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
ShipIt MacOS M1 taking 100% CPU #777
Comments
Dear contributor, because this issue seems to be inactive for quite some time now, I've automatically closed it. If you feel this issue deserves some attention from my human colleagues feel free to reopen it. |
Also often experience very high Ray CPU usage on my M2 even when nothing is logging. |
This issue has been open for quite some time, and we are happy to let you know that we are working on version 3.0. In this version, we have revisited Ray and are refactoring the application without removing any mandatory features. Among other things, we are focusing on the performance issues Ray seems to cause on various systems. We hope to release this version to the public soon and resolve the performance issues across different systems! Thank you for your patience regarding this issue. |
Mac Mini M1, running Sonoma 14.6.1 Ray 2.8.1 Every day I come to the machine and find the CPU usage fills the activity monitor. Stop Ray and all is back to normal. |
This isn't going to be terribly useful because I don't have more details to provide you. But I just noticed on my M1 that my battery was draining like crazy. Opened up the Activity Monitor and saw that a process named ShipIt was taking 100% CPU.
Possibly linked: element-hq/element-desktop#647
I inspected the process further and saw many references to Spatie/Ray.
I then forced-quit the process and Ray opened up immediately after. I had just installed a Ray update.
So I'm just reporting this so you can keep an eye out, maybe you have more insight as to what is going on. It may have been related to the update process, unsure.
The text was updated successfully, but these errors were encountered: