I’m working on a meteor app I inherited from the previous dev, so I’m not quite an expert on meteor.
I’ve got the app running on heroku, with hobby dynos. There’s 2 set up, one for staging and another for production. The staging one has a similar database to the one in production - I copied it over not too long ago to do some testing with real data. The memory usage of the staging app is around 80-130mb. It can go up a bit (~20mb) when you’re messing around on the app.
The problem is with the production version. It sits around ~650mb, minimum 550mb, with spikes over 1gb (when according to heroku, there were 5 requests/min).
I can recreate this issue on my local dev env as well. When running the app with
meteor, it uses just under 100mb (as told by
ps aux). When running
meteor run --production, it hits over 500mb, just like on heroku.
There appears to be something that’s causing the app to use a ton of memory whenever it’s in “production mode”. Can anyone tell me where I should start looking to track down this issue, or if you’ve had the same issue, how you’ve fixed it?
Thanks in advance!