4_load_tests_deep_dive

# yaml-language-server: $schema=https://raw.githubusercontent.com/buildwithgrove/path/refs/heads/main/e2e/config/e2e_load_test.config.schema.yaml

All currently supported Grove Portal services are supported in the load tests.

To see the list of supported services for the tests, see the test_cases array in the Load Test Config file.

The load tests collect and validate comprehensive metrics across multiple dimensions:

Category

Metrics Collected

HTTP Metrics

- Success rates (HTTP 200) - Status code distribution - HTTP error categorization

Latency Metrics

- P50, P95, P99 latency percentiles - Average latency - Per-method latency analysis

JSON-RPC Validation

- Response unmarshaling success - JSON-RPC error field validation - Result field validation - Protocol-specific validation

Service-Level Metrics

- Per-service success aggregation - Cross-method performance comparison - Service reliability scoring - Error categorization and reporting

Tests will fail if any configured thresholds are exceeded, ensuring consistent service quality and performance.

When running against local PATH instances, logs may be written to ./path_log_load_test_{timestamp}.txt.

In order to enable this, set the log_to_file field:

yq eval '.e2e_load_test_config.load_test_config.log_to_file = true' -i ./e2e/config/.e2e_load_test.config.yaml

You should see the following log line at the bottom of the test summary:

===== 👀 LOGS 👀 =====

 ✍️ PATH container output logged to /tmp/path_log_load_test_1745527319.txt ✍️

===== 👀 LOGS 👀 =====

Was this helpful?