2_load_tests_quickstart

# Run Websocket load tests for specific service IDs
make load_test_websocket xrplevm,xrplevm-testnet

# Run Websocket load tests for all Websocket-compatible services  
make load_test_websocket_all

Note: Websocket load tests are completely separate from HTTP tests. Use the regular make load_test commands for HTTP-only testing, and the make load_test_websocket commands for Websocket-only testing.

🌿 Grove Employees

You can obtain the required Portal Application ID and API Key from the Grove Portal App Credentials for PATH Load Testing on 1Password.

You can export like so to your shell:

op item get iznzvqegxbl4y73d5lppm4y6r4 --fields notesPlain --format json | jq -r '.value'
1

Setup configs & credentials

Run:

make config_copy_e2e_load_test

You will be prompted to enter your Grove Portal Application ID and API Key.

2

Run load tests against Grove Portal

HTTP load tests with specified service IDs only:

make load_test eth,xrplevm

HTTP load tests with all service IDs:

make load_test_all

Websocket load tests with specified service IDs only:

make load_test_websocket xrplevm,xrplevm-testnet

Websocket load tests with all Websocket-compatible service IDs:

make load_test_websocket_all

Load Testing Grove Fallback Endpoints

🌿 Grove Employees Only

This section is exclusively for Grove employees who need to test PATH's fallback endpoint functionality.

You can obtain the required PATH config from the Grove Portal App Credentials for PATH Load Testing on 1Password.

1

Download PATH config

First, download the PATH config from 1Password (see the existing Grove Portal section above for credentials access).

2

Enable fallback endpoints

Enable fallback endpoints for all services:

make config_enable_grove_fallback
3

Restart PATH

Apply the config updates:

make path_down; make path_up
4

Run load tests

Finally, run load tests (example for specific service IDs):

make load_test eth,xrplevm

Was this helpful?