I remember someone who was running two of the testnets on a single machine, just using two sets of executables, separate folder, etc. Saves on hardware and both the testnets aren’t resource hungry.
I’ve got both preview and pre-prod setup and can run them separately, but I get an error when running both that the socket address is in use. Was there something special I need to do two run both in terms of the host address? Or something like that?
Well, I was running 8.1.2 on preview, so yeah, I should just upgrade that too, but I thought I had to run two separate executables. I’ll read through your stuff a bit more and see where I’m going wrong.
I am running both instances using separate ports, but maybe I’ve missed one of the variables in the env file.
Well, you run them separately, but they need to be installed only once. To do an ls of one directory in one terminal and an ls of another directory in another terminal, you also do not need to have two separate installations of ls.
If you regularly want to upgrade earlier on one network than on the other – to first test it on Preview, for example – a setup with two separate cardano-node executables might make sense, though.
If you used the CNTools way of doing things that’s quite possible. There are a lot of things in those. Since you say in the original post that it complains about “socket”, not port, it’s probably that.
Only occasionally running my nodes on my normal desktop when I want to do or test something: The two testnets need much less resources than the mainnet. 32 GiB work with running Mainnet, Preprod, and Preview all at the same time and still normally working alongside that.
Thanks for the info! For Mainnet it used to take something along the lines of ~13GB of memory at one point (this could have changed though: to less with better memory management; or to more with a bigger utxo size). But how much do Preview and Preprod take these days? They are periodically reset as well, right, so they wont grow indefinitely?
(Preview has jumped to 2.10 GiB a few moments after taking that screenshot. After that all three have stayed at those numbers. So, I guess this should give a pretty accurate impression of the order of magnitude today.)
I got it working, I had to change the prometheus port on the second instance, along with the EKG port. Not sure why mine is working different to what you have set up @HeptaSean but at least it is working now with two instances (and two different versions, one for preview and one for preprod).