Date.now()?

V

Varna•4/25/24, 1:11 PM

thought about that too

but maybe it would be better to use smth like

crypto.randomUUID()

crypto.randomUUID()

crypto.randomUUID()

crypto.randomUUID(), or maybe I'm overthinking this

V

Varna•4/25/24, 3:13 PM

I wanted to test if

expirationTtl

expirationTtl

expirationTtl

expirationTtl works by setting it's value to 70 (seconds).
It did set it to

expiration: 1716649322

expiration: 1716649322

expiration: 1716649322

expiration: 1716649322 on

KV.list()

KV.list()

KV.list()

KV.list() response which is 18:02 (8 minutes ago).
Is it purged at batches on some intervals, or do I need to do that manually?
Or is this normal if I had a long

cacheTtl

cacheTtl

cacheTtl

cacheTtl.

V

Varna•4/25/24, 4:40 PM

It started working :catjam:

Oom What is this? Curious 🤔 what are you doing

R

Rubi•4/27/24, 3:00 PM

it's sveltekit middleware to check if a request to a path group is authorized or not

Oom Device id is just user agent?

R

Rubi•4/27/24, 3:02 PM

a session id inside a header

Oom D1 with index would be cheaper then D0

R

Rubi•4/27/24, 3:03 PM

I'm finding DO Alarm are harder to use inside sveltekit, I don't know how, it's need a class and something

Oom D1 with index would be cheaper then D0

R

Rubi•4/27/24, 3:03 PM

I may gonna stick with KV for the session, and the DB... I just moved it to neon

Oom Do alarm for? Deleting expired session?

R

Rubi•4/27/24, 3:05 PM

yes

Oom DO needs separate workers to be deployed, apart from pages not inside page

R

Rubi•4/27/24, 3:06 PM

yeah, I really don't understand, why the way we use it can't be just like D1, or KV

Oom If stored in kv unless you do mapping with database you can't track the session ...

R

Rubi•4/27/24, 3:11 PM

yes, they key are mapped with database

Oom Use D1 with workers cron

R

Rubi•4/27/24, 3:12 PM

I think I'm gonna keeping things simple and traditional

Oom With this you don't need mapping or alarms. Just delete it periodically with clo...

R

Rubi•4/27/24, 3:20 PM

aren't this is bad? because D1 single threaded? so it will execute one by one by one an CRUD action?

I read it from here and it makes me afraid to use D1:

d1-database

Oom Unless you are making 1000 request per second you should not be worried, maybe t...

R

Rubi•4/27/24, 8:47 PM

the response time for 128rps INSERT is actually fine, interesting...

T

tskuzzy•4/30/24, 9:54 PM

If I'm storing structured data in KV, is it better to stick it into metadata or to (de)serialize it as JSON in the value?

T

tonytheonly•5/3/24, 2:08 AM

Anyone else having issues updating KV?

T

tonytheonly•5/3/24, 2:10 AM

what gets logged in my console:

         await c.env.KV_CAMPAIGN.put(campaign.id, JSON.stringify({
            ...campaign
        }));
        const kv = await c.env.KV_CAMPAIGN.get(campaign.id)
        console.log("UPDATED KV",kv)

         await c.env.KV_CAMPAIGN.put(campaign.id, JSON.stringify({
            ...campaign
        }));
        const kv = await c.env.KV_CAMPAIGN.get(campaign.id)
        console.log("UPDATED KV",kv)

         await c.env.KV_CAMPAIGN.put(campaign.id, JSON.stringify({
            ...campaign
        }));
        const kv = await c.env.KV_CAMPAIGN.get(campaign.id)
        console.log("UPDATED KV",kv)

         await c.env.KV_CAMPAIGN.put(campaign.id, JSON.stringify({
            ...campaign
        }));
        const kv = await c.env.KV_CAMPAIGN.get(campaign.id)
        console.log("UPDATED KV",kv)

T

tonytheonly•5/3/24, 2:10 AM

is not what I see when I refresh / go to the KV store in cloudflare

U

Unsmart•5/3/24, 2:11 AM

KV is eventually consistent

T

tonytheonly•5/3/24, 2:12 AM

eventually?

U

