ObjectRocket’s Mongo plans offer structured pairing of storage and memory allocations for a single Mongo instance (Sharded or Replica Set). Below are a set of tables that show storage and memory per shard or replica set associated for each of our Mongo Plans.
MongoDB Storage and Memory Options¶
Sharded and Replica Sets
All Storage Engines
Microsoft Azure Regions¶
Replica Sets Only
mmap Storage Engine
WiredTiger Storage Engine
Plan Size Storage Limits¶
As your Mongo data footprint grows, we offer several tools to help manage the size and scale of your growth – we have experts standing by to help walk you through options. Once your data reaches storage capacity for that instance, we will reach out (via open ticket) with suggestions and options. If you just want to size-up your instance to the next plan, you don’t have to do anything – we will just invoice accordingly. If you need advice, just respond to the ticket with your questions.
Plan Size Memory Limits¶
Some applications can have certain memory requirements in their shard or replica set. If this is a requirement for your workload, you will need to select a plan based upon that requirement even if you don’t require that much storage. For example, if your Mongo instance fits within a 20G instance but you require 5G of RAM, you should select the 50G instance that comes with 5G of RAM.