Performance improvements in 3.6

Owned by Sebastian Brudziński
Last updated: Apr 10, 2019
1 min read

key summary type assignee priority status resolution
Refresh


Performance gains

TicketRelated endpoint / Part of the systemImprovements
OLMIS-6077 - Getting issue details... STATUS
Requisition initiate screen
  • The time to initiate the requisition was reduced by the time required to fetch requisition (depends on the size of requisition)
OLMIS-6074 - Getting issue details... STATUS and OLMIS-6073 - Getting issue details... STATUS
Logging in
  • This was a regression, so no performance boost compared to v3.5
OLMIS-5000 - Getting issue details... STATUS
Convert requisition to order screen
  • Execution time for an endpoint was reduced from 19s to 10s (measured with automated perf tests)
OLMIS-4531 - Getting issue details... STATUS
Requisition initiate (+ other POST/PUT requests)
  • The initiate requisition endpoint response is now compressed, which will be especially noticeable on slow connections
OLMIS-4291 - Getting issue details... STATUS
Facility type approved products
  • 1000 FTAPs from 1150ms to 600ms
  • 9000 FTAPs from 6600ms to 4600ms
OLMIS-3773 - Getting issue details... STATUS
Facility search
  • From 4s to about 700ms (measured with automated perf tests)
OLMIS-3641 - Getting issue details... STATUS
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
OLMIS-3496 - Getting issue details... STATUS
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)
OLMIS-3494 - Getting issue details... STATUS Processing periods search (affecting requisition initiate)

Performance tests for search:

  • from 15s to 20ms

OpenLMIS: the global initiative for powerful LMIS software