[MODBULKED-23] Establish performance baseline for item status bulk updates Created: 05/Feb/22  Updated: 02/Nov/22  Resolved: 02/Nov/22

Status: Closed
Project: mod-bulkedit
Components: None
Affects versions: None
Fix versions: None

Type: Story Priority: P3
Reporter: Magda Zacharska Assignee: Aliaksei Harbuz
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by RANCHER-215 Monitoring In Progress
Cloners
is cloned by PERF-287 Clone - Establish performance baselin... Closed
is cloned by PERF-288 PTF - Establish performance baseline ... Closed
Defines
defines UXPROD-3543 Bulk Edit performance Closed
Relates
relates to PERF-284 Create a Bulk Edits JMeter Script Closed
Sprint: Firebird - Sprint 145, Firebird - Sprint 151, Firebird - Sprint 146, Firebird - Sprint 153, Firebird - Sprint 144
Story Points: 3
Development Team: Firebird
RCA Group: TBD

 Description   

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

Additional information:
Coordinate with devops to get memory/cpu usage



 Comments   
Comment by Magda Zacharska [ 12/Jun/22 ]

Removing story points as the scope has changed.

Comment by Magda Zacharska [ 20/Jul/22 ]

Removing item former ids due to MODEXPW-194 Closed that will be addressed in later releases.

Comment by Aliaksei Harbuz [ 27/Jul/22 ]

Magda Zacharska , the report - https://folio-org.atlassian.net/wiki/display/FOLIJET/JMeter+performance+tests+for+bulk+edit+statuses+of+items for bulk edit statuses is created.

Comment by Viachaslau Khandramai (Inactive) [ 27/Jul/22 ]

Aliaksei Harbuz , the results of this story don't include multi-user cases. I assume we need to know how Bulk-Edit operates with several simultaneously users. For this purposes I can propose re-establish performance baseline including from 1 to 5 parallel users/threads. 

Magda Zacharska, please, confirm if we need such investigation.

CC Denis 

Thanks,

Slava

Comment by Magda Zacharska [ 27/Jul/22 ]

Thanks Viachaslau Khandramai for pointing it out. We do need tests for multiple concurrent users. Aliaksei Harbuz please include performance baseline for 1 to 5 parallel users.

Comment by Magda Zacharska [ 14/Oct/22 ]

Hi Aliaksei Harbuz is the story still blocked? If yes, what is blocking it?

Comment by Aliaksei Harbuz [ 14/Oct/22 ]

Hi Magda Zacharska , I need bulk-edit-perf for several days. Previously it was busy by some other activity, I could not use it.

Comment by Magda Zacharska [ 02/Nov/22 ]

The report provided by PTF contains information about performance baseline for bulk editing item records: https://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=1396821

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