From 1dc3b08ba86fe64c5f5832c19322bc76f662b0d3 Mon Sep 17 00:00:00 2001 From: Kamesh Akella Date: Thu, 24 Oct 2024 15:55:51 -0400 Subject: [PATCH] update the sizing guide with the correct instance type Closes #34315 Signed-off-by: Kamesh Akella --- .../high-availability/concepts-memory-and-cpu-sizing.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/high-availability/concepts-memory-and-cpu-sizing.adoc b/docs/guides/high-availability/concepts-memory-and-cpu-sizing.adoc index ff302b6d98b..1dab02bf32f 100644 --- a/docs/guides/high-availability/concepts-memory-and-cpu-sizing.adoc +++ b/docs/guides/high-availability/concepts-memory-and-cpu-sizing.adoc @@ -127,7 +127,7 @@ The benefit of this setup is that the number of Pods does not need to scale duri The following setup was used to retrieve the settings above to run tests of about 10 minutes for different scenarios: * OpenShift 4.16.x deployed on AWS via ROSA. -* Machinepool with `m5.4xlarge` instances. +* Machinepool with `m5.2xlarge` instances. * {project_name} deployed with the Operator and 3 pods in a high-availability setup with two sites in active/active mode. * OpenShift's reverse proxy running in passthrough mode were the TLS connection of the client is terminated at the Pod. * Database Amazon Aurora PostgreSQL in a multi-AZ setup.