-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' into pay-2096-typeerror-cannot-read-properties-…
…of-undefined-reading
- Loading branch information
Showing
43 changed files
with
397 additions
and
245 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
# n8n benchmarking tool | ||
|
||
Tool for executing benchmarks against an n8n instance. The tool consists of these components: | ||
Tool for executing benchmarks against an n8n instance. | ||
|
||
## Directory structure | ||
|
||
|
@@ -12,6 +12,39 @@ packages/@n8n/benchmark | |
├── scripts Orchestration scripts | ||
``` | ||
|
||
## Benchmarking an existing n8n instance | ||
|
||
The easiest way to run the existing benchmark scenarios is to use the benchmark docker image: | ||
|
||
```sh | ||
docker pull ghcr.io/n8n-io/n8n-benchmark:latest | ||
# Print the help to list all available flags | ||
docker run ghcr.io/n8n-io/n8n-benchmark:latest run --help | ||
# Run all available benchmark scenarios for 1 minute with 5 concurrent requests | ||
docker run ghcr.io/n8n-io/n8n-benchmark:latest run \ | ||
--n8nBaseUrl=https://instance.url \ | ||
[email protected] \ | ||
--n8nUserPassword=InstanceOwnerPassword \ | ||
--vus=5 \ | ||
--duration=1m \ | ||
--scenarioFilter SingleWebhook | ||
``` | ||
|
||
### Using custom scenarios with the Docker image | ||
|
||
It is also possible to create your own [benchmark scenarios](#benchmark-scenarios) and load them using the `--testScenariosPath` flag: | ||
|
||
```sh | ||
# Assuming your scenarios are located in `./scenarios`, mount them into `/scenarios` in the container | ||
docker run -v ./scenarios:/scenarios ghcr.io/n8n-io/n8n-benchmark:latest run \ | ||
--n8nBaseUrl=https://instance.url \ | ||
[email protected] \ | ||
--n8nUserPassword=InstanceOwnerPassword \ | ||
--vus=5 \ | ||
--duration=1m \ | ||
--testScenariosPath=/scenarios | ||
``` | ||
|
||
## Running the entire benchmark suite | ||
|
||
The benchmark suite consists of [benchmark scenarios](#benchmark-scenarios) and different [n8n setups](#n8n-setups). | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.