Flavors and performance classes of MongoDB Flex
Currently we offer six different performance classes.
If your performance class is too small, you can upgrade it to a bigger one.
To upgrade it, please open a service request at the Help Center.
Performance classes
Section titled “Performance classes”| Description | ID | Max. IOPS | Max. throughput (MB/s) |
|---|---|---|---|
| Performance class 2 | premium-perf2-mongodb | 1000 | 100 |
| Performance class 4 | premium-perf4-mongodb | 2000 | 150 |
| Performance class 6 | premium-perf6-mongodb | 5000 | 200 |
| Performance class 8 | premium-perf8-mongodb | 10000 | 250 |
| Performance class 10 | premium-perf10-mongodb | 15000 | 300 |
| Performance class 12 | premium-perf12-mongodb | 20000 | 350 |
Currently, we offer three types of instances. For each type there are different flavors available.
If your flavor is too small, you can upgrade it to a bigger one. Currently, it is only possible to upgrade from a replica set flavor to another replica set flavor, and from a single instance flavor to another single instance flavor. It is not possible to upgrade from a single instance flavor to a replica set flavor.
MongoDB recommends the use of at least 4 GB of RAM in its Deployment prerequisites. A flavor with less than 4 GB RAM may not provide the required stability for a production system.
Single (not recommended for production)
Section titled “Single (not recommended for production)”| Description | ID | CPU | RAM (GB) |
|---|---|---|---|
| Tiny, Compute optimized | 1.2 | 1 | 2 |
| Tiny, Database optimized | 1.4 | 1 | 4 |
A single node is not recommended for production environments, because it uses only one availability zone and has no replica. If this one zone is disrupted or fails temporarily, your production environment is also offline.
Replica set
Section titled “Replica set”| Description | ID | CPU | RAM (GB) |
|---|---|---|---|
| Tiny, Compute optimized | 1.2 | 1 | 2 |
| Tiny, Database optimized | 1.4 | 1 | 4 |
| Tiny, Memory optimized | 1.8 | 1 | 8 |
| Small, Compute optimized | 2.4 | 2 | 4 |
| Small, Database optimized | 2.8 | 2 | 8 |
| Small, Memory optimized | 2.16 | 2 | 16 |
| Medium, Compute optimized | 4.8 | 4 | 8 |
| Medium, Database optimized | 4.16 | 4 | 16 |
| Medium, Memory optimized | 4.32 | 4 | 32 |
| Large, Compute optimized | 8.16 | 8 | 16 |
| Large, Database optimized | 8.32 | 8 | 32 |
| Large, Memory optimized | 8.64 | 8 | 64 |
| X-Large, Compute optimized | 16.32 | 16 | 32 |
| X-Large, Database optimized | 16.64 | 16 | 64 |
Sharded cluster
Section titled “Sharded cluster”| Description | ID | CPU | RAM (GB) |
|---|---|---|---|
| Medium, Memory optimized | 4.32 | 4 | 32 |
| Large, Database optimized | 8.32 | 8 | 32 |
| Large, Memory optimized | 8.64 | 8 | 64 |
| X-Large, Compute optimized | 16.32 | 16 | 32 |
| X-Large, Database optimized | 16.64 | 16 | 64 |