As for our current system resources, we first used Countly in production on a standard Linode with 2GB of RAM, eventually it completely crashed.
We upgraded the linode to 4GB of RAM and 2 CPU, eventually that crashed too.
So, we upgraded the linode to 8GB of RAM and 4 CPU. It did not crash, but we would still get alerts from Linode about CPU usage and inbound traffic rates.
That's when I searched the docs and saw that
Running your Countly instance on a dedicated or barebone server greatly increases network throughput and CPU performance.
So, now we run this:
- 8GB of RAM
- 4 CPU
- 160GB of storage
- On a dedicated CPU
No crashes to report yet, but I got mail from Linode informing me that the CPU was being used heavily and inbound traffic rates were high ("averaging 14.53 Mb/s for the last 2 hours").
Being used to PAAS like Heroku or even easier hosting with services like Netlify, I feel like I'm just taking shots in the dark with this server management thing...
End of the novel