> ## Documentation Index
> Fetch the complete documentation index at: https://lightdash-refactor-full-audit-reorg.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Resource recommendations

> Recommended resource requests and availability settings for each Lightdash component.

Baseline per-component resource requests for a standard self-hosted instance deployed with the official Helm chart:

| Component                 | CPU    | Memory      | Ephemeral | Replicas |
| ------------------------- | ------ | ----------- | --------- | -------- |
| Backend                   | 500m–1 | 1.5–4 Gi    | 1–2 Gi    | **2+**   |
| Scheduler worker          | 500m   | 1425 Mi     | 1 Gi      | 1        |
| Warehouse NATS worker     | 250m   | 1.5 Gi      | 9 Gi      | 1        |
| Pre-aggregate NATS worker | 650m   | 4 Gi        | 9 Gi      | 1        |
| Browserless               | 2      | 4 Gi        | 1 Gi      | 1        |
| NATS                      | 100m   | 256 Mi–1 Gi | —         | 1        |

NATS workers buffer large result sets on ephemeral disk before uploading to S3 — the 9 Gi ephemeral-storage request is not a typo.

## Availability

Run at least two backend replicas with pod anti-affinity and a pod disruption budget:

```yaml theme={null}
replicaCount: 2

autoscaling:
  enabled: true
  minReplicas: 2
  maxReplicas: 10
  targetCPUUtilizationPercentage: 60   # backend only; workers scale via replicas

podAntiAffinity:
  enabled: true        # spreads each component across nodes (hard) and zones (soft)

podDisruptionBudget:
  enabled: true
  minAvailable: 1
```