From bf7ebb09fe23ffae4b05e7299cc1f5c6bf3b02cc Mon Sep 17 00:00:00 2001 From: vy-ton Date: Thu, 29 May 2025 12:44:18 -0400 Subject: [PATCH 1/9] D1 REST API latency changelog --- .../d1/2025-05-30-d1-rest-api-latency.mdx | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx diff --git a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx new file mode 100644 index 000000000000000..aa122acdd0aff86 --- /dev/null +++ b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx @@ -0,0 +1,15 @@ +--- +title: Faster D1 REST API +description: D1 REST API request latency improvements. +products: + - d1 + - workers +date: 2025-05-29T00:00:00Z +--- + +Users using Cloudflare's [REST API](/api/resources/d1/subresources/database/methods/query/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the Cloudflare network data center hosting your database. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core data centers, which added network round trips to select, central locations. + +D1 query endpoints like `/query` and `/raw` have the most noticeable improvements since they no longer access Cloudflare's core data centers. D1 control plane endpoints such as those to create and delete databases see smaller improvements, due to authentication at the network data center hosting a database, but still require access to Cloduflare's core data centers. + +Performance improvements apply to only the REST API. Users can now expect similar performance querying their database via the REST API and via a [Worker](/d1/best-practices/query-d1/#query-d1-with-workers-binding-api). + From 29f6104b054c4c6547c1833d63c2a047df992551 Mon Sep 17 00:00:00 2001 From: vy-ton Date: Thu, 29 May 2025 12:55:01 -0400 Subject: [PATCH 2/9] fix content --- src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx index aa122acdd0aff86..822bedd8b7c2293 100644 --- a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx +++ b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx @@ -7,9 +7,9 @@ products: date: 2025-05-29T00:00:00Z --- -Users using Cloudflare's [REST API](/api/resources/d1/subresources/database/methods/query/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the Cloudflare network data center hosting your database. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core data centers, which added network round trips to select, central locations. +Users using Cloudflare's [REST API](/api/resources/d1/subresources/database/methods/query/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the closest Cloudflare network data center that recieved the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core data centers, which added network round trips to select, central locations. -D1 query endpoints like `/query` and `/raw` have the most noticeable improvements since they no longer access Cloudflare's core data centers. D1 control plane endpoints such as those to create and delete databases see smaller improvements, due to authentication at the network data center hosting a database, but still require access to Cloduflare's core data centers. +D1 query endpoints like `/query` and `/raw` have the most noticeable improvements since they no longer access Cloudflare's core data centers. D1 control plane endpoints such as those to create and delete databases see smaller improvements, due to authentication at the network data center recieving the request, but still require access to Cloduflare's core data centers. Performance improvements apply to only the REST API. Users can now expect similar performance querying their database via the REST API and via a [Worker](/d1/best-practices/query-d1/#query-d1-with-workers-binding-api). From 791cf2e5c7055d1e2471749b0876e30ccc8e0162 Mon Sep 17 00:00:00 2001 From: Vy Ton Date: Thu, 29 May 2025 12:59:49 -0400 Subject: [PATCH 3/9] Update 2025-05-30-d1-rest-api-latency.mdx --- src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx index 822bedd8b7c2293..bc838a86417ed19 100644 --- a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx +++ b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx @@ -7,9 +7,9 @@ products: date: 2025-05-29T00:00:00Z --- -Users using Cloudflare's [REST API](/api/resources/d1/subresources/database/methods/query/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the closest Cloudflare network data center that recieved the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core data centers, which added network round trips to select, central locations. +Users using Cloudflare's [REST API](/api/resources/d1/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the closest Cloudflare network data center that recieved the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core centralized centers, which added network round trips. -D1 query endpoints like `/query` and `/raw` have the most noticeable improvements since they no longer access Cloudflare's core data centers. D1 control plane endpoints such as those to create and delete databases see smaller improvements, due to authentication at the network data center recieving the request, but still require access to Cloduflare's core data centers. +D1 query endpoints like `/query` and `/raw` have the most noticeable improvements since they no longer access Cloudflare's core data centers. D1 control plane endpoints such as those to create and delete databases see smaller improvements, since they still require access to Cloduflare's core data centers for other control plane metadata. Performance improvements apply to only the REST API. Users can now expect similar performance querying their database via the REST API and via a [Worker](/d1/best-practices/query-d1/#query-d1-with-workers-binding-api). From 07233c5fad495f2141547a8a5e816e640c3f2eee Mon Sep 17 00:00:00 2001 From: Vy Ton Date: Thu, 29 May 2025 13:03:27 -0400 Subject: [PATCH 4/9] typo --- src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx index bc838a86417ed19..1218bb095490d4a 100644 --- a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx +++ b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx @@ -9,7 +9,7 @@ date: 2025-05-29T00:00:00Z Users using Cloudflare's [REST API](/api/resources/d1/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the closest Cloudflare network data center that recieved the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core centralized centers, which added network round trips. -D1 query endpoints like `/query` and `/raw` have the most noticeable improvements since they no longer access Cloudflare's core data centers. D1 control plane endpoints such as those to create and delete databases see smaller improvements, since they still require access to Cloduflare's core data centers for other control plane metadata. +D1 query endpoints like `/query` and `/raw` have the most noticeable improvements since they no longer access Cloudflare's core data centers. D1 control plane endpoints such as those to create and delete databases see smaller improvements, since they still require access to Cloudflare's core data centers for other control plane metadata. Performance improvements apply to only the REST API. Users can now expect similar performance querying their database via the REST API and via a [Worker](/d1/best-practices/query-d1/#query-d1-with-workers-binding-api). From 3481dc28b4eb2548c742e397d2ba772f3bc37e3c Mon Sep 17 00:00:00 2001 From: Vy Ton Date: Thu, 29 May 2025 13:20:04 -0400 Subject: [PATCH 5/9] Update 2025-05-30-d1-rest-api-latency.mdx --- .../changelog/d1/2025-05-30-d1-rest-api-latency.mdx | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx index 1218bb095490d4a..5f5882a1ddc8c4f 100644 --- a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx +++ b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx @@ -1,5 +1,5 @@ --- -title: Faster D1 REST API +title: 50-500ms Faster D1 REST API Requests description: D1 REST API request latency improvements. products: - d1 @@ -9,7 +9,6 @@ date: 2025-05-29T00:00:00Z Users using Cloudflare's [REST API](/api/resources/d1/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the closest Cloudflare network data center that recieved the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core centralized centers, which added network round trips. -D1 query endpoints like `/query` and `/raw` have the most noticeable improvements since they no longer access Cloudflare's core data centers. D1 control plane endpoints such as those to create and delete databases see smaller improvements, since they still require access to Cloudflare's core data centers for other control plane metadata. - -Performance improvements apply to only the REST API. Users can now expect similar performance querying their database via the REST API and via a [Worker](/d1/best-practices/query-d1/#query-d1-with-workers-binding-api). +Latency improvements range from 50-500 ms depending on request location and [database location](/d1/configuration/data-location/) and only apply to the REST API. Users can now expect similar performance querying their database via the REST API and via a [Worker](/d1/best-practices/query-d1/#query-d1-with-workers-binding-api). +D1 query endpoints like `/query` and `/raw` have the most noticeable improvements since they no longer access Cloudflare's core data centers. D1 control plane endpoints such as those to create and delete databases see smaller improvements, since they still require access to Cloudflare's core data centers for other control plane metadata. From 762444eb4acb97fa68dbaefb0f76592f26d6a73a Mon Sep 17 00:00:00 2001 From: Vy Ton Date: Thu, 29 May 2025 13:20:40 -0400 Subject: [PATCH 6/9] typo fix --- src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx index 5f5882a1ddc8c4f..51eb68b75cb884f 100644 --- a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx +++ b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx @@ -7,7 +7,7 @@ products: date: 2025-05-29T00:00:00Z --- -Users using Cloudflare's [REST API](/api/resources/d1/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the closest Cloudflare network data center that recieved the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core centralized centers, which added network round trips. +Users using Cloudflare's [REST API](/api/resources/d1/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the closest Cloudflare network data center that received the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core centralized centers, which added network round trips. Latency improvements range from 50-500 ms depending on request location and [database location](/d1/configuration/data-location/) and only apply to the REST API. Users can now expect similar performance querying their database via the REST API and via a [Worker](/d1/best-practices/query-d1/#query-d1-with-workers-binding-api). From 405af18d65549000c88da9952b2f040d2b69a5be Mon Sep 17 00:00:00 2001 From: Vy Ton Date: Thu, 29 May 2025 13:45:45 -0400 Subject: [PATCH 7/9] Update 2025-05-30-d1-rest-api-latency.mdx --- src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx index 51eb68b75cb884f..b763c56b0f17db7 100644 --- a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx +++ b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx @@ -7,8 +7,8 @@ products: date: 2025-05-29T00:00:00Z --- -Users using Cloudflare's [REST API](/api/resources/d1/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the closest Cloudflare network data center that received the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core centralized centers, which added network round trips. +Users using Cloudflare's [REST API](/api/resources/d1/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the closest Cloudflare network data center that received the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core, centralized data centers, which added network round trips and latency. -Latency improvements range from 50-500 ms depending on request location and [database location](/d1/configuration/data-location/) and only apply to the REST API. Users can now expect similar performance querying their database via the REST API and via a [Worker](/d1/best-practices/query-d1/#query-d1-with-workers-binding-api). +Latency improvements range from 50-500 ms depending on request location and [database location](/d1/configuration/data-location/) and only apply to the REST API. REST API requests and databases outstide the United States see a bigger benefit since Cloudflare's primary core data centers resides in the United States. D1 query endpoints like `/query` and `/raw` have the most noticeable improvements since they no longer access Cloudflare's core data centers. D1 control plane endpoints such as those to create and delete databases see smaller improvements, since they still require access to Cloudflare's core data centers for other control plane metadata. From 2ee3d42d89ef5958396f9d72a547ea325207baf9 Mon Sep 17 00:00:00 2001 From: Vy Ton Date: Thu, 29 May 2025 13:48:16 -0400 Subject: [PATCH 8/9] Update 2025-05-30-d1-rest-api-latency.mdx --- src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx index b763c56b0f17db7..25f160f96cd1234 100644 --- a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx +++ b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx @@ -9,6 +9,6 @@ date: 2025-05-29T00:00:00Z Users using Cloudflare's [REST API](/api/resources/d1/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the closest Cloudflare network data center that received the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core, centralized data centers, which added network round trips and latency. -Latency improvements range from 50-500 ms depending on request location and [database location](/d1/configuration/data-location/) and only apply to the REST API. REST API requests and databases outstide the United States see a bigger benefit since Cloudflare's primary core data centers resides in the United States. +Latency improvements range from 50-500 ms depending on request location and [database location](/d1/configuration/data-location/) and only apply to the REST API. REST API requests and databases outstide the United States see a bigger benefit since Cloudflare's primary core data centers reside in the United States. D1 query endpoints like `/query` and `/raw` have the most noticeable improvements since they no longer access Cloudflare's core data centers. D1 control plane endpoints such as those to create and delete databases see smaller improvements, since they still require access to Cloudflare's core data centers for other control plane metadata. From c1b023447ba502c2ca395a5d6bfe0a3558e7936e Mon Sep 17 00:00:00 2001 From: Vy Ton Date: Thu, 29 May 2025 14:01:31 -0400 Subject: [PATCH 9/9] Update src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx Co-authored-by: Lambros Petrou --- src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx index 25f160f96cd1234..bb54cd0f3e7f087 100644 --- a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx +++ b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx @@ -9,6 +9,6 @@ date: 2025-05-29T00:00:00Z Users using Cloudflare's [REST API](/api/resources/d1/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the closest Cloudflare network data center that received the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core, centralized data centers, which added network round trips and latency. -Latency improvements range from 50-500 ms depending on request location and [database location](/d1/configuration/data-location/) and only apply to the REST API. REST API requests and databases outstide the United States see a bigger benefit since Cloudflare's primary core data centers reside in the United States. +Latency improvements range from 50-500 ms depending on request location and [database location](/d1/configuration/data-location/) and only apply to the REST API. REST API requests and databases outside the United States see a bigger benefit since Cloudflare's primary core data centers reside in the United States. D1 query endpoints like `/query` and `/raw` have the most noticeable improvements since they no longer access Cloudflare's core data centers. D1 control plane endpoints such as those to create and delete databases see smaller improvements, since they still require access to Cloudflare's core data centers for other control plane metadata.