DOC-1521 Update memory requirements in sizing (#1223)

Co-authored-by: Paulo Borges <[email protected]>

Author: micheleRP

modules/deploy/pages/deployment-option/self-hosted/manual/sizing.adoc

@@ -14,12 +14,24 @@ Throughput and retention requirements can cause bottlenecks in the system. On an
 
 In general, choose the number of nodes based on the following criteria, and add nodes for fault tolerance. This ensures that the system can operate with full throughput in a degraded state.
 
-* Total network bandwidth must account for maximum simultaneous writes and reads, multiplied by the replication factor.
-* Have a minimum of 2 GB memory for each core, but more memory is better.
-* Have a minimum of 4 MB of memory for each topic partition replica. You can enforce this requirement in the tunable xref:reference:tunable-properties.adoc#topic_memory_per_partition[`topic_memory_per_partition` property].
-* Use Tiered Storage to unify historical and real-time data.
-* For AWS, test with either i3en, i4i, or is4gen; for GCP, test with n2-standard (GCP); and for Azure, test with lsv2. In general, choose instance types that prioritize storage and network performance.
-* Run hardware and Redpanda benchmark tests for a performance baseline.
+* **Network bandwidth**: Total bandwidth must account for maximum simultaneous writes and reads, multiplied by the replication factor.
+* **Memory per core**: Allocate a minimum of 2 GB memory for each CPU core. Additional memory could improve performance.
+* **Memory per partition**: Allocate a minimum of 2 MB of memory for each topic partition replica. 
++
+For example: If you have 10,000 total partitions with a replication factor of 3, you need at least 60 GB of memory across all brokers:
++
+10,000 partitions × 3 replicas × 2 MB = 60,000 MB (60 GB) 
++
+If these partitions are evenly distributed across three brokers, each broker needs at least 20 GB of memory.
+* **Storage strategy**: Use Tiered Storage to unify historical and real-time data cost-effectively.
+* **Performance testing**: Run hardware and Redpanda benchmark tests to establish a performance baseline. Choose instance types that prioritize storage and network performance:
++
+--
+* **AWS**: Test with i3en (NVMe SSD), i4i (NVMe), or is4gen (Intel-based NVMe) instances, or other NVMe-backed types
+* **Azure**: Test with Lsv2-series instances (high I/O performance) or other high-performance storage types
+* **GCP**: Test with n2-standard instances with local SSD or other high-performance local storage types
+--
+
 
 == Sizing considerations