Details
-
New Feature
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Won't Do
-
None
-
-
Core: Platform
Description
In order to reproduce and debug performance issues, it would be desirable to have a testbed deployed and loaded in local development environment. The testbed should provide ability to perform load tests against FOLIO ecosystem as a whole and isolated individual modules or subset of modules. Testing against FOLIO as a whole will provide overhead testing metrics for filtering and routing through Okapi and ensure it is constant for all test plans. Testing modules in isolation will enable isolation and debugging for quick turn around for tuning. To be consistent with Jenkins performance testing and to afford reusability of tests, Apache JMeter should be used. The current suite of test plans can be found https://github.com/folio-org/folio-perf-test. Therefore, analysis of this repo and how it works will be a prerequisite. This repo contains references to load data hosted on AWS. This may be reusable, but should ensure test data is of most recent schema. In addition, a documented baseline with environment specifications and persistent and concurrent load metrics should be produced.
TestRail: Results
Attachments
Issue Links
- relates to
-
MODINVSTOR-237 Performance: GET 200 - Get updated mod-inventory/item by using modInventoryItemId
-
- Closed
-
-
MODINVSTOR-238 Performance: GET 200 - instance-storage by ID from POST above
-
- Closed
-