[PERF-287] Clone - Establish performance baseline for item status bulk updates Created: 06/Sep/22  Updated: 07/Sep/22  Resolved: 07/Sep/22

Status: Closed
Project: perf-testing
Components: None
Affects versions: None
Fix versions: None

Type: Story Priority: P3
Reporter: Denis Anischenko Assignee: Denis Anischenko
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones MODBULKED-23 Establish performance baseline for it... Closed
Defines
defines UXPROD-3543 Bulk Edit performance Closed
Sprint:
Story Points: 3
Development Team: Firebird
RCA Group: TBD

 Description   

This is a clone of https://folio-org.atlassian.net/browse/MODBULKED-23 for PTF Team{}

Purpose/Overview:

Establish a baseline for bulk edit app - item records update.

Requirements/Scope:

  1. Create jmeter tests that can be executed against: https://bulk-edit-perf.ci.folio.org/
  2. The tests cover item status updates for following statuses:
    1. Available
    2. Missing
    3. Withdraw
  3. the test will start with 100 item records edits and then progress to 1000 records edits and then 10 000 and 100 000 records edits
  4. the test will cover scenarios when the bulk edit is triggered by uploading file with following identifiers:
    1. item barcodes
    2. item UUIDs
    3. holdings UUIDs
    4. item HRIDs
    5. item former ids
    6. item accession numbers
  5. the test will cover saving records preview and saving matching records in CSV format
  6. the test will cover impact of the bulk edit on the inventory modules documented: CPU, memory, db timeouts

Approach:

Acceptance criteria:

  • The tests are written and can be executed on demand
  • The findings are documented on the wiki

Coordinate with devops to get memory/cpu usage


Generated at Thu Feb 08 22:30:39 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.