Blog post on all this eventually™️
Blog post on all this eventually
EWoohoo!
Jdon't you mean 
JCan someone help with this
WThe getAssetFromKV should map the asset to the hashed one.
@cherryjimbo is best to answer but I can try until he's around
What I'd recommend first is just passing in the request you're given rather than making a new one. So,
I also see in the docs for kv-asset-handler it'd also like waitUntil (though not sure why exactly) so maybe try to pass that in too.
Then unrelated, your error is trying to get the request from the request. That should just be
@cherryjimbo is best to answer but I can try until he's around
What I'd recommend first is just passing in the request you're given rather than making a new one. So,
getAssetFromKV({ request: req })I also see in the docs for kv-asset-handler it'd also like waitUntil (though not sure why exactly) so maybe try to pass that in too.
Then unrelated, your error is trying to get the request from the request. That should just be
event.url
HEither via API calls, or through a Worker Proxy.
ENo.. hopefully it is an entirely different experience.. 
And if you can do that, you should totally file a HackerOne bug bounty, and it would make you quite a nice bit of cash I am sure
And if you can do that, you should totally file a HackerOne bug bounty, and it would make you quite a nice bit of cash I am sure
ENo, I mean between different accounts. Two workers on the same account is absolutely no problem and is supposed to work
ENo worries, we are always here to help!
EYeah, you can't do that with the native KV namespace API. But you can use the API key through the Cloudflare API at https://api.cloudflare.com
ANevermind, this is not an issue with KV, instead this was an issue with how I'm sending the request to my worker.
WKV works by having central storage then on read caching the value at the PoP. So, a high initial read value is indeed expected and then it'll sit at ~10-25ms
Here's a graph of initial read times in a bunch of areas
Here's a graph of initial read times in a bunch of areas
WThat 110-150ms is the total request time or the KV read time?
WHow are you measuring that time though, is it for the entire request or are you doing a measurement of the KV read itself?
WSo yeah you're doing the whole request time, ok so a lot contributes to that. I'd check firstly what kind of response time is it to the PoP in general. So I'd hit /cdn-cgi/trace and see what the timings are like
Wyeah but hit your domain just do you don't get any special treatment
WSince ya know, Enterprise PoPs and such
WOk, so -40ms
WNow what does the script itself do?
WI mean the Worker script
Wwhat does it do?
WOh... interesting
WYeah I bet the API acts quite differently from Workers
WSo the API is in core servers, it doesn't work from the edge like Workers. So I bet the performance when using API vs Workers is just expected here
WWorker would be much faster
Wsince it can act from the edge and have that low read in that PoP
WYou wouldn't be charged a request for reading KV but you would be for the request itself if that's what you mean
