Page Comparison

...

• ERROR rate is low 0,0007% of all requests
• High response time at the beginning of a test were made by caching process.
• Call affected most by caching [get] /inventory/items (holdingsRecordId=="{holdingsRecordId}");
• "Failed to publish LOAN_DUE_DATE_CHANGED event: loan is null" Error, appears each time after making title level request  CIRC-1503
• Duplicate request is defined during creating of a test script  UICIRC-781
• No Memory leaks were defined
• CPU usage is intended, without sudden spikes and anomalies.
• Average response times for 5 users tests (for create TLR, lookup user, retrieve instance data transactions (including all related calls)):
  • While caching going
    • Get instance transaction 8.159159s
    • Create TLR.  1.054054s
    • Get users 0.212 212 s
  • After caching is done:
    • Get Instance transaction 0.657657s
    • Create TLR. 0.820820s
    • Get users 0.160160s
• Average response times for 5 users 1 users tests (for create TLR, lookup user, retrieve instance data transactions (including all related calls)):
•  Caching is done:
  • Get instance transaction 0.657
  • Create TLR.  0.820
  • Get users 0.160

...

At the beginning of a test cache being involved into process. It's expanding high response times at the beginning of a test

Also DRS CPU utilisation utilization is much higher when cache is involved.

...