Open vkurup opened 7 years ago
I wonder if salt-master can be configured to be smaller, since we really don't need it to scale to thousands of clients in this case.
Good thought. I couldn't find any really clear options on how to do that here: https://docs.saltstack.com/en/latest/ref/configuration/master.html
When I watched the process in real-time, the NPM process kept using an increasing amount of resident memory. It does the same thing on my laptop. There are some suggestions in this thread: https://github.com/npm/npm/issues/9884
One is to tell node to limit npm's memory usage (I copied the params verbatim from that thread, so don't know if they're optimal):
node --max_semi_space_size=1 --max_old_space_size=198 --max_executable_size=148 /usr/bin/npm install
This limited npm's memory usage to about 300M of resident memory (as opposed to about 1500M), but it slowed the install down by about 1 minute (from 1:40 to 2:40)
Attempting to deploy to a t2.micro instance fails because of out-of-memory errors during the
npm install
phase.EC2 instance type: t2.micro (1 GB RAM)
Setting up the master and the minion works, but 'fab staging deploy' fails:
It happens during the
npm install
, but salt is also taking up a lot of memory at the time:I'm not sure how best to approach this.