> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/deploy/host-n8n/configure-n8n/scaling/measure-performance.md).

# Measure performance

n8n can handle up to 220 workflow executions per second on a single instance, with the ability to scale up further by adding more instances.

This document outlines n8n's performance benchmarking. It describes the factors that affect performance, and includes two example benchmarks.

## Performance factors <a href="#performance-factors" id="performance-factors"></a>

The performance of n8n depends on factors including:

* The workflow type
* The resources available to n8n
* How you configure n8n's scaling options

## Run your own benchmarking <a href="#run-your-own-benchmarking" id="run-your-own-benchmarking"></a>

To get an accurate estimate for your use case, run n8n's [benchmarking framework](https://github.com/n8n-io/n8n/tree/master/packages/%40n8n/benchmark). The repository contains more information about the benchmarking.

## Example: Single instance performance <a href="#example-single-instance-performance" id="example-single-instance-performance"></a>

This test measures how response time increases as requests per second increase. It looks at the response time when calling the Webhook Trigger node.

Setup:

* Hardware: ECS c5a.large instance (4GB RAM)
* n8n setup: Single n8n instance (running in main mode, with Postgres database)
* Workflow: Webhook Trigger node, Edit Fields node

<figure><img src="/files/r03BYZ1wcm4IMbPRfRqH" alt=""><figcaption><p>This graph shows the percentage of requests to the Webhook Trigger node getting a response within 100 seconds, and how that varies with load. Under higher loads n8n usually still processes the data, but takes over 100s to respond.</p></figcaption></figure>

## Example: Multi-instance performance <a href="#example-multi-instance-performance" id="example-multi-instance-performance"></a>

This test measures how response time increases as requests per second increase. It looks at the response time when calling the Webhook Trigger node.

Setup:

* Hardware: seven ECS c5a.4xlarge instances (8GB RAM each)
* n8n setup: two webhook instances, four worker instances, one database instance (MySQL), one main instance running n8n and Redis
* Workflow: Webhook Trigger node, Edit Fields node
* Multi-instance setups use [Queue mode](/deploy/host-n8n/configure-n8n/scaling/enable-queue-mode.md)

<figure><img src="/files/F3BNio7Y8iFms7WQSeHW" alt=""><figcaption><p>This graph shows the percentage of requests to the Webhook Trigger node getting a response within 100 seconds, and how that varies with load. Under higher loads n8n usually still processes the data, but takes over 100s to respond.</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.n8n.io/deploy/host-n8n/configure-n8n/scaling/measure-performance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.