Reduce footprint of a Meteor application

I am hosting a small Meteor demo app where I am running my own DDP server. I’ve noticed that the memory footprint of meteor is quite large, about 70% of my 512MB DO droplet. For comparison, my own server process that is running all of the app logic takes only about 0.7%.

I don’t need mongodb, node/JS or Meteor’s DDP server on the backend for my application, and I am looking for options to reduce footprint of my Meteor installation. I would like the client to remain a native Meteor application- just one that connects to a different DDP source.

Has anyone attempted reducing footprint before?

2 Likes