Problem statement:

As an ACM Observability User I am able to determine the exact memory and CPU requirement needed for the default Multi-cluster Observability Operator needs to schedule query, qfe and store-gw pods for a given max-cardinality per query

As an ACM Observability User I have confidence in the base performance of a default installation of ACM Multi-cluster Observability Operator component in my Hub Cluster with respect to max series/chunks per-query and max query concurrency per-querier

OCP Example https://docs.openshift.com/container-platform/4.13/scalability_and_performance/planning-your-environment-according-to-object-maximums.html

Mimir example https://grafana.com/docs/mimir/latest/manage/run-production-environment/planning-capacity/#:~:text=Estimated%20required%20CPU%2C%20memory%2C%20and,every%20300%2C000%20series%20in%20memory