You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The document shows how the Throughput changes for different number of concurrent users, etc.
In my case, I want to know 「Throughput changes for different number of concurrent users」over 2,000 concurrent users. (I want to throughput changes when 20,000 conurrent users.)
Description:
Hi, wso2 teams.
Thank you for provide wso2 api manager.
To find out which API manager(ex. Kong, Amazon API Gateway, etc.) is better, I'm trying to comparing performance of API manager.
So, I found the following article.
https://docs.wso2.com/display/AM260/WSO2+API-M+Performance+and+Capacity+Planning
The document shows how the Throughput changes for different number of concurrent users, etc.
In my case, I want to know 「Throughput changes for different number of concurrent users」over 2,000 concurrent users. (I want to throughput changes when 20,000 conurrent users.)
So, in order to reproduce the charts, git clone https://github.com/wso2/performance-common and https://github.com/wso2/performance-apim
But I cant' figure out how to run performance tests and get results in spite of read README of performance-common and performance-apim.
Could you teach me how to run the performance tests and get results on environment described in https://docs.wso2.com/display/AM260/WSO2+API-M+Performance+and+Capacity+Planning ( WSO2 API Manager All-in-one Deployment )?
I found branch https://github.com/wso2/performance-common/tree/performance-test-21-2019-05-30_09-35-11 and I confirmed the results are stored in performance/benchmarks directory.
benchmark results are stored by wso2-product-performance-bot user, so I think you run performance script automatically (e.g. using Jenkins?)?
Suggested Labels:
reproduce,test
Suggested Assignees:
Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:
The text was updated successfully, but these errors were encountered: