-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Workload Resilience
-
Workload Resilience 2026-05-11, Workload Resilience 2026-05-25, Workload Resilience 2026-06-08, Workload Resilience 2026-06-22, Workload Resilience 2026-07-06, Workload Resilience 2026-07-20, Workload Resilience 2026-08-03, Workload Resilience 2026-08-17, Workload Resilience 2026-08-31
-
None
-
None
-
None
-
None
-
None
-
None
-
None
this is the parent ticket for multi-tenancy POC work to showcase our solution works as expected in the targeting customer workload scenarios.
- workload running in M20 and M50 variants, Operation spike, Inefficient query (maybe just collection scans). More specs in https://docs.google.com/document/d/12cAXuxEfgSFUjfBY29X2QUBpdaDepZ63M0gnA3NVG0Q/edit?tab=t.0#heading=h.ip2vinz5ha5p
- Try server side POC, https://github.com/10gen/mongo/compare/mbroadst/multi-tenant-poc-codex the ingress per tenant rate limiter poc
- the acceptance criteria would be good put of each tenant, with the rate limiter, the active tenant good put drop drastically comparing to without the solution so that system resources can be shared with other tenants.