Repository navigation
Replies: 2 comments 17 replies
|
Interesting that 1 PHP process causes 200% load. |
1 reply
|
What will be initially useful is
If I'm not mistaken you have had this same issue in several versions of Relay in a row surviving large-scale redesigns of the internals. There must be somehing unique about this setup or server. One thing I know would cause this problem is if an fpm worker was killed was Edit: I am also going to rework our spinlocks to also be robust so Relay will just crash rather than spin. |
16 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
After upgrading to v0.40.0 we're seeing CPU spontaneously maxing out on PHP workers and staying that way indefinitely.
This is on a QA/DEV server where traffic doesn't explain the anomaly, and only change made was the relay upgrade to 0.40.
@michael-grunder what else would you need to help diagnose/troubleshoot?
All reactions