We have been using the m5 instance type to run our mongodb replicaset. We are in a position to be able to change this now.
I’m curious if percona reccomends a particular instnace type to run mongodb and the reasons for it.
I came across this video today which looks interesting - https://www.youtube.com/watch?v=ZZ2tx8iL3P4
He is using I3en instance type - Amazon EC2 I3en Instances - dense SSD storage instances
Does anyone have any thoughts?
Instance types, CPU and RAM configuration are all very specific to your workloads.
I can just provide some regular guidance:
- Storing indexes and data in RAM would definately give you some performance boost for almost any database. With this in mind look at the instances with higher memory - R family on AWS is a usual choice.
- Keeping all the data in RAM is not an option for decent dataset sizes. That is why fast storage is important. That is where you have various options on AWS:
- Use fast disks (like IO2). They will get expensive very quickly, as you would leverage provisioned IOPs.
- Use built-in NVME SSDs. There are multiple instance types that provide that on AWS. Look at Storage Optimized instances or instances with “D” prefix (ex. r6d).
Also have a look at the following blog posts:
- Percona Operator for MongoDB with Local Storage and OpenEBS
- Reduce Your Cloud Costs With Percona Kubernetes Operators
If you need deeper assessment of your environment - please reach out to our teams: Sales & General Inquiries - Percona