JS is likely to be faster for HTTP request processing. The benefit of Wasm is usually in heavy, off-

JS is likely to be faster for HTTP request processing. The benefit of Wasm is usually in heavy, off-request compute or where you want to use non-JS libraries/code

MMatt Silverlock JS is likely to be faster for HTTP request processing. The benefit of Wasm is us...

Gytis•7/31/23, 1:48 PM

yeah, thats what im thinking as well, I just dont have numbers to prove it. I might end up doing some benchmarks myself

kian•7/31/23, 2:03 PM

The WASM performance hits are usually when you’re doing any large copying of data between the WASM <-> JS boundary. Since the stringref proposal isn’t stabilised yet, strings are always copied rather than a reference being passed.

kian•7/31/23, 2:04 PM

Unless it’s a large workload, I doubt there’ll be differences other than a few milliseconds (if that)

Gytis•7/31/23, 10:38 PM

yep, thats what I am thinking. I think the only place where one may see any difference is cost. I am not sure if I should expect it to be higher or lower for such case
Anyways, I will write up a benchmark someday to play around with it. Im just curious

Tin Cap•8/3/23, 8:58 PM

I just switched a short algorithm from JS to WASM. My worker was taking about 3.5ms before and after.

Tin Cap•8/3/23, 8:59 PM

I was worried that invoking the WASM runtime would have a big performance impact but I didn't see it.

leostera•8/4/23, 2:09 PM

hey folks! has someone implemented simple locks with kv? for implementing a synchronized monotonic counter

kian•8/4/23, 2:15 PM

KV is eventually consistent so I'm not too sure it fits your use-case

kian•8/4/23, 2:15 PM

Writes take some time to propagate, reads are cached, etc

leostera•8/4/23, 2:31 PM

hmm. good point.

Lleostera hey folks! has someone implemented simple locks with kv? for implementing a sync...

DaniFoldi•8/4/23, 2:32 PM

#durable-objects are much more suited for that - with KV the best you could do (not recommended) is to write a key on each request, and then list them 1000 at a time to count (again, not recommended, not scalable, just a way to abuse KV into what you want)

leostera•8/4/23, 2:32 PM

cool! will look into this

leostera•8/4/23, 2:33 PM

thanks @Dani Foldi @kian !

Kkian KV is eventually consistent so I'm not too sure it fits your use-case

leostera•8/4/23, 2:46 PM

hmm are there any replication guarantees? like writes are replicated in the same order?

leostera•8/4/23, 2:46 PM

like if i find the key i’m looking for, every key i’ve written before will appear in a kv prefix scan

Lleostera hmm are there any replication guarantees? like writes are replicated in the same...

Hello, I’m Allie!•8/4/23, 3:02 PM

There is not

Ee0 Hello! I'm developing a SvelteKit application hosted on Cloudflare Pages and am ...

itsmatteomanf•8/4/23, 10:52 PM

Are you thinking of saving each sequence to a KV key?

itsmatteomanf•8/4/23, 10:52 PM

Ok, so a read-heavy kind of design is perfect for KV (as long as the value is <25MiB, which seems the case here).

itsmatteomanf•8/4/23, 10:53 PM

You'd need to be ok with a short propagation delay once the sequence updates.

Ee0 Thank you for replying! Since I always need to get all of the sequences at once,...

itsmatteomanf•8/4/23, 11:56 PM

Ok, then a single store makes sense.

itsmatteomanf•8/4/23, 11:57 PM

A Worker is better the smaller it is, even though the script is limited to 10MB so it would be fine, keeping it under 1MB would be ideal.

itsmatteomanf•8/4/23, 11:57 PM

Do note you are limited to 50 (or 1000 in Unbound) fetches per request, so 7500 wouldn't even work.

itsmatteomanf•8/4/23, 11:58 PM

A single KV key would be the way I'd go, personally.

itsmatteomanf•8/4/23, 11:58 PM

R2 might work, too, but it's slower on average and it requires more processing. D1 is not yet GA, but also costs per data processed.

itsmatteomanf•8/4/23, 11:58 PM

DOs are not worth it here.

matt•8/5/23, 12:25 AM

Hi all

does KV have something like Redis LRANGE?

matt•8/5/23, 1:51 AM

actually DO's look amazing for this use case. will give that a try

HHello, I’m Allie!There is not

leostera•8/6/23, 3:49 PM

but would fetching specific keys force replication?

Unsmart•8/6/23, 4:07 PM

Writes are replicated when you write and its just a last writer wins and if there happens to be a mismatch between the data sometimes the read can push through a replication fix where it chooses one. But you are also only supposed to write once per second to a specific key so if your use case involves higher write throughput than that you probably should not be using KV.

TigersWay•8/6/23, 11:32 PM

Could someone confirm that the dashboard numbers (operations) are for the last 24 hours but the limits are counted from 0:00 UTC?
Thanks

TigersWay•8/6/23, 11:38 PM

And if true, do we have anyway to know what have been used during the last period(s) / 0:00 - 23:59 UTC?

Murder Chicken•8/7/23, 1:19 PM

Is there any way to bulk fetch KV values in a single request from a worker?

TTigersWay And if true, do we have anyway to know what have been used during the last perio...

Cyb3r-Jak3•8/7/23, 1:34 PM

You should be able to use the GraphQL API to get that data

UUnsmart Writes are replicated when you write and its just a last writer wins and if ther...

leostera•8/7/23, 5:38 PM

i'm actually only writing once per key, but every now and then I'll need to write N things and a summary of what those N things are, like this:

entries = [
  {id: `entry:1`, body: "..."},
  {id: `entry:2`, body: "..."},
  {id: `entry:3`, body: "..."},
]
summary = { id: `summary:1`, entries: [`entry:1`, `entry:2`, `entry:3`] }

entries = [
  {id: `entry:1`, body: "..."},
  {id: `entry:2`, body: "..."},
  {id: `entry:3`, body: "..."},
]
summary = { id: `summary:1`, entries: [`entry:1`, `entry:2`, `entry:3`] }

leostera•8/7/23, 5:40 PM

what I still need to try is if the following read pattern will force replication of all the entries in the summary:

let summary = await fetchSummary(`summary-1`);
for entry in summary.entries {
  let entry = await fetchEntry(entry);
}

let summary = await fetchSummary(`summary-1`);
for entry in summary.entries {
  let entry = await fetchEntry(entry);
}

leostera•8/7/23, 5:47 PM

In the docs I also saw this:

One pattern is to send all of your writes for a given KV key through a corresponding instance of a Durable Object

but i'm not sure how this would look like in code?

leostera•8/7/23, 6:00 PM

yes

leostera•8/7/23, 6:00 PM

immutable as well

leostera•8/7/23, 6:00 PM

so there may be subsequent rquests to summary:1summary:1 but it will never change once its written

leostera•8/7/23, 6:00 PM

(same for entry:1entry:1, 2, 3, etc)

leostera•8/7/23, 6:01 PM

cool!

leostera•8/7/23, 6:01 PM

will give this a shot soon

leostera•8/7/23, 6:01 PM

thanks @skye_31!

jax•8/7/23, 10:47 PM

I made a VSCode extension to interface with KV right from VSCode that y'all might like. Has some benefits over the web UI like the a single uniform interface for Local, Preview, and Production environments, and the ability to view and edit metadata and expiration times. Anyways, it's free. https://marketplace.visualstudio.com/items?itemName=jaaxxx.cloudflare-vscode-devtools

Cloudflare KV (unofficial) - Visual Studio Marketplace

Extension for Visual Studio Code - Interface with Cloudflare products (for now just KV, more to come?)

JS is likely to be faster for HTTP request processing. The benefit of Wasm is usually in heavy, off-

Similar Threads

Similar Threads

Similar Threads