Skip to content
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

Closed
alexblack opened this issue Oct 26, 2016 · 6 comments
Closed

Experiencing a significant performance problem #2943

alexblack opened this issue Oct 26, 2016 · 6 comments

Comments

@alexblack
Copy link

alexblack commented Oct 26, 2016

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:

  1. Parse-server 2.2.23 (also tried rolling back to 2.2.22, no change)
  2. Database is Mongo, at mLab, no visible change in metrics there, it looks good to me
  3. Deployed at Heroku, on (4) 2x dynos
  4. Using node express

screenshot 2016-10-26 11 47 00

@alexblack
Copy link
Author

screen_shot_2016-10-27_at_7 49 58_am

@flovilmart
Copy link
Contributor

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.

@alexblack
Copy link
Author

Thanks for the input, we'll look at Mongo!

@alexblack
Copy link
Author

Thanks for the fast response @flovilmart , very helpful. 👍

@alexblack
Copy link
Author

alexblack commented Oct 26, 2016

It was mongo, we've now added an index to a new class we'd created, and the problem has gone away. Thanks again.

@flovilmart
Copy link
Contributor

As expected

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants