-
Type: Task
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Performance
-
Epic Link:
Context
We want to be able to run a list of Gatling tests to validate the performance of the repository under a typical workload.
Compare to the existing default Gatling tests, the main difference is that:
- we will leverage the specific content model we defined for the benchmark
- we want to focus on what could go wrong at large scale
The very point of these tests will be to allow us to determine at what volume a given infrastructure collapses so that we can scale out before the next step in the volumization of the repository.
Typical Tests we want to do
- queries
- fetch all statements for a given account
- fetch all statements for a given customer
- create a new Document via REST API
- XXX - doc type and blob to be defined
- update a Document via REST API
- XXX - doc type and blob to be defined
- daily-import
- import doc via REST API or CSV
- XXX - doc type and blob to be defined
- links to