n8n/packages/@n8n/benchmark
github-actions[bot] 247bcc16c8
🚀 Release 1.65.0 (#11386)
Co-authored-by: cstuncsik <5410822+cstuncsik@users.noreply.github.com>
2024-10-24 12:29:51 +02:00
..
bin feat: Add n8n-benchmark cli (no-changelog) (#10410) 2024-08-22 11:33:11 +03:00
infra ci: Remove benchmark VM entra login (#10679) 2024-09-05 13:57:09 +03:00
scenarios fix(benchmark): Fix single webhook script path in manifest (#11308) 2024-10-18 13:36:53 +03:00
scripts fix(benchmark): Benchmark improvements (#11290) 2024-10-17 13:37:00 +03:00
src feat(benchmark): Add filter flag (#11355) 2024-10-23 15:09:30 +03:00
.eslintrc.js refactor(benchmark): Use kebab-case for file and directory names (#10787) 2024-09-12 16:06:43 +03:00
.gitignore feat: Benchmark env with run scripts (no-changelog) (#10477) 2024-08-23 14:43:26 +03:00
biome.jsonc ci: Setup biome and pre-commit hooks for formatting (no-changelog) (#10795) 2024-09-17 15:10:22 +03:00
Dockerfile build(benchmark): Fix docker image build (#10854) 2024-09-17 17:37:07 +03:00
package.json 🚀 Release 1.65.0 (#11386) 2024-10-24 12:29:51 +02:00
README.md feat(benchmark): Add filter flag (#11355) 2024-10-23 15:09:30 +03:00
tsconfig.build.json feat: Add n8n-benchmark cli (no-changelog) (#10410) 2024-08-22 11:33:11 +03:00
tsconfig.json feat: Add n8n-benchmark cli (no-changelog) (#10410) 2024-08-22 11:33:11 +03:00

n8n benchmarking tool

Tool for executing benchmarks against an n8n instance.

Directory structure

packages/@n8n/benchmark
├── scenarios        Benchmark scenarios
├── src              Source code for the n8n-benchmark cli
├── Dockerfile       Dockerfile for the n8n-benchmark cli
├── scripts          Orchestration scripts

Benchmarking an existing n8n instance

The easiest way to run the existing benchmark scenarios is to use the benchmark docker image:

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 \
	--n8nUserEmail=InstanceOwner@email.com \
	--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 and load them using the --testScenariosPath flag:

# 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 \
	--n8nUserEmail=InstanceOwner@email.com \
	--n8nUserPassword=InstanceOwnerPassword \
	--vus=5 \
	--duration=1m \
	--testScenariosPath=/scenarios

Running the entire benchmark suite

The benchmark suite consists of benchmark scenarios and different n8n setups.

locally

pnpm benchmark-locally

In the cloud

pnpm benchmark-in-cloud

Running the n8n-benchmark cli

The n8n-benchmark cli is a node.js program that runs one or more scenarios against a single n8n instance.

Locally with Docker

Build the Docker image:

# Must be run in the repository root
# k6 doesn't have an arm64 build available for linux, we need to build against amd64
docker build --platform linux/amd64 -t n8n-benchmark -f packages/@n8n/benchmark/Dockerfile .

Run the image

docker run \
  -e N8N_USER_EMAIL=user@n8n.io \
  -e N8N_USER_PASSWORD=password \
  # For macos, n8n running outside docker
  -e N8N_BASE_URL=http://host.docker.internal:5678 \
  n8n-benchmark

Locally without Docker

Requirements:

  • k6
  • Node.js v20 or higher
pnpm build

# Run tests against http://localhost:5678 with specified email and password
N8N_USER_EMAIL=user@n8n.io N8N_USER_PASSWORD=password ./bin/n8n-benchmark run

Benchmark scenarios

A benchmark scenario defines one or multiple steps to execute and measure. It consists of:

  • Manifest file which describes and configures the scenario
  • Any test data that is imported before the scenario is run
  • A k6 script which executes the steps and receives API_BASE_URL environment variable in runtime.

Available scenarios are located in ./scenarios.

n8n setups

A n8n setup defines a single n8n runtime configuration using Docker compose. Different n8n setups are located in ./scripts/n8nSetups.