kv takes too long to take affect

[fickle ferry]

send me a dm so i send you my website to see what i mean

[old ether]

Support AI

Hey 👋

It seems there may not be enough information in your post to effectively get support from the community. Please ensure you include as much as possible, you can check the channel guidelines for some examples of what kind of information to include.

This is an AI generated response, it may not be 100% accurate. Please validate the output. You can ask followups by replying to this message or mentioning me.

[opaque imp]

KV is eventually consistent with a one minute cache TTL.

So you can see the old content for up to a minute after it was changed, this is expected.

[fickle ferry]

previously it wasn't like that. can i change that?

@opaque imp

[opaque imp]

It has always been like this.

[fickle ferry]

and i can't configure it to not have a cache?

[opaque imp]

No.

Don't use KV, use a different product like D1.

[fickle ferry]

the reason i use kv is kv is edge, unlike d1

[opaque imp]

The only reason it's "edge" is because of the cache.

[fickle ferry]

oh, makes sense

[opaque imp]

KV is only backed by two regions, in US and EU.

[fickle ferry]

so is there any edge kv/db offered by cloudflare?

[opaque imp]

One that runs in all 300+ datacenters at the same time? No...

[fickle ferry]

i also remember d1 at some point to have been faster than it is right now

[opaque imp]

Placebo.

[fickle ferry]

https://developers.cloudflare.com/kv/api/write-key-value-pairs/#create-expiring-keys

does this not help 🤔

[opaque imp]

I don't see how that related to the cache.

That deletes the entire key, not the cache.

[fickle ferry]

expirationTtl: 0

[opaque imp]

Not related to cache.

[fickle ferry]

ok

[opaque imp]

https://developers.cloudflare.com/kv/api/read-key-value-pairs/#cachettl-parameter