Jira Legacy

Test Summary

All tests shows stable work, and pass whit 0% of errors. However high CPU utilisation from RDS side may cause an issues with bigger loads in future.

The more load causes more CPU usage on database and it leads to higher average response times.

There is two query types that causes most of CPU usage, it's count.estimate and select jsonb,id from circulation_storage.requests.

Results

Requests	Total	OK	Min	50th pct	75th pct	95th pct	99th pct	Max
Requests	Total	OK	Response times (seconds)
GET_addresstypes	4141	4141	0.013	0.032	0.040	0.072	0.106	0.418
GET_cancellation-reason-storage/cancellation-reasons	4141	4141	0.014	0.031	0.038	0.059	0.093	0.762
GET_circulation/pick-slips/servicePointId	4141	4141	0.028	0.089	0.105	0.159	0.246	0.489
GET_circulation/requests	16560	16560	0.079	0.256	0.534	0.876	1.039	2.054
GET_circulation/requests-reports/hold-shelf-clearance/servicePointId	8282	8282	0.026	0.066	0.080	0.122	0.185	0.800
GET_groups	4141	4141	0.013	0.031	0.039	0.068	0.104	0.778
GET_service-points	4141	4141	0.015	0.031	0.038	0.061	0.106	0.373
GET_staff-slips-storage/staff-slips	4141	4141	0.014	0.031	0.038	0.062	0.114	0.766
GET_tags	4141	4141	0.014	0.031	0.038	0.060	0.098	0.375
POST_authn/login	1	1	0.445	0.445	0.445	0.445	0.445	0.445
Search request by open status transaction workflow	4137	4137	1.294	1.893	2.017	2.417	2.825	3.898

...