Uploaded image for project: 'FOLIO'
  1. FOLIO
  2. FOLIO-1815

SPIKE: "profile" checkin/out-by-barcode API response time

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      Core: Platform - Sprint 58, Core: Platform - Sprint 59
    • Story Points:
      3
    • Development Team:
      Core: Platform

      Description

      As shown in FOLIO-1811 and FOLIO-1812, when there are concurrent checkin/out-by-barcode requests, the response time for each checkin/out request is very long. This needs to be improved because checkin/out are likely to be used quite often in a library system.

      Note: since checkin/out-by-barcode APIs fan-out to multiple other APIs to mod-inventory/inventory-storage/circulation-storage, it is inevitable slower due to many calls involved. Also it makes it harder to pin down which APIs or database calls are more time consuming. If FOLIO has a way to help troubleshooting performance across multiple modules/layers, that would be very helpful.

      Acceptance criteria: ideally the response time should be under 2 seconds even when there are concurrent checkin/out requests. Upgrade to latest RMB, and do general performance analysis of check-in/out by barcode.

      • Timing of check-in/out by barcode
      • Timing of search for an instance by known instanceId, for comparison
      • Determine where time is spent

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                nassar Nassib Nassar
                Reporter:
                hji Hongwei Ji
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases