diff --git a/docs/modules/ROOT/nav.adoc b/docs/modules/ROOT/nav.adoc
index fe0dd4a..3662915 100644
--- a/docs/modules/ROOT/nav.adoc
+++ b/docs/modules/ROOT/nav.adoc
@@ -64,8 +64,7 @@
 *** xref:data-formats:xml.adoc[XML]
 *** xref:data-formats:protobuf.adoc[Protobuf]
 
-* Performance
-//** xref:streams:streaming-data.adoc[Benchmarks]
+* xref:deploying:performance.adoc[]
 
 .Query
 * xref:querying:writing-queries.adoc[Query with {short-product-name}]
diff --git a/docs/modules/deploying/images/perf-metrics.png b/docs/modules/deploying/images/perf-metrics.png
new file mode 100644
index 0000000..f30c229
Binary files /dev/null and b/docs/modules/deploying/images/perf-metrics.png differ
diff --git a/docs/modules/deploying/pages/performance.adoc b/docs/modules/deploying/pages/performance.adoc
new file mode 100644
index 0000000..76b9d18
--- /dev/null
+++ b/docs/modules/deploying/pages/performance.adoc
@@ -0,0 +1,25 @@
+= Performance
+:description: Performance when running {short-product-name}
+
+Running {short-product-name} in production and at scale.
+
+== Minimum specifications
+
+We recommend running {short-product-name} on a machine with at least 2 CPUs and 8 GiB of memory.
+
+For production resilience, please ensure you're running multiple {short-product-name} instances to ensure continued uptime.
+
+{short-product-name} is efficient at utilizing spare resources so scales very effectively as you scale the underlying hardware to have greater available resources.
+
+Doubling the available resources can roughly half your processing latency and increase your overall throughput.
+
+== Tuning
+
+When running {short-product-name} in xref:deploying:production-deployments.adoc[production], ensure you've configured an external xref:querying:observability.adoc#performance-metrics--prometheus[Prometheus] server to capture your metrics, then {short-product-name} will graph them on the Endpoint page. From there you can see the throughput of your query and the latency of each message processed.
+
+image:perf-metrics.png[]
+
+The throughput of {short-product-name} will be highly dependent on the complexity of your queries and external models that the system is having to make requests to. A query running a basic streaming process with minimal lookups should be able to scale until exhausting your available processing resources. A query with lots of external lookups and connections is more likely to be bound by IO time, so monitor your query durations closely.
+
+If your external lookups are cacheable, consider using {short-product-name}'s native xref:describing-data-sources:caching.adoc[caching] annotations to save making the same API requests repeatedly and retrieve the data from local memory instead.
+