Merge pull request #8511 from Lakith-Rambukkanage/master-4.4.0-perf

Update perf results for 4.4.0
wso2 · Oct 28, 2024 · b34c2a3 · b34c2a3
2 parents 619d7ec + d099698
commit b34c2a3
Show file tree

Hide file tree

Showing 14 changed files with 8 additions and 8 deletions.
diff --git a/en/docs/assets/img/setup-and-install/performance-test-results/gc_0ms.png b/en/docs/assets/img/setup-and-install/performance-test-results/gc_0ms.png
diff --git a/en/docs/assets/img/setup-and-install/performance-test-results/graphql/avgt_0ms.png b/en/docs/assets/img/setup-and-install/performance-test-results/graphql/avgt_0ms.png
diff --git a/en/docs/assets/img/setup-and-install/performance-test-results/graphql/gc_0ms.png b/en/docs/assets/img/setup-and-install/performance-test-results/graphql/gc_0ms.png
diff --git a/...d-install/performance-test-results/graphql/response-time-summary-query1-0ms.png b/...d-install/performance-test-results/graphql/response-time-summary-query1-0ms.png
diff --git a/...ocs/assets/img/setup-and-install/performance-test-results/graphql/thrpt_0ms.png b/...ocs/assets/img/setup-and-install/performance-test-results/graphql/thrpt_0ms.png
diff --git a/...install/performance-test-results/lineplot-average-response-time-2g-1kib-0ms.png b/...install/performance-test-results/lineplot-average-response-time-2g-1kib-0ms.png
diff --git a/.../setup-and-install/performance-test-results/lineplot-throughput-2g-1kib-0ms.png b/.../setup-and-install/performance-test-results/lineplot-throughput-2g-1kib-0ms.png
diff --git a/...l/performance-test-results/lmplot-average-response-time-concurrent-users-2g.png b/...l/performance-test-results/lmplot-average-response-time-concurrent-users-2g.png
diff --git a/...stall/performance-test-results/lmplot-average-response-time-message-size-2g.png b/...stall/performance-test-results/lmplot-average-response-time-message-size-2g.png
diff --git a/...-and-install/performance-test-results/lmplot-throughput-concurrent-users-2g.png b/...-and-install/performance-test-results/lmplot-throughput-concurrent-users-2g.png
diff --git a/...etup-and-install/performance-test-results/lmplot-throughput-message-size-2g.png b/...etup-and-install/performance-test-results/lmplot-throughput-message-size-2g.png
diff --git a/...g/setup-and-install/performance-test-results/response_time_summary_1KiB_0ms.png b/...g/setup-and-install/performance-test-results/response_time_summary_1KiB_0ms.png
diff --git a/...-and-setup/setup/deployment-best-practices/performance-tests-results-graphql.md b/...-and-setup/setup/deployment-best-practices/performance-tests-results-graphql.md
@@ -62,7 +62,7 @@ Two key performance metrics were used to measure the performance of each test.
     <td>Apache JMeter Client</td>
     <td>c5.large</td>
     <td>2</td>
-    <td>4</td>
+    <td>2</td>
   </tr>
   <tr>
     <td>Apache JMeter Server 01</td>
@@ -86,7 +86,7 @@ Two key performance metrics were used to measure the performance of each test.
     <td>WSO2 API Manager</td>
     <td>c5.large</td>
     <td>2</td>
-    <td>4</td>
+    <td>2</td>
   </tr>
 </tbody>
 </table>
@@ -106,7 +106,7 @@ All scripts used to run the performance tests and analyze results are in the fol
 
 ## Results
 
-The complete results can be found [here](https://github.com/wso2/performance-apim/blob/performance-test-447-2024-03-12_05-54-54/performance/benchmarks/summary.md).
+The complete results can be found [here](https://github.com/wso2/performance-apim/blob/performance-test-470-2024-10-24_05-16-34/performance/benchmarks/summary.csv).
 
 The following graph depicts the throughput changes based on the number of concurrent users for different GraphQL queries.
 
@@ -132,7 +132,7 @@ The following graph depicts the average response time changes based on the numbe
 
 Let’s look at the 90th, 95th, and 99th response time percentiles. It is useful to measure the percentage of requests that exceeded the response time value for a given percentile. A percentile can be used to determine the percentage of requests completed below the particular response time value.
 
-For example, when there are 100 concurrent users, the 90th response time percentile for Query 1 is 76ms. This means that 10% of the requests have taken more than 76ms to respond. Similarly, the 99th response time percentile for Query 1 is 132ms, which means that 99% of the requests have been completed within 132ms.
+For example, when there are 100 concurrent users, the 90th response time percentile for Query 1 is 73ms. This means that 10% of the requests have taken more than 73ms to respond. Similarly, the 99th response time percentile for Query 1 is 130ms, which means that 99% of the requests have been completed within 130ms.
 
 The figure below represents the percentile values for Query 1.
 

diff --git a/.../install-and-setup/setup/deployment-best-practices/performance-tests-results.md b/.../install-and-setup/setup/deployment-best-practices/performance-tests-results.md
@@ -36,7 +36,7 @@ Two key performance metrics were used to measure the performance of each test.
     <td>Apache JMeter Client</td>
     <td>c5.large</td>
     <td>2</td>
-    <td>4</td>
+    <td>2</td>
   </tr>
   <tr>
     <td>Apache JMeter Server 01</td>
@@ -66,7 +66,7 @@ Two key performance metrics were used to measure the performance of each test.
     <td>WSO2 API Manager</td>
     <td>c5.large</td>
     <td>2</td>
-    <td>4</td>
+    <td>2</td>
   </tr>
 </tbody>
 </table>
@@ -86,7 +86,7 @@ All scripts used to run the performance tests and analyze results are in the fol
 
 ## Results
 
-Considering the fact that an average WSO2 API Manager user uses ~1KiB messages, the performance test highlights for that scenario are represented in the charts below. The complete results can be found [here](https://github.com/wso2/performance-apim/blob/performance-test-442-2024-03-08_12-05-14/performance/benchmarks/summary.md).
+Considering the fact that an average WSO2 API Manager user uses ~1KiB messages, the performance test highlights for that scenario are represented in the charts below. The complete results can be found [here](https://github.com/wso2/performance-apim/blob/performance-test-468-2024-10-23_15-25-13/performance/benchmarks/summary.md).
 
 The following graph depicts the throughput changes based on the number of concurrent users.
 
@@ -111,7 +111,7 @@ The following graph depicts the average response time changes based on the numbe
 
 Let’s look at the 90th, 95th, and 99th response time percentiles when the message size is 1KiB. It is useful to measure the percentage of requests that exceeded the response time value for a given percentile. A percentile can be used to determine the percentage of requests completed below the particular response time value.
 
-For example, when there are 100 concurrent users, the 90th response time percentile for Echo API is 48ms. This means that 10% of the requests have taken more than 48ms to respond. Similarly, the 99th response time percentile for Echo API is 88ms, which means that 99% of the requests have been completed within 88ms.
+For example, when there are 100 concurrent users, the 90th response time percentile for Echo API is 46ms. This means that 10% of the requests have taken more than 46ms to respond. Similarly, the 99th response time percentile for Echo API is 72ms, which means that 99% of the requests have been completed within 72ms.
 
 The figure below represents the percentile values for Echo API (PassThrough Scenario).