IN PROGRESS
...
Average response time per request 0.874 s.
...
.
...
Test flow
Test consist of few calls:
...
Duration - 4 hr 57 min
Records transferred . - 4770043 (should be 8415303)
Records harvested - 20618 X 100 = 2 061 800.
Total Underlying SRS records: 1,212,039
...
- While data transferring process is going on the background DB CPU usage has reached 70%-75%.
- Data transferring process has failed in 10 minutes and transfer only 4770043 from 8M records.
- Harvesting itself consumes 15% DB CPU.
Test 2
Duration 4 hr 25 min
Records transferred . - 3815867 (should be 8415303)
Records harvested - 22305 X 100 = 2 230 500.
Total Underlying SRS records: 1,212,039
...
We can see here that memory usage is stable and none of containers didn't fail.
Notable observations:
- Unstable parts of first tests was made by data set:
- instances didn't have underlying records and this causes multiple repeating calls from mod-edge-oai-pmh to mod-oai-pmh.
- this leads to end client to wait until oai-pmh will find records with underlying records. And often client fail with 504 getaway timeout (load balancer timeout 400 seconds).
- Timeouts in DB fixed with changing of dataset to "bugfest" like.
- Jira ticket created to handle client waits: MODOAIPMH-383