parse-community / parse-server

Parse Server for Node.js / Express
https://parseplatform.org
Apache License 2.0
20.9k stars 4.78k forks source link

High Response Time - Especialy Parse File #1396

Closed okaris closed 8 years ago

okaris commented 8 years ago

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!

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

» 6 Apr 2016 13:41:14.978 303 <158>1 2016-04-06T10:41:14.657872+00:00 heroku router - - at=info method=POST path="/parse/classes/Waves" host=coralline.herokuapp.com request_id=e695d979-b818-4522-afa1-1ef5bd31671a fwd="176.55.82.62" dyno=web.1 connect=0ms service=8033ms status=200 bytes=112561 High Response Time
» 6 Apr 2016 13:42:05.125 303 <158>1 2016-04-06T10:42:04.828062+00:00 heroku router - - at=info method=POST path="/parse/classes/Waves" host=coralline.herokuapp.com request_id=ab402f80-928c-4297-b9f2-08847c3efe34 fwd="176.55.82.62" dyno=web.2 connect=0ms service=9684ms status=200 bytes=112561 High Response Time
» 6 Apr 2016 13:50:35.741 305 <158>1 2016-04-06T10:50:35.388542+00:00 heroku router - - at=info method=POST path="/parse/classes/Waves" host=coralline.herokuapp.com request_id=f77c3876-979d-499e-b20b-abf8f725f835 fwd="212.156.45.238" dyno=web.2 connect=0ms service=6834ms status=200 bytes=113110 High Response Time
» 6 Apr 2016 14:31:21.571 328 <158>1 2016-04-06T11:31:21.350907+00:00 heroku router - - at=info method=POST path="/parse/files/user-J5dPFK2F82-profile-picture.png" host=coralline.herokuapp.com request_id=d755e3e1-5dd2-4a43-9023-7a112db1f982 fwd="188.58.3.200" dyno=web.2 connect=0ms service=5953ms status=201 bytes=820 High Response Time
» 6 Apr 2016 15:30:05.190 332 <158>1 2016-04-06T12:30:04.767143+00:00 heroku router - - at=info method=POST path="/parse/files/user-Ri85PxoWvA-profile-picture.png" host=coralline.herokuapp.com request_id=26e2ad88-7648-4dce-8846-a7d21f020d8f fwd="178.240.192.212" dyno=web.2 connect=4ms service=28532ms status=201 bytes=820
MattiaConfalonieri commented 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...

flovilmart commented 8 years ago

Closing due to lack of activity, please reopen if the issue persist.

Don't forget to include your current: