fast global replication also a must, i remember a couple of years ago reading that KV was up to 30 s

fast global replication also a must, i remember a couple of years ago reading that KV was up to 30 seconds, but there was a performance release a few months ago right?

mattOP•2/18/25, 1:39 AM

oh boyo, that 30 seconds is now 60 seconds :\

mattOP•2/18/25, 1:40 AM

what is cloudflare kv used for? I thought it was intended to be a redis-like db, but the performance profile is too detached from what redis offers

Mmatt fast global replication also a must, i remember a couple of years ago reading th...

Isaac McFadyen•2/18/25, 2:33 AM

It's always been 60 seconds except for a short time during a rollout that ended up being rolled back.

Isaac McFadyen•2/18/25, 2:33 AM

KV is primarily designed for read-heavy workloads that rarely write.

Isaac McFadyen•2/18/25, 2:34 AM

For example, KV backs Cloudflare Pages and Workers Assets, where you deploy a site infrequently but people access often and quickly.

Isaac McFadyen•2/18/25, 2:35 AM

KV caches at your nearest colo (that's why the 60 second limit), and future reads during the time it's cached will be very low-latency.

Mmatt low-latency batch reads (eg. HMGET) would be a requirement

Chaika•2/18/25, 3:12 AM

not a thing currently but they talked about doing stuff for it recently: kv

Mmatt fast global replication also a must, i remember a couple of years ago reading th...

Chaika•2/18/25, 3:14 AM

worth keeping in mind along with what Isaac said, KV doesn't replicate as much as it does cache: https://developers.cloudflare.com/kv/concepts/how-kv-works/
Two Central stores, US and EU, all the colos/data reads are behind cache and cacheTtl. It's not actively pushing, they're pulling

Cloudflare Docs

How KV works · Cloudflare Workers KV

KV is a global, low-latency, key-value data store. It stores data in a small number of centralized data centers, then caches that data in Cloudflare's data centers after access.

nukely•2/24/25, 6:03 PM

Which is faster and has lower latency for random reads/writes: KV or D1?

Nnukely Which is faster and has lower latency for random reads/writes: KV or D1?

Isaac McFadyen•2/24/25, 6:20 PM

Likely KV because it's cached much more heavily than d1 (D1 is single-location), but updates may take up to 60s to be visible globally.

o7•2/28/25, 7:08 AM

I racked up 700K (free plan) delete operations testing worst case cleanup operations, then 1.27M with a paid plan.
The paid plan includes 1M deletes, so will I be charged fractionally for 270k deletes? Or rounded up to $5?

o7•2/28/25, 7:09 AM

Also is delete performance irrelevant if the key exists or not? I was deleting blank keys via the bulk api since it returned successful_key_countsuccessful_key_count regardless

FaustKreationen•3/2/25, 12:17 PM

hey Devs! I am bit confused with KV- encryption. The doc's are pretty clear data are encrypted on rest and transit. But when sending a new entry via Wrangler the value can be read and editetd without any encryption in the dashboard? I am planing to store API keys in KV so a encryption is necessary. I am pretty sure i am missing something?

Walshy•3/2/25, 12:27 PM

Yeah, it's encrypted when stored and during transit. However, users should still be able to see their data so it's unencrypted before it's given back to you

I'd recommend encrypting yourself if you want to better control when the values are visible to you.

FaustKreationen•3/2/25, 12:29 PM

thank you! I will do so

saitharun•3/3/25, 4:50 PM

We're experiencing consistently high latency (~1000ms) when using the Cloudflare KV REST API for basic key-value operations in our authentication flow. This seems excessive compared to the expected performance of KV storage.

Our implementation uses standard API calls following your documentation:

GET/PUT to https://api.cloudflare.com/client/v4/accounts/{account_id}/storage/kv/namespaces/{namespace_id}/values/{key}https://api.cloudflare.com/client/v4/accounts/{account_id}/storage/kv/namespaces/{namespace_id}/values/{key}
Authentication via X-Auth-Email and X-Auth-Key headers
Small data payloads (<2KB)

Is this latency (1 second) expected behavior for the REST API endpoint? If not, are there known optimizations, best practices, or alternative approaches you'd recommend to reduce this latency to more reasonable levels for an authentication system?

Ssaitharun We're experiencing consistently high latency (~1000ms) when using the Cloudflare...

Isaac McFadyen•3/3/25, 4:51 PM

Rest API latency is fairly expected because the REST API is located in a few core locations and all requests must travel through those locations before hitting the end service.

Isaac McFadyen•3/3/25, 4:51 PM

In the case of KV, a lot of the benefits come because of the caching done at the edge colos where the data is retrieved from, which doesn't happen with the REST API either iirc

Isaac McFadyen•3/3/25, 4:52 PM

Your best bet might be creating a Worker that uses the KV binding (even if it's a single Worker that just services a similar API as the REST API does)

saitharun•3/3/25, 4:53 PM

What's the most efficient way to access Cloudflare KV from a Python backend application?

Ssaitharun What's the most efficient way to access Cloudflare KV from a Python backend appl...

Hard@Work•3/3/25, 4:53 PM

Write a Worker that implements an API for you to call

HHard@Work Write a Worker that implements an API for you to call

saitharun•3/3/25, 4:54 PM

Thanks. Let me check.

o7•3/5/25, 6:23 AM

~~KV listing in the dashboard seems to be broken?~~

~~namespaceId: 1febbc2176164bb28d7cd90ab661e8621febbc2176164bb28d7cd90ab661e862~~

edit: the only fix was recreating the namespace

o7•3/5/25, 6:27 AM

~~all these list ops come from a few minutes at the dashboard~~

Castio•3/5/25, 10:33 PM

hey everyone, I have a nextjs app that is a worker. I also have a binding for KV ready. How can I use it directly with binding in the app? KV store in NextJs App I decribed it in more details here

zegevlier•3/6/25, 10:11 PM

I don't think it's possible to do that. If your worker only does KV reads/writes, perhaps turning off the routes there could be a solution?

zegevlier•3/6/25, 10:12 PM

If your worker does more, I don't really have a good solution for you :/

1984 Ford Laser•3/6/25, 10:16 PM

Put auth on the Worker so a bad actor can't access it?

1984 Ford Laser•3/6/25, 10:17 PM

Per user rate limiting of some kind then perhaps

1984 Ford Laser•3/6/25, 10:23 PM

What do you mean? You said you wanted to avoid KV reads
Something like this depending on how much effort you want to go to: https://developers.cloudflare.com/durable-objects/examples/build-a-rate-limiter/

1984 Ford Laser•3/6/25, 10:40 PM

Then you'd need to implement something client-side, which doesn't render my suggestion useless, just wouldn't be using Workers to do so

1984 Ford Laser•3/6/25, 10:43 PM

:bye:

OOSC if they're simply pinging the site via a command line tool, which seems to be th...

boop•3/6/25, 10:51 PM

ICMP doesn't invoke your worker if that's what you're implying

OOSC That's good to know. But was more thinking along the lines of a bad actor will b...

boop•3/6/25, 10:53 PM

I figured as much, was a just-in-case

1984 Ford Laser•3/6/25, 10:55 PM

How is your site hosted, on CF with Workers/Pages? What is the KV storing, and how is the client-side accessing it?

1984 Ford Laser•3/6/25, 10:58 PM

Sounds like you need to host the site on Static Assets which would be free unlimited requests if you are serving static HTML files

1984 Ford Laser•3/6/25, 10:59 PM

Could you store in D1 for way more reads?

1984 Ford Laser•3/6/25, 10:59 PM

What is the data on the pages?

fast global replication also a must, i remember a couple of years ago reading that KV was up to 30 s

Similar Threads

Similar Threads

Similar Threads