Unsmart•5/3/24, 2:13 AM

yes, it means data is cached and replicated so it may take some time for the data to be updated

C

Chaika•5/3/24, 2:13 AM

https://developers.cloudflare.com/kv/reference/how-kv-works/

V

Varna•5/3/24, 11:10 AM

(new Blob([{ question: "is this correct way to measure if I fit in 1024bytes for KV metadata?" }])).size

(new Blob([{ question: "is this correct way to measure if I fit in 1024bytes for KV metadata?" }])).size

(new Blob([{ question: "is this correct way to measure if I fit in 1024bytes for KV metadata?" }])).size

(new Blob([{ question: "is this correct way to measure if I fit in 1024bytes for KV metadata?" }])).size

C

CalBoy•5/3/24, 11:47 AM

Does anyone know if it's possible to get the TTL of a key with a get? ie I've put an entry into the KV with a TTL i then want to check how much longer on it's TTL it has?

CCalBoy Does anyone know if it's possible to get the TTL of a key with a get? ie I've pu...

B

Beny•5/3/24, 6:18 PM

You can see the expiration time by using

env.KV.list({ prefix: key, limit: 1 })

env.KV.list({ prefix: key, limit: 1 })

env.KV.list({ prefix: key, limit: 1 })

env.KV.list({ prefix: key, limit: 1 })

R

Rich•5/9/24, 11:48 AM

We've been using the Cache API to cache sub-requests for a while and have found that because some of our sites are relatively low traffic, cache entries get evicted all the time so it offers minimal benefit.

We're looking at trying out KV store to cache subrequests instead, but I've read that cold reads can be very slow and I'm concerned even the KV store's colo / regional / central tier caches will get evicted just as aggressively as the Cache API does.

Does anybody know if KV caches are stickier than the Cache API?

RRich We've been using the Cache API to cache sub-requests for a while and have found ...

H

Hello, I’m Allie!OP•5/9/24, 12:07 PM

KV caching is the Cache API under the hood, iirc

HHello, I’m Allie!KV caching is the Cache API under the hood, iirc

R

Rich•5/9/24, 12:46 PM

I did wonder that but the docs suggest it takes advantage of tiered caching which the Cache API doesn't

Data must be read from the nearest regional tier, followed by a central tier, degrading finally to the central store for a truly cold global read

R

Rich•5/9/24, 12:50 PM

The way the docs describe it, I was hoping the KV Store would act similarly to Tiered Caching and Cache Reserve -- neither of which you get with the Cache API

RRich I did wonder that but the docs suggest it takes advantage of tiered caching whic...

C

Chaika•5/9/24, 1:18 PM

the docs are wrong, they were updated to talk about KV 2.0 (or whatever you want to call it), but that was reverted and pulled back

C

Chaika•5/9/24, 1:21 PM

they pulled the blog post too, this is what KV 2.0 was supposed to be: https://web.archive.org/web/20230701095201/https://blog.cloudflare.com/faster-workers-kv-architecture/

C

Chaika•5/9/24, 1:22 PM

we raised an issue about getting those docs reverted a while ago but I guess nothing came of it

C

Chaika•5/9/24, 1:24 PM

(but regardless, the way the current kv works is just per location cache and then one of the central stores. KV's cache is also slower by ~20ms or so then normal cache api I've noticed, not sure what it is exactly under the hood but it behaves pretty much the same as the cache api besides the slowness)
here's the older doc which reflects the current released version of kv: https://web.archive.org/web/20230520041620/https://developers.cloudflare.com/workers/learning/how-kv-works/

K

kian•5/9/24, 1:30 PM

I imagine that the KV cache is implemented in KV's Worker, so you still have to go talk to that

K

kian•5/9/24, 1:30 PM

idk why else it'd be slower :blobhaj_thonk:

Kkian I imagine that the KV cache is implemented in KV's Worker, so you still have to ...

C

Chaika•5/9/24, 1:30 PM

yea but that wouldn't be 20-30ms slower just to talk to a worker one would think

K

kian•5/9/24, 1:34 PM

If Date.now() for IO is to be believed, my Worker fetching a Hello World Worker takes about 15-25ms

Similar Threads

Similar Threads

Similar Threads