Is there any performance (or other) impact on as worker as KV bindings/size increase? I'm about to j

Is there any performance (or other) impact on as worker as KV bindings/size increase? I'm about to jump from 1 to 3 KVs (each w/a preview) and while the count and the physical size of the KVs isn't that large now, I realized I didn't know if there was any impact on the worker for adding them. Is startup/response time increased? Are there any thresholds or other guidance around this?

dave•5/31/23, 4:40 PM

does

/*

/*

match /hello/whoami/hello/whoami?

dave•5/31/23, 4:45 PM

answer: looks like yes

JJFSIII Is there any performance (or other) impact on as worker as KV bindings/size incr...

Unsmart•5/31/23, 4:50 PM

From 1 -> 3 no. If you have like hundreds and hundreds of bindings then yes it can.

JFSIIIOP•5/31/23, 4:53 PM

Thanks! That was my intuition/assumption but I wanted to check. Does the number of entries, or disk size of the KVs have any effect on the worker or the read/write perf of the KV?

Unsmart•5/31/23, 4:53 PM

No it doesnt

UUnsmart No it doesnt

JFSIIIOP•5/31/23, 4:55 PM

ok, cool. Thanks again!

sdan•5/31/23, 5:30 PM

would be nice to have a "sort by requests in last 24 hours"

Screenshot_2023-05-31_at_10.29.53_AM.png

Chaika•5/31/23, 5:31 PM

it used to exist, in old workers unconverged

we've asked about it, hopefully will come back soontm

ItsWendell•5/31/23, 5:33 PM

Looking to build a system for sending reminders for open payments through push notifications, emails and potentially sms, thinking durable objects and alarms.

Any libraries, systems, readings that come to mind before designing this?

Felix || Flow-Like.com•5/31/23, 9:09 PM

has there been a change to how workers calculate initial cpu usage?

Felix || Flow-Like.com•5/31/23, 9:09 PM

my functions suddenly dont publish anymore

Felix || Flow-Like.com•5/31/23, 9:09 PM

just imports, nothing special, worked before

Felix || Flow-Like.com•5/31/23, 9:10 PM

+ didnt touch the imports

Felix || Flow-Like.com•5/31/23, 9:10 PM

if I runtime load them all via await import treeshaking wont work and the size will increase a lot...

Felix || Flow-Like.com•5/31/23, 9:11 PM

+ probably performance implications

Felix || Flow-Like.com•5/31/23, 9:19 PM

this either needs some good debugging utilities or serious rework.. suddenly all ci systems failing without reason is not great.

micromashor•5/31/23, 9:45 PM

is there any way to access bindings from the global scope?

Felix || Flow-Like.com•5/31/23, 9:47 PM

kind of

Felix || Flow-Like.com•5/31/23, 9:49 PM

let scoped : null | bindingType = null;

...
async fetch(env){
if(!scoped) scoped = env.whatever
}

let scoped : null | bindingType = null;

...
async fetch(env){
if(!scoped) scoped = env.whatever
}

Felix || Flow-Like.com•5/31/23, 9:50 PM

thats how I use the global scope for caching things

micromashor•5/31/23, 9:50 PM

micromashor•5/31/23, 9:51 PM

I'm doing a similar thing, but I was hoping there was a way I could prime the "cache" without waiting for the first request to inevitably miss

Felix || Flow-Like.com•5/31/23, 9:51 PM

should not make much of a difference with the cold start times of workers

micromashor•5/31/23, 9:52 PM

wdym? (haven't looked at performance numbers much)

Felix || Flow-Like.com•5/31/23, 9:54 PM

workers run on lightweight v8 containers (please correct me), not nodejs environments like lambda. Coldstart basically does not exist

Felix || Flow-Like.com•5/31/23, 9:55 PM

https://upstash.com/blog/aws-lambda-vs-cloudflare-workers

AWS Lambda vs Cloudflare Workers

Articles and tutorials on serverless technologies from Upstash and community

micromashor•5/31/23, 9:55 PM

yeah I noticed that

micromashor•5/31/23, 9:55 PM

Coldstart basically does not exist

more curious what you mean by this

Felix || Flow-Like.com•5/31/23, 9:56 PM

lambda can be very slow to boot

Felix || Flow-Like.com•5/31/23, 9:56 PM

cf workers are not

micromashor•5/31/23, 9:57 PM

oh you mean the time between when the request hits and the

fetch

fetch

handler starts executing?

Felix || Flow-Like.com•5/31/23, 9:57 PM

no I mean the first request

Felix || Flow-Like.com•5/31/23, 9:57 PM

cold start

micromashor•5/31/23, 9:57 PM

Felix || Flow-Like.com•5/31/23, 9:58 PM

lambda functions will stay active for some time, which is called warmstart. So the following invocations are way quicker

Felix || Flow-Like.com•5/31/23, 9:58 PM

workers also stay active for some time, not sure how long tho

Felix || Flow-Like.com•5/31/23, 10:00 PM

curl --request POST \
  --url https://search.tm9657.de/search \
  --header 'Content-Type: application/json' \
  --data '{
    "index": "movie",
    "term": "guardian"
}'

curl --request POST \
  --url https://search.tm9657.de/search \
  --header 'Content-Type: application/json' \
  --data '{
    "index": "movie",
    "term": "guardian"
}'

micromashor•5/31/23, 10:00 PM

here's my issue... I have a message on the front page of a website, which changes daily. I don't care if it gets changed when I redeploy, so I'm going to just store the message in a global. (I have to store it in a global because SQLite has no way to seed the RANDOMRANDOM function.) But I was hoping I could get the first database pull out of the way during worker startup.

Felix || Flow-Like.com•5/31/23, 10:01 PM

here you can test how long they will stay active. First request takes 400 - 800 ms, searches after that 40ms

micromashor•5/31/23, 10:02 PM

I'm not really worried about worker-related speeds as much as the latency of a database query

Felix || Flow-Like.com•5/31/23, 10:02 PM

you might be able to use the cache api for that or KV

Felix || Flow-Like.com•5/31/23, 10:02 PM

you will need to check that in their terms

Felix || Flow-Like.com•5/31/23, 10:03 PM

or R2 if the performance is ok for you

Felix || Flow-Like.com•5/31/23, 10:03 PM

cheaper for lots of reads