Details
-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
-
Not defined
Description
We should have load testing against our API to make sure performance is still acceptable. We need to define what acceptable means. This could potentially be run as part of a nightly job.
There might exist a tool that makes this easy to configure. One option that we could consider would be to use https://github.com/jmeter-maven-plugin/jmeter-maven-plugin, which allows JMeter tests to be executed as part of our build. However, this would still require the tests to be defined up front using the JMeter UI.
In addition to general testing of API performance under load, we should make sure that load on the ingestion API doesn't have unacceptable impact on the rest of the API. The amount of requests that the ingestion API can serve is configurable.
ATs:
- We have a regular load/performance test of our API by making x number of requests to our more commonly used endpoints from a large (and preferably scaling up number of simulated users)
- We have a test for API performance while the ingestion API is under heavy load