Closed okaris closed 8 years ago
Hi, sorry for the question not related to your, you same that you use hirefire, i don't have sucefully setup hirefire demo manage, because i don't have the procfile to copy get the dyne manage name... how did you do? Thanks if you reply...
Closing due to lack of activity, please reopen if the issue persist.
Don't forget to include your current:
Check out this issue for an ideal bug report. The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!
For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities.
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
Environment Setup
mLab M3 Dedicated Replica Set Minimum 2dynos - Standart 1X Dyno on Heroku (HireFire.io autoscale based on newrelic appdex and heroku average reponse time) Parse Server 2.2.4 Amazon S3
Steps to reproduce
Some requests to Waves class and especially lately some ParseFiles result in very high reponse time. I have checked the requests to Waves class and they aren't unique requests, normally they run fast (also not related to load, they happen even when there is not much load). I have no idea why are some ParseFile requests are so slow.
Logs/Trace