Custos JMeter Testing
To learn and understand the performance of Custos, I started by requesting the tenant from https://dev.portal.usecustos.org/. Using Custos python SDK and set up custos clients.
The following are some scenarios I would like to share:
- Create Group
Performed load testing the create group endpoint of custos using three different loads -
- 200 concurrent requests (threads)
Graph results for 200 connection requests –
The average response time was around 51.9ms for each request with an overall throughput of 118.94 requests/min.
- 400 concurrent requests (threads)
Graph results for 400 connection requests –
The average response time was around 55.04ms for each request with an overall throughput of 245.50 requests/min.
- 600 concurrent requests (threads)
Graph results for 600 connection requests –
The average response time was around 74.33ms for each request with an overall throughput of 276.47 requests/min.
- Register User
Performed load testing the create group endpoint of custos using three different loads -
- 200 concurrent requests (threads)
Graph results for 200 connection requests –
The average response time was around 41.08ms for each request with an overall throughput of 136.49 requests/min.
- 400 concurrent requests (threads)
Graph results for 400 connection requests –
The average response time was around 68.55ms for each request with an overall throughput of 178.72 requests/min.
- 600 concurrent requests (threads)
Graph results for 600 connection requests –
The average response time was around 75.62ms for each request with an overall throughput of 270.97 requests/min.
The different number of threads shows how response time and overall throughput is getting affected due to load. But can handle min 600 requests and can extend beyond but response time will be compromised.