-
-
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
Json parser seems to be eating up a lot of response time #2711
Comments
The json parser is the default json parser provided alongside express.js not sure what should be done here |
@flovilmart yea, im not sure what to say, just seeing a pattern on some of the calls that seems to be processing a lot in the json parser now.. again not sure if this had been happening but I like to keep an eye out on things that take longer than x ms to execute.. hmmm |
@gateway I am facing similar issue. Most of the time, everything works fine. Some time I see delayed queries and time reaches around 50s. By checking transaction trace on NewRelic, I found out that Middleware:jsonParser is taking much of the time. |
Following, simillar issue. |
Please read the following instructions carefully.
Check out #1271 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!
Many members of the community use Stack Overflow and Server Fault to ask questions.
Read through the existing questions or ask your own!
For database migration help, please file a bug report at https://parse.com/help#report
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
Issue Description
Been keeping an eye out on high response times with our app in New Relic... One that stuck out was a simple class to get places that are disabled.
Looking at the transaction traces it spent most of its time in the json parser.
This seems to be happening across various classes, now I did update from 2.2.17 to 2.2.19 just fyi but not sure if thats the cause.
Steps to reproduce
Not sure really how to repo this, this was just based upon what we are seeing now in New Relic
Environment Setup
Logs/Trace
None that could be found.
The text was updated successfully, but these errors were encountered: