Memory usage increased ~100% after updating from Parse server 2.2.25 to 2.6.3

[saulogt]

I updated to the newest version of parse server (2.2.25 -> 2.6.3) looking for bugfixes and possibly performance improvements. However, the memory usage increased about 100% from ~200MB to ~400MB and it seems to not decrease.

The current load is 50 requests per second. The response time and cpu load haven't changed.

I expected to use the same amount of memory as before and even downgrade the dyno if it was more stable. Now I'm concerned about the peaks of load.

Environment Setup

• Server

  • parse-server version: 2.6.3
  • NodeJS: 8.6.0
  • Hardware: Heroku Standard 2X

• Database

  • MongoDB version: 3.0.12
  • Storage engine: MMAPv1
  • Hardware: Dedicated Cluster - mLab

[montymxb]

@saulogt What version of node are you using to run this?

[saulogt]

@montymxb it is nodejs 8.6.0. I just added this information to the original comment

[agwl-saurabh]

I am using below on AWS. with no issue. might be Node.js issue not 100% but as suggested by node team always use most used version not latest.
Node.js 6.11.3
Parse Server 2.6.1
MongoRock 3.4

My personal experience:- I always have issue with latest version. so i normally use old version of any product Like i am using Node and parse .
Now updating to mongoDBreplica set but having issue with mongo. if you have any info about mongoDB please response to my below issue. Not sure if 3.2 mongo is better

#4236

[flovilmart]

That’s a good advice, we see various differences on node versions, from promise performance, to memory usage, I’m not sure where it comes from, but there’s no real need to ride on the latest version.

[flovilmart]

@saulogt did you try the revolution proposed in #4235, closing in favour of #4247

[saulogt]

@flovilmart It makes sense. I'm updating mongoDb to 2.4 first.
I'm gonna test this soon and post here the results

[flovilmart]

Try out with the enableSingleSchemaCache option, this should greatly improve your memory usage

[n-so]

@flovilmart
I have the same issue when upgrading to parse server 3.x
Is there any other solution except from enableSingleSchemaCache:true?

[mtrezza]

@n-so can you provide more details about the environment you are running and what exactly your issue is?

[n-so]

@mtrezza Thanks for your quick replay .
I posted an issue #6061
thanks.