Hi David,
hard to tell, because it’s also depending on how your users are using the platform and what else is running on the Mattermost server. Is this a single-server deployment and if so, what components are running on this server?
- Reverse Proxy?
- Mattermost Application server?
- S3 Storage Server?
- Database Server?
- Elasticsearch Server?
- etc.
The mattermost process on my server is using ~1GB of RAM and is not very CPU hungry, but the database and elastichsearch services are, so the sizing for system might differ depending on the requirements.
If it’s a virtual infrastructure which supports hot-adding resources, then you can start with a smaller deployment and grow online as the need arises, whereas a downsizing always comes with a reboot and therefore a short downtime.
Calls, f.ex., start a separate process per CPU dynamically, so the more CPUs you have, the better your calling performance will be when you have lots of calls. If there are just a few calls, it will not matter.
The reference architectures online are a bit oversized for your requirements, I think, so if you can scale fast, I’d say give it a try with your current resources, maybe add 2 cpus and 2gb of ram, just to be on the safe side.