Performance improvements in 3.6

https://openlmis.atlassian.net/browse/OLMIS-6077

Requisition initiate screen

• The time to initiate the requisition was reduced by the time required to fetch requisition (depends on the size of requisition)

https://openlmis.atlassian.net/browse/OLMIS-6074 and https://openlmis.atlassian.net/browse/OLMIS-6073

Logging in

• This was a regression, so no performance boost compared to v3.5

https://openlmis.atlassian.net/browse/OLMIS-5000

Convert requisition to order screen

• Execution time for an endpoint was reduced from 19s to 10s (measured with automated perf tests)

https://openlmis.atlassian.net/browse/OLMIS-4531

Requisition initiate (+ other POST/PUT requests)

• The initiate requisition endpoint response is now compressed, which will be especially noticeable on slow connections

https://openlmis.atlassian.net/browse/OLMIS-4291

Facility type approved products

• 1000 FTAPs from 1150ms to 600ms

• 9000 FTAPs from 6600ms to 4600ms

https://openlmis.atlassian.net/browse/OLMIS-3773

Facility search

• From 4s to about 700ms (measured with automated perf tests)

https://openlmis.atlassian.net/browse/OLMIS-3641

Supply Lines (mainly affecting Convert requisition to order screen)

• Getting all 1000 supply lines from 10s to 500ms

• Searching supply lines by supplying facility id etc. from 8s to 200ms

https://openlmis.atlassian.net/browse/OLMIS-3496

Requisition initiate (Retrieve PoD step)

Performance tests:

• getting all PODs from 170 seconds to 1.241 s (line90)

• for getting POD by orderId from 2 seconds to 1.122s (line90)

https://openlmis.atlassian.net/browse/OLMIS-3494

Processing periods search (affecting requisition initiate)

Performance tests for search:

• from 15s to 20ms