hyperdrive: add placement guidance

Author: elithrar

src/content/docs/hyperdrive/concepts/how-hyperdrive-works.mdx

@@ -51,6 +51,8 @@ Hyperdrive automatically manages the connection pool properties for you, includi
 
 Learn more about connection pooling behavior and configuration in [Connection pooling](/hyperdrive/concepts/connection-pooling/).
 
+<Render file="placement-hint-partial" product="hyperdrive" />
+
 ### 3. Query Caching
 
 Hyperdrive supports caching of non-mutating (read) queries to your database.

src/content/docs/hyperdrive/get-started.mdx

@@ -402,6 +402,8 @@ For example, if the URL of your new Worker is `hyperdrive-tutorial.<YOUR_SUBDOMA
 
 By finishing this tutorial, you have created a Hyperdrive configuration, a Worker to access that database and deployed your project globally.
 
+<Render file="placement-hint-partial" product="hyperdrive" />
+
 ## Next steps
 
 - Learn more about [how Hyperdrive works](/hyperdrive/concepts/how-hyperdrive-works/).

src/content/docs/hyperdrive/reference/faq.mdx

@@ -27,6 +27,12 @@ and how Hyperdrive solves this.
 
 D1 does not require round trips to create database connections. D1 is designed to be performant for access from Workers by default, without needing Hyperdrive.
 
+### Should I use Placement with Hyperdrive?
+
+Yes, if your Worker makes multiple queries per request. [Placement](/workers/configuration/placement/) runs your Worker near your database, reducing per-query latency from 20-30ms to 1-3ms. Hyperdrive handles connection pooling and setup. Placement reduces the network distance for query execution.
+
+Use `placement.region` if your database runs in AWS, GCP, or Azure. Use `placement.host` for databases hosted elsewhere.
+
 ## Pricing
 
 ### Does Hyperdrive charge for data transfer / egress?

src/content/partials/hyperdrive/placement-hint-partial.mdx

@@ -0,0 +1,19 @@
+---
+{}
+---
+
+:::note[Reduce latency with Placement]
+
+If your Worker makes **multiple sequential queries** per request, use [Placement](/workers/configuration/placement/) to run your Worker close to your database. Each query adds round-trip latency: 20-30ms from a distant region, or 1-3ms when placed nearby. Multiple queries compound this difference.
+
+If your Worker makes only one query per request, placement does not improve end-to-end latency. The total round-trip time is the same whether it happens near the user or near the database.
+
+```jsonc title="wrangler.jsonc"
+{
+	"placement": {
+		"region": "aws:us-east-1", // Match your database region, for example "gcp:us-east4" or "azure:eastus"
+	},
+}
+```
+
+:::