i need something like 4-8 seconds behind at most

was thnking to use the DO

maybe all reqs to the DO and it builds the cache

if cache misses back to do

KV is faster usually, but it's guaranteeing a 60s average.

yea with KV my results wer mixed

like the sam region i was seeing often around 10s

I was imagining that the data was stored in the Durable Object and then you'd have an edge worker that would load the data from the DO into the cache, then return the cache to that user accessing the data.

Wouldn't that reduce egress costs?

Definitely. Higher latency on first requests, though.

Yeah, but in vans' use case, with the delay of 4-8 seconds then there should be enough time to touch the cache to make it hot and reduce the latency at each colo that will need it.

The Cache is instant per colo, so once it's filled all subsequent requests can use it, it's just per colo.

HLS video 2 second segments are not allowed in cache tho right?

Why not?

Just make sure to be polite and set the cache expiration reasonably.

(For Cloudflare and end users.)

ah i dont know i thought video had to use the cloudflare streams

what is reasonable expiration like 2h or 24h?

Sorry I forgot 1 important point on the KV testing, this was an update to existing key. I forgot to test the speed of inserting new key that DNE, i think it was much faster.

If it's live video, 30 seconds to 2 minutes. If not live video, sort of depends on your use case. Keep in mind you need to remove the video data from the Durable Object too or it will build up. I have not heard of any limitations for use for video but maybe someone at Cloudflare could answer. Cloudflare Stream is really good for automating multi-quality encoding and takes care a lot of the process for you.

A new key, on KV, is instant in the same colo, up to 60s on all others (usually way less). Updates same thing.

This was clearly not the case on updates on my testing, thru multiple times refreshing the page and hitting the same worker. (I doubt I was jumping around colos every refresh, I have a fiber line)

Yea live video. The idea behind the DO was it could be the source of truth, so always it will have the most recent data, up to say like 30 sec of video. Whatever fits in mem, 30sec should fit unless it's some h264 6k video, could be based on mem vs time. Then as requests come in for hls segments, hit the cache if cache miss hit the DO and subsequently fill the cache

The cache should prob get filled on ingestion actually

On https://github.com/cloudflare/durable-objects-template it says > On your first publish, you must use

wrangler publish --new-class Counter

to allow the Counter class to implement Durable Objects. but the latest wrangler doesn't like it:

error: Found argument '--new-class' which wasn't expected, or isn't valid in this context

Is this outdated advice?

You need the pre-release version of wrangler: https://github.com/cloudflare/wrangler/releases/tag/v1.16.0-durable-objects-rc.0

that version specifically? It says that version or later and I'm on 1.16.1

ok, it is just that particular version

For what it's worth I have Google Fiber and my requests appear to come out of the Google network all over North America, it's pretty wild