[FOLIO-2328] verify performance of filtering instances by item.effectiveLocationId Created: 28/Oct/19  Updated: 03/Jun/20  Resolved: 11/Nov/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P2
Reporter: Jakub Skoczen Assignee: Eric Valuk
Resolution: Done Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to MODINVSTOR-256 Improve performance of /instance-stor... Closed
Sprint: CP: sprint 76
Story Points: 1
Development Team: Core: Platform

 Description   

A new field has been introduced through MODINVSTOR-348 Closed called effectiveLocation, based on this field a new filter will be added to the UI that will allow to filter instances by the value of this field:

/instance-storage/instances?query=item.effectiveLocationId==xxx

We should verify performance of this search in the platform-per-test environment. This issues might create similar perf issues as in MODINVSTOR-256 Closed and MODINVSTOR-292 Closed .

Acceptance criteria

  • A jMeter test included in the perf-test-platform
  • any changes to the perf data set to ensure the test can be executed


 Comments   
Comment by Julian Ladisch [ 28/Oct/19 ]

I changed item.effectiveLocationId=xxx to item.effectiveLocationId==xxx in the description because we want to match the complete UUID using the B-tree index.

Generated at Thu Feb 08 23:19:51 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.