|
To verify the result, I used the same JMeter checkin/out script but disabled all API calls in the workflow except the checkin-by-barcode one. The test was done on a standard perf env with the code from folio stable site on 2018-02-15. The test sends 100 requests in 60 seconds ramp-up window. Each request looks like checkin.txt and the barcode is selected from a pool and is different for each request. The JMeter log is in checkin_100_60.log and the result is in
In summary: even though a single checkin-by-barcode call on an idle system is not slow (under 2 seconds). When there are multiple concurrent checkin API calls (100 requests in 60s ramp-up window), each individual API call suffer significant latency (average is 83 seconds, between min 64s to max 97s). The bright side is that throughput is still good (49 requests per minute). The possible reason for individual latency is that behind the scene, checkin-by-code API makes multiple other API calls, see attached log files for mod-circulation.log , mod-circulation-storage.log , and mod-inventory-storage.log .
|