-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Experiencing a significant performance problem #2943
Comments
Looks like it's stalling on your mongodb command, Not sure how it's related to parse-server's code. That is likely to be a deployment scaling problem. Look at your indexes, slow queries, mongodb configurations etc... Not sure how we can help you fix that. Not sure either there is anything to fix in parse-server. |
Thanks for the input, we'll look at Mongo! |
Thanks for the fast response @flovilmart , very helpful. 👍 |
It was mongo, we've now added an index to a new class we'd created, and the problem has gone away. Thanks again. |
As expected |
Hi, we'll look at posting some more thorough steps to reproduce and details, but, right now we're experiencing some major issues, and any insights or suggestions would be helpful.
It looks like an update in our mobile app is causing a lot more requests to hit our parse-server, and our deployment at Heroku is not standing up, requests are taking 30s to respond.
New relic analysis seems to indicate that 80% of the time is spent in handleParseHeaders
We're also seeing more errors than normal out of one of our cloud functions, a
beforeSave
trigger. We are working change things in our app to minimize this, but, in the meantime we're still in bad spot.Details:
2.2.23
(also tried rolling back to2.2.22
, no change)The text was updated successfully, but these errors were encountered: