Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Jira Legacy
serverSystem JIRA
columnskey,summary,type,assignee,priority,status,resolution
maximumIssues20
jqlQueryproject = OLMIS AND fixVersion = 3.6 AND labels = Performance AND Sprint in (386, 383, 361, 353, 355, 372, 376, 364, 338, 369, 347) and status = 'Done'
serverId448ba138-230b-3f91-a83e-16e7db1deed1


Performance gains

TicketRelated endpoint / Part of the systemImprovements
Jira Legacy
serverSystem JIRA
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-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)
Jira Legacy
serverSystem JIRA
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-6074
and
Jira Legacy
serverSystem JIRA
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-6073
Logging in
  • This was a regression, so no performance boost compared to v3.5
Jira Legacy
serverSystem JIRA
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-5000
Convert requisition to order screen
  • Execution time for an endpoint was reduced from 19s to 10s (measured with automated perf tests)
Jira Legacy
serverSystem JIRA
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-4531
Requisition initiate (+ other POST/PUT requests)
  • The initiate requisition endpoint response is now compressed, which will be especially noticeable on slow connections
Jira Legacy
serverSystem JIRA
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-4291
Facility type approved products
  • 1000 FTAPs from 1150ms to 600ms
  • 9000 FTAPs from 6600ms to 4600ms
Jira Legacy
serverSystem JIRA
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-3773
Facility search
  • From 4s to about 700ms (measured with automated perf tests)
Jira Legacy
serverSystem JIRA
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-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
Jira Legacy
serverSystem JIRA
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-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)
Jira Legacy
serverSystem JIRA
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-3494
Processing periods search (affecting requisition initiate)

Performance tests for search:

  • from 15s to 20ms