hey everyone, is KV durable? can I rest assured stored content will persist indefinitely?
hey everyone, is KV durable? can I rest assured stored content will persist indefinitely?
HAssuming that you don’t overwrite it, yes
CAlso assuming that you pay the bill every month lol, but yes, durable
Bthanks
戴guys i have a hono project , when i tried to get a kv key but return null even though already binding, it work fine when in cli too, didn tknow why this happen
戴i with pumpkin guy can help me LOL
I?pings
SPlease do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.
KI really want to use kv, but the cold read latency is kinda killing me. For context, I am starting an API gateway service for API provides (similar to something like an API marketplace), and I use KV to store config details about the API and the end user. KV is god tier when I load test with tons of reqs / sec, but for more realistic scenarios of bursted requests at a smaller scale, I am getting P90 of ~300ms which is just not feasible. Would love to stay on Cloudflare services such as D1, but Upstash Redis seems like a good fix. Any thoughts?
EHow often does that data change? The ttl property on get requests may help.
KNot often but only thing is data changes should be reflected quickly (e.x certain api key gets banned, don’t want to wait super long)
SHello, only based on object TTL; i.e. after you update a value, the safest is to purge after max TTL defined for your objects + some small buffer.
IFollowing is my Question and Answer(given by ChatGPT)
Please confirm / update the Answer given by ChatGPT. Thanks.
QUESTION :
In the following Cloudflare Worker Code to List by Prefix .. how will the billing happen ? .. billing only for the Keys which are read and correspond to prefix or billing for complete scan of the KV namespace ?
export default {
async fetch(request, env, ctx) {
const value = await env.NAMESPACE.list({ prefix: "user:1:" });
return new Response(value.keys);
},
};
ANSWER by CHATGPT :
In Cloudflare Workers, billing for KV operations depends on the specific API calls and the data retrieved. Here's how the billing works for your provided code:
Please confirm / update the Answer given by ChatGPT. Thanks.
QUESTION :
In the following Cloudflare Worker Code to List by Prefix .. how will the billing happen ? .. billing only for the Keys which are read and correspond to prefix or billing for complete scan of the KV namespace ?
export default {
async fetch(request, env, ctx) {
const value = await env.NAMESPACE.list({ prefix: "user:1:" });
return new Response(value.keys);
},
};
ANSWER by CHATGPT :
In Cloudflare Workers, billing for KV operations depends on the specific API calls and the data retrieved. Here's how the billing works for your provided code:
- KV List API Billing
- The
operation is billed based on the number of keys returned that match theKV.list()
filter, not the total number of keys in the namespace.prefix - The filtering by
is handled internally by Cloudflare, so the operation scans only the relevant part of the namespace that matches the specifiedprefix
.prefix
- List Operation: Each call to
counts as a single read operation, regardless of the number of keys returned.list() - Key Retrieval: You are billed for each key returned in the
array. If thevalue.keys
operation retrieves 10 keys, it will count as 10 read operations.list()
- Assume
returns 50 keys.NAMESPACE.list({ prefix: "user:1:" }) - You are billed for:
- 1 list operation (base cost for calling the
method).list() - 50 read operations (one for each key returned in the result).
- 1 list operation (base cost for calling the
- You are not billed for scanning or evaluating keys that do not match the
. The filtering happens on Cloudflare's side, and only matching keys are returned and billed.prefix
list()
MHello, does the expiration set at the key creation persists if I put on the key without specifying expiration?
ME.g in this code:
SNo, it does not inherit the expiration settings of the previous overwritten object.
�Requests from around the world, pretty higher than expected
IQQ : Can "Storage" for "Workers KV per Namespace" store 200GB of data ? .. Limits section says "Unlimited", but still want this to be confirmed .
THey folks. We're designing a new feature for Workers KV to make it easier to retrieve multiple kv pairs at once. I'd love to get some feedback on some early designs. If you're up for it, snag 15 minutes on my calendar and I'll share with you some of the things we're thinking (or DM me) https://calendar.app.google/ABB6TtNyg7jPg82j8
森Scheduled! First time doing this, would it be on discord?
Jhi qq -- im trying to convert a largely kv-based lookup metadata of ~7GB in size of json and gets 10+ GB in size later with parallel reads, updates. Metadata needs persistence storage for consistency and availability too.
My metadata has 10M+ entries where each entry is a small dict of mostly nested strings of a loose schema, mixed with floats.
Is this size a good use case for cloudflare kv? thanks!
My metadata has 10M+ entries where each entry is a small dict of mostly nested strings of a loose schema, mixed with floats.
Is this size a good use case for cloudflare kv? thanks!
ASorry for the cross-post. I asked this in workers before I knew about this channel.
Are values written to KV automatically compressed for storage?
Are values written to KV automatically compressed for storage?
Ihow much is "expirationTtl (option in Workers-KV)" reliable ? .. i mean, if ttl is set for 10-minutes, can i expect the key to deleted after 10-minutes ? or what error margin need to be taken in consideration ?
IBrilliant. Thanks for confirmation.
IQQ : if i use get(my_key) after expiration/expirationTTL .. i shall be getting "null" / "undefined" as returned value ?
1It will be
null
CWhat's the difference between expirationTtl vs cachettl ?
CIf I use for example:
expirationTtl: 21600 or it will be cached by default?
CexpirationTtl: after this time, the key (and thus its value) will be gone forever
cacheTtl: Cache it x long, to reduce cold requests to KV's Central Stores, but of course also impacts how quickly you'll see updates if you do delete/update it
cacheTtl: Cache it x long, to reduce cold requests to KV's Central Stores, but of course also impacts how quickly you'll see updates if you do delete/update it
CcacheTtl is 60 seconds minimum. If you don't set it, it'll be 60s.
CIf I have a key which won't change till I manually delete it, I normally use
I guess it would help a lot to also add cacheTtl: 21600, right?
cache will be delete when I delete the key manually?
expirationTtl: 21600I guess it would help a lot to also add cacheTtl: 21600, right?
cache will be delete when I delete the key manually?
CFor example I do:
Pit isn't clear to me, that if cacheTtl is absent what happens - is the default min of 60 seconds applied, or is it no cache what so ever?
Wdefault 60s yeah
JThat looks like a bug. You may want to file an issue at https://github.com/cloudflare/cloudflare-docs/issues
Chey there, any wrapper around KV to easly query thinks?
JWhat kind of wrapper are you looking for? The KV bindings in Workers work really well, for example to read values: https://developers.cloudflare.com/kv/api/read-key-value-pairs/
JWas there an issue you hit or some use-case or workflow where you think a wrapper for something would be helpful?
Cwell, i'm looking for a more orm like .. thing; i'm using KV to store objects, that have some relations stored via metadata
Ci was just wondered if there's something out there that simplifies this, by adding some syntax sugar
Cbut probably using prefix, would make more sense
Mwould KV be a good replacement for upstash redis?
Mlow-latency batch reads (eg. HMGET) would be a requirement
Mfast global replication also a must, i remember a couple of years ago reading that KV was up to 30 seconds, but there was a performance release a few months ago right?
Moh boyo, that 30 seconds is now 60 seconds :\
Mwhat is cloudflare kv used for? I thought it was intended to be a redis-like db, but the performance profile is too detached from what redis offers