Add D1 changelog and release notes for request latency improvements (#19235)

* Add D1 changelog and release notes for request latency improvements

* Update src/content/changelogs-next/2025-01-07-d1-faster-query.mdx

Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>

* try to fix parse error

* Add metrics graph & address feedback

* De-emphasize REST

* Change REST API wording

* Add image caption

* change wording

* Apply suggestions from code review

* Update 2025-01-07-d1-faster-query.mdx

* Update src/content/changelogs-next/2025-01-07-d1-faster-query.mdx

Co-authored-by: Matt Silverlock <[email protected]>

* Update 2025-01-07-d1-faster-query.mdx

* Update d1.yaml

try to fix parse error

* Update d1.yaml

escape quote to fix yaml?

* Update d1.yaml

fix indentation

* Update src/content/changelogs-next/2025-01-07-d1-faster-query.mdx

* Update 2025-01-07-d1-faster-query.mdx

* address comments & add image to d1 changelog

* wording change

* fix relative path

* Update src/content/changelogs/d1.yaml

* Handling images correctly for D1 changelog entry.

---------

Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>
Co-authored-by: Matt Silverlock <[email protected]>
Co-authored-by: Lambros Petrou <[email protected]>
Co-authored-by: Jun Lee <[email protected]>

Author: 5 people

public/images/d1/faster-d1-worker-api.png

@@ -0,0 +1,17 @@
+---
+title: 40-60% Faster D1 Worker API Requests
+description: D1's Worker API request latency decreases by 40-60%.
+products:
+  - d1
+date: 2025-01-07T18:00:00Z
+---
+
+Users making [D1](/d1/) requests via the [Workers API](/d1/worker-api/) can see up to a 60% end-to-end latency improvement due to the removal of redundant network round trips needed for each request to a D1 database.
+
+![D1 Worker API latency](public/images/d1/faster-d1-worker-api.png)
+
+*p50, p90, and p95 request latency aggregated across entire D1 service. These latencies are a reference point and should not be viewed as your exact workload improvement.*
+
+This performance improvement benefits all D1 Worker API traffic, especially cross-region requests where network latency is an outsized latency factor. For example, a user in Europe talking to a database in North America. D1 [location hints](/d1/configuration/data-location/#provide-a-location-hint) can be used to influence the geographic location of a database.
+
+For more details on how D1 removed redundant round trips, see the D1 specific changelog [entry](/d1/platform/changelog/#2025-01-07).

src/content/changelogs-next/2025-01-07-d1-faster-query.mdx

@@ -16,6 +16,19 @@ entries:
 
       For better insight into your current usage, refer to your [billing metrics](/d1/observability/billing/) for rows read and rows written, which can be found on the [D1 dashboard](https://dash.cloudflare.com/?account=/workers/d1) or GraphQL API.
 
+  - publish_date: "2025-01-07"
+    title: D1 Worker API request latency decreases by 40-60%.
+    description: |-
+      D1 lowered end-to-end Worker API request latency by 40-60% by eliminating redundant network round trips for each request.
+
+      ![D1 Worker API latency](/public/images/d1/faster-d1-worker-api.png)
+
+      *p50, p90, and p95 request latency aggregated across entire D1 service. These latencies are a reference point and should not be viewed as your exact workload improvement.*
+
+      For each request to a D1 database, at least two network round trips were eliminated. One round trip was due to a bug that is now fixed. The remaining removed round trips are due to avoiding creating a new TCP connection for each request when reaching out to the datacenter hosting the database.
+
+      The removal of redundant network round trips also applies to D1\'s [REST API](/api/resources/d1/subresources/database/methods/query/). However, the REST API still depends on Cloudflare's centralized datacenters for authentication, which reduces the relative performance improvement.
+
   - publish_date: "2024-08-23"
     title: D1 alpha databases have stopped accepting SQL queries
     description: |-