diff --git a/noir/README.md b/noir/README.md
index c604644e712c..beaaafeac586 100644
--- a/noir/README.md
+++ b/noir/README.md
@@ -3,18 +3,44 @@
 We subrepo noir into the folder `noir-repo`.
 This folder contains dockerfiles and scripts for performing our custom build of noir for the monorepo.
 
-# Syncing with the main Noir repository
+## Syncing with the main Noir repository
 
 In order to keep aztec-packages in step with the main Noir repository we need to periodically sync between them.
 
 Syncing from aztec-packages into noir currently attempts to revert any changes in Noir since the last sync so it's recommended to always sync from Noir first to ensure that aztec-packages is up-to-date.
 
-## Syncing from Noir to aztec-packages.
+### Syncing from Noir to aztec-packages.
 
 To start the sync run [this action](https://github.com/AztecProtocol/aztec-packages/actions/workflows/pull-noir.yml) manually (click the "Run Workflow" button in the top right). aztec-bot will then open a new PR which does the initial sync, this will have merge conflicts with master which will need to be resolved.
 
-## Syncing from aztec-packages to Noir.
+### Syncing from aztec-packages to Noir.
 
 When syncing from aztec-packages to Noir it's important to check that the latest release of `bb` uses the same ACIR serialization format as the current master commit. This is because Noir uses a released version of barretenberg rather than being developed in sync with it, it's then not possible to sync if there's been serialization changes since the last release.
 
 To start the sync run [this action](https://github.com/AztecProtocol/aztec-packages/actions/workflows/mirror-noir-subrepo.yml) manually (click the "Run Workflow" button in the top right). aztec-bot will then open a new PR in the `noir-lang/noir` repository which does the initial sync, this will have merge conflicts with master which will need to be resolved.
+
+## Benchmarking
+
+This repository supports benchmarking of Barretenberg's proving speeds on Noir programs.
+
+### Benchmarking locally
+
+To gather proving speeds benchmark on your local machine:
+
+1. [Install Docker](https://docs.docker.com/get-docker/)
+2. [Install Earthly](https://earthly.dev/get-earthly)
+3. `git clone https://github.com/AztecProtocol/aztec-packages.git`
+4. (If you are on macOS:)
+    1. `brew install coreutils`
+    2. Edit the `cp --parents…` line in [*aztec-packages/noir/Earthfile*](https://github.com/AztecProtocol/aztec-packages/blob/master/noir/Earthfile) to `gcp --parents…`
+5. `earthly ./noir+bench-acir-bb`
+
+**Note:** It is recommended to increase or maximize your Docker instance's memory limit, as some of the pre-benchmark compilations are very memory intensive (e.g. an 8GB memory limit is insufficient and is expected to cause OOM errors).
+
+### Adding / updating benchmarks
+
+Benchmarking programs are located in [*noir/noir-repo/test_programs/benchmarks*](https://github.com/AztecProtocol/aztec-packages/tree/master/noir/noir-repo/test_programs/benchmarks). Follow the naming scheme of folders and packages (in Nargo.toml) beginning with *bench_...* and add or update programs in the directory directly.
+
+To benchmark locally after modifications:
+1. `git commit ...`
+2. `earthly ./noir+bench-acir-bb`