Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Status Submitted
Categories Atlas
Created by Guest
Created on May 5, 2020

M30 Cluster Tier option with 4 CPUs

There is a gap in the Cluster Tiers for clients that have high CPU requirements but lower disk space requirements. We run on a M30 Cluster where we max out the CPU when running aggregations, we use little of the available disk and do not want to move to a M40.
  • Attach files
  • Guest
    Jul 14, 2021
    I would like this. Since we use application level to connect, we don't specifically connect to shards, we connect straight to the cluster. Which usually falls on the primary. We would love a middle option with 4CPU cores and everything else remains the same. just for extra aggregations of reads and writes.
  • Guest
    May 7, 2020
    Jaco, would you mind exploring whether you can optimize your cost/performance by spreading the aggregation workload across replicas? That might be a better path forward here. -Andrew
  • Guest
    May 6, 2020
    Hi Andrew, we use the the primary only.
  • Guest
    May 6, 2020
    Hi Jaco, One thing I do want to confirm -- are you leveraging secondaries to round out your aggregation read load, or might you be pushing aggregations exclusively to your primary? Cheers -Andrew