Files
lasuite-drive/load-tests/user.properties.example
T
Nathan VasseandNicolas Clerc 9084163ed9 (load-tests) add a JMeter basic user session scenario
We need to measure backend response times and error codes from 100 up to
100k simultaneous users, on any instance. The scenario simulates a full
user session (browse, recents, shared-with-me, folder creation, upload,
trash, hard-delete) with randomized think times, using the e2e auth
endpoint instead of the IDP, out of scope like the WOPI editors.

Everything is property-driven (BASE_URL, USERS, USER_OFFSET...) so the
same plan runs unchanged against any instance and across distributed
injectors, each with its own USER_OFFSET to keep generated user emails
globally unique. Uploads reproduce the frontend flow (item creation,
presigned PUT to the object storage, upload-ended) and randomly pick a
fixture entry; folder entries mirror the frontend folder upload by
materializing the hierarchy before uploading each file into its parent.
2026-09-03 13:53:35 +02:00

20 lines
705 B
Plaintext

# Per-injector JMeter properties for distributed runs.
#
# Copy this file to `user.properties` on each injector machine and give each
# one a distinct USER_OFFSET so virtual users get globally unique emails
# (load-user-<USER_OFFSET + threadNum>@test.test).
#
# Example for 3 injectors running 1000 users each:
# injector 1: USER_OFFSET=0 -> load-user-1..1000
# injector 2: USER_OFFSET=1000 -> load-user-1001..2000
# injector 3: USER_OFFSET=2000 -> load-user-2001..3000
USER_OFFSET=0
# Any other property from the README can also be pinned here instead of
# being passed with -J on the command line, e.g.:
# BASE_URL=https://drive-load.example.com
# USERS=1000
# RAMP_UP=600
# DURATION=1800