# Disk Usage by Execution / Consensus Client

### Summary

As of late 2022, here is a sampling of EL/CL combinations and their disk space usage. Sorted by highest to lowest disk usage, from a glance you can determine relatively how much space each client combination required at that time and hopefully help you make better informed decisions.

<details>

<summary>Mainnet tldr</summary>

**Least disk space use:** Besu/Teku 577GB

**Most disk space use**: Erigon/Lodestar 1.6TB

</details>

<details>

<summary>Testnet Goerli tldr</summary>

**Least disk space use:** Besu/Prysm

**Most disk space use**: Erigon/Nimbus

</details>

### Mainnet

{% hint style="info" %}
Execution and consensus layer data usage numbers as of 2022.12.19 by barnabas
{% endhint %}

| Disk Use | CL EL Combination     |
| -------- | --------------------- |
| 1.6T     | erigon-lodestar       |
| 1.6T     | erigon-prysm          |
| 1.5T     | erigon-nimbus         |
| 1.5T     | erigon-lighthouse     |
| 1.4T     | erigon-teku           |
| 1.2T     | nethermind-lodestar   |
| 1.1T     | nethermind-nimbus     |
| 1.1T     | nethermind-lighthouse |
| 1.1T     | nethermind-prysm      |
| 1.0T     | nethermind-teku       |
| 1.0T     | geth-lodestar         |
| 947G     | geth-lighthouse       |
| 946G     | geth-prysm            |
| 923G     | geth-nimbus           |
| 886G     | geth-teku             |
| 688G     | besu-lodestar         |
| 645G     | besu-prysm            |
| 604G     | besu-nimbus           |
| 631G     | besu-lighthouse       |
| 577G     | besu-teku             |

### Testnet Goerli

{% hint style="info" %}
Execution and consensus layer data usage numbers as of 2022.12.19 by Sea Monkey
{% endhint %}

| Disk Use | CL EL Combination     |
| -------- | --------------------- |
| 643G     | nimbus-erigon         |
| 639G     | lighthouse-erigon     |
| 431G     | lodestar-erigon       |
| 390G     | teku-erigon           |
| 344G     | lighthouse-nethermind |
| 330G     | prysm-nethermind      |
| 329G     | prysm-erigon          |
| 318G     | nimbus-nethermind     |
| 312G     | teku-nethermind       |
| 304G     | lighthouse-geth       |
| 288G     | lodestar-nethermind   |
| 281G     | nimbus-geth           |
| 273G     | lodestar-besu         |
| 270G     | teku-geth             |
| 268G     | lighthouse-besu       |
| 248G     | lodestar-geth         |
| 241G     | nimbus-besu           |
| 239G     | teku-besu             |
| 218G     | prysm-geth            |
| 142G     | prysm-besu            |


---

# Agent Instructions: 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:

```
GET https://www.coincashew.com/coins/overview-eth/guide-or-how-to-setup-a-validator-on-eth2-mainnet/part-iii-tips/disk-usage-by-execution-consensus-client.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.