Performance Test for updated lux:itemAny triple- scheduled for TBD

[clarkepeterf]

Update this ticket when the data is ready for it

Primary Objective

Identify the scenario in Perf Test Line Up and state the primary objective.

Changes Being Tested

A new dataset will add item's member_of relationship to the lux:itemAny triple. We will need to test the performance impact of this change

Context

Environment and Versions

• Environment: TST which is configured to the TODO backend.
• MarkLogic TODO
• Backend TODO
• Middle Tier TODO
• FrontendTODO
• Dataset produced on TODO

Backend Application Server Configuration

• lux-request-group-1 on port 8003: The middle tier is expected to send all requests here except search and relatedList requests. Maximum of 6 concurrent requests.
• lux-request-group-2 on port 8004: The middle tier is expected to send all search and relatedList requests to this application server. Maximum of 12 concurrent requests.
• Maximum of 18 concurrent requests per node.

Tasks

For more information please see the documentation: LUX Performance Testing Procedure

Prep, Start, and Preliminary Checks

• [ ] Confirm the most recent blue-green switch is 100% complete (i.e., no part of TST is using PROD).
• [ ] Deploy code and/or configuration changes that are being tested.
• [ ] Disable middle-tier caching in TST (instructions).
• [ ] Verify LUX trace events are enabled plus v8 delay timeout.
• [ ] Smoke test the front end.
• [ ] Start collecting OS-level metrics (instructions).
• [ ] Start collecting middle tier metrics (script)
• [ ] QA: Verify/set ramp-up schedule to 2 simple search VUs, 1 filtered VU, and 1 entity page VU every three minutes until there are 148 users then hold for 15 minutes.
• [ ] QA: Verify test is configured with three second wait times.
• [ ] QA: Verify scripts point to TST, https://lux-front-tst.collections.yale.edu/
• [ ] Team: Sign off on the above before proceeding.
• [ ] QA: Start performance test.
• [ ] Team: begin monitoring for v8 engine crashes.
• [ ] Team: check total request count at 10 minutes.
• [ ] Team: check total request count at 15 minutes.
• [ ] Team: check total request count at 20 minutes.
• [ ] QA: Finish performance test.

Collect data

• [ ] Stop collecting OS-level metrics and attach to the ticket.
• [ ] Stop collecting middle-tier metrics and attach to the ticket.
• [ ] Collect data from AWS and attach to ticket.
• [ ] Collect ML monitoring history (instructions).
• [ ] Collect (script), trim (script), and attach backend logs to the ticket.
• [ ] Pull app server queue metrics (script), attach to the ticket, and record in Perf: Key Metrics. Starting in ML 11.2.0, this information may be included in the ML monitoring history screenshots and exports.
• [ ] Update online spreadsheet tabs with what is known at this point.

Restore and Verify Environment

• [ ] Revert this test's code and configuration changes
• [ ] Enable middle-tier caching (instructions).
• [ ] Smoke test the front end.

Analyze

• [ ] Upon receipt, review report from QA and update related portions of the online spreadsheet tabs.
• [ ] Mine the backend logs?
• [ ] Determine if the test is valid.
• [ ] Determine if the performance is acceptable.

[roamye]

UAT 7/22 Need to identify the objective of the test and a date. Keeping in prioritization review.

[roamye]

UAT 8/26.

Closing this as we are not looking into doing a performance test right now.