Json parser seems to be eating up a lot of response time #2711

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!

• Stack Overflow: http://stackoverflow.com/questions/tagged/parse.com
• Server Fault: https://serverfault.com/tags/parse

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!

• [x ] You've met the prerequisites: https://github.com/ParsePlatform/parse-server/wiki/Parse-Server-Guide#prerequisites.
• [ x] You're running the latest version of Parse Server: https://github.com/ParsePlatform/parse-server/releases
• [ x] You've searched through existing issues: https://github.com/ParsePlatform/Parse-Server/issues?utf8=%E2%9C%93&q=is%3Aissue Chances are that your issue has been reported or resolved before.
• [x ] You have filled out every section below. Issues without sufficient information are more likely to be closed.

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

• Server
  • parse-server version (Be specific! Don't say 'latest'.) : 2.2.19
  • Operating System: Unknown
  • Hardware: 2 Standard XL
  • Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): Heroku
• Database
  • MongoDB version: 3.2.x
  • Storage engine: WiredTiger
  • Hardware: M1 Cluster
  • Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): Mlab

Logs/Trace

None that could be found.