Update cache-planning-faq.yml

Author: MSFTeegarden

articles/azure-cache-for-redis/cache-planning-faq.yml

@@ -17,41 +17,7 @@ sections:
       - question: |
           Azure Cache for Redis performance
         answer: |
-          The following tables show the maximum throughput values that were observed while testing various sizes of Standard, Premium, Enterprise, and Enterprise Flash caches. We used `redis-benchmark.exe` from an IaaS VM against the Azure Cache for Redis endpoint. For TLS throughput, redis-benchmark is used with *stunnel* to connect to the Azure Cache for Redis endpoint.
-          
-          >[!IMPORTANT] 
-          >These values aren't guaranteed and there's no SLA for these numbers. We strongly recommend that you should [perform your own performance testing](cache-best-practices-performance.md) to determine the right cache size for your application.
-          >These numbers might change as we post newer results periodically.
-          >
-          
-          From this table, we can draw the following conclusions:
-          
-          * Throughput numbers are for GETS.
-          * Throughput for the caches that are the same size is higher in the Premium tier as compared to the Standard tier. For example, with a 6 GB Cache, throughput of P1 is 180,000 requests per second (RPS) as compared to 100,000 RPS for C3.
-          * With Redis clustering, throughput increases linearly as you increase the number of shards (nodes) in the cluster. For example, if you create a P4 cluster of 10 shards, then the available throughput is 400,000 * 10 = 4 million RPS.
-          * Throughput for bigger key sizes is higher in the Premium tier as compared to the Standard Tier.
-          
-          | Pricing tier | Size | CPU cores | Available bandwidth | 1-KB value size | 1-KB value size |
-          | --- | --- | --- | --- | --- | --- |
-          | **Standard cache sizes** | | |**Megabits per sec (Mb/s) / Megabytes per sec (MB/s)** |**GET Requests per second Non-SSL** |**GET Requests per second SSL** |
-          | C0 | 250 MB | Shared | 100 / 12.5  |  15,000 |   7,500 |
-          | C1 |   1 GB | 1      | 500 / 62.5  |  38,000 |  20,720 |
-          | C2 | 2.5 GB | 2      | 500 / 62.5  |  41,000 |  37,000 |
-          | C3 |   6 GB | 4      | 1000 / 125  | 100,000 |  90,000 |
-          | C4 |  13 GB | 2      | 500 / 62.5  |  60,000 |  55,000 |
-          | C5 |  26 GB | 4      | 1,000 / 125 | 102,000 |  93,000 |
-          | C6 |  53 GB | 8      | 2,000 / 250 | 126,000 | 120,000 |
-          | **Premium cache sizes** | |**CPU cores per shard** | **Megabits per sec (Mb/s) / Megabytes per sec (MB/s)** |**GET Requests per second Non-SSL, per shard** |**GET Requests per second SSL, per shard** |
-          | P1 |   6 GB |  2 | 1,500 / 187.5 | 180,000 | 172,000 |
-          | P2 |  13 GB |  4 | 3,000 / 375   | 350,000 | 341,000 |
-          | P3 |  26 GB |  4 | 3,000 / 375   | 350,000 | 341,000 |
-          | P4 |  53 GB |  8 | 6,000 / 750   | 400,000 | 373,000 |
-          | P5 | 120 GB | 32 | 6,000 / 750   | 400,000 | 373,000 |
-          
-          > [!Important]
-          > P5 instances in the China East and China North regions use 20 cores, not 32 cores. 
-          
-          For instructions on setting up stunnel or downloading the Redis tools such as `redis-benchmark.exe`, see [How can I run Redis commands?](cache-development-faq.yml#how-can-i-run-redis-commands-).
+          For guidance on how to benchmark the performance of your Azure Cache for Redis instance and for sample benchmarking numbers, please see the [Performance testing](cache-best-practices-performance.md#example-performance-benchmark-data) page.
           
       - question: |
           In what region should I locate my cache?