mempool/production/mempool-start-all

#!/usr/bin/env zsh
export NVM_DIR="$HOME/.nvm"
source "$NVM_DIR/nvm.sh"

for site in mainnet mainnet-lightning testnet testnet-lightning signet signet-lightning bisq liquid liquidtestnet;do
    cd "${HOME}/${site}/backend/" && \
    screen -dmS "${site}" sh -c 'while true;do npm run start-production;sleep 1;done'
done
Change shebang in scripts to be universal for prod install 2022-07-06 12:11:13 +02:00			`#!/usr/bin/env zsh`
Update production scripts to install/load NodeJS/npm using nvm 2020-09-18 14:53:58 +02:00			`export NVM_DIR="$HOME/.nvm"`
			`source "$NVM_DIR/nvm.sh"`
Refactor nginx.conf and other ops scripts for lightning 2022-07-06 14:01:18 +02:00
			`for site in mainnet mainnet-lightning testnet testnet-lightning signet signet-lightning bisq liquid liquidtestnet;do`
Don't start production instances if backend folder doesn't exist 2021-02-24 18:38:38 +01:00			`cd "${HOME}/${site}/backend/" && \`
Reduce backend heap size setting to 2G since cache memory usage was optimized (#345) On powerful servers, nodejs automatically sets the limit at 4GB ``` % node -e 'console.log(`node heap limit = ${require("v8").getHeapStatistics().heap_size_limit / (1024 * 1024)} Mb`)' node heap limit = 4144 Mb ``` On a Raspberry Pi with 8GB RAM, nodejs automatically sets the limit at 1GB ``` % node -e 'console.log(`node heap limit = ${require("v8").getHeapStatistics().heap_size_limit / (1024 * 1024)} Mb`)' node heap limit = 1048 Mb ``` On a Raspberry Pi with 4GB RAM, nodejs automatically sets the limit at 740MB ``` % node -e 'console.log(`node heap limit = ${require("v8").getHeapStatistics().heap_size_limit / (1024 * 1024)} Mb`)' node heap limit = 739.4694900512695 Mb ``` After testing with manually setting the limit to 768MB, mempool starts up fine, but crashes when saving the cache when the mempool is quite large (over 400MB with custom bitcoin.conf setting). So it's probably safe to reduce the 4GB limit setting to 2GB for all devices and and just use the automatically set values, now that the backend's disk cache memory usage was recently optimized. However, a new npm script for `npm run start-production` will be added so we can keep our production mempool.space servers running with a very large bitcoin.conf mempool 2021-02-14 16:25:29 +01:00			`screen -dmS "${site}" sh -c 'while true;do npm run start-production;sleep 1;done'`
Update misc files used for mempool.space production website 2020-05-25 11:42:00 +02:00			`done`