It should just be an instant drop off, like you are observing
It should just be an instant drop off, like you are observing
HIf you get it below the limit, then it should just be 0(minus TLS start/other stuff)
LWhen I deploy this is what I see, is the limit based on compressed or uncompressed? Seems its already under but maybe something is still sending it to cold storage since its close?
HCompressed. Just to be sure, are you paying for Workers atm?
Lyeah, enterprise and unbound
HWeird…
HYeah, not sure what else could be causing that
CThe other thing is about how your worker runs. If you use a route that specifies a specific path the magical cold start stuff can't work
Chttps://blog.cloudflare.com/eliminating-cold-starts-with-cloudflare-workers/
For now, this is only available for Workers that are deployed to a “root” hostname like “example.com” and not specific paths like “example.com/path/to/something.” We plan to introduce more optimizations in the future that can preload specific paths.Edit: If it's more then ~50ms then it sounds more like global scope then cold start not working though, tcp connect isn't that long
Chey, i'm creating a minimal email worker that's making a post request to a slack webhook. all good and working. the problem is i'm missing email body. i was looking for it on but is not there
UGitHub
An example of a worker that parses an email. Contribute to edevil/email_worker_parser development by creating an account on GitHub.
Caha, i see ty @Unsmart | Tech debt
Aevery time I deploy my worker the kv bindings is removed from my worker. I tried:
Cdoes email workers are supported in wrangler?
INot sure if it would be a matter of getting credit, but more that you can't run your own models on Workers AI yet.
LI tested with a simple proxy and same issue
LDoes this apply if I have it at root but add a query string?
Also what do you mean by global scope being an issue?
Also what do you mean by global scope being an issue?
MCan the automatic running of cloudflare worker code while I'm typing be turned off? I can't work like this when I get basic auth popups every split second and I dont see the advantage of my worker constantly running on each keypress when I can use the Send button anytime I need to run
HYou may be able to disable it in the settings, but otherwise, you can develop locally and push
MI dont see an option for this but I think I may have a workaround.. I have to cause a syntax error and then it doesnt run constantly
Mnevermind it still runs
BHi, I am having problem with r2 audio/video file uploaded via presigned URL (PutObjectCommand). It was being uploaded but when we are going to use it via signedUrl(GetObjectCommand) for transcription, file cannot be read for transcription. The get presigned and signed URL are generated through Workers. I tried to download it and played in media player, and still it was unable to play the file. Did I missed something in upload using presigned url ?
but when I upload the file directly in R2, then transcribed the file via signedUrl, the transcription service that we are using are successfully able to transcribed it
but when I upload the file directly in R2, then transcribed the file via signedUrl, the transcription service that we are using are successfully able to transcribed it
ZHey,
I'm currently trying to minimize latency as much as possible. I am currently using Cloudflare hyperdrive with my postgres db + a cloudflare kv cache for my entries, but I am still getting around 100ms latency. Is there any way to reduce this further? I am just running a simple select query and my return size is about 4KB. I attached an image of what my route looks like, and an image of what the respective latency for each operation is. I also attached an image for my db middleware to allow me to use my db in ever call. I know this is not very effective, but almost all my routes use a DB call anyway. Or is there any way to reuse an existing connection?
I'm currently trying to minimize latency as much as possible. I am currently using Cloudflare hyperdrive with my postgres db + a cloudflare kv cache for my entries, but I am still getting around 100ms latency. Is there any way to reduce this further? I am just running a simple select query and my return size is about 4KB. I attached an image of what my route looks like, and an image of what the respective latency for each operation is. I also attached an image for my db middleware to allow me to use my db in ever call. I know this is not very effective, but almost all my routes use a DB call anyway. Or is there any way to reuse an existing connection?
UI would remove the cache and remove the 2nd db connection that doesnt use hyperdrive and it should be faster 
Uand if theres some reason you really dont want to use hyperdrive for a specific route I would make it where you return only the hyperdrive connection or only the direct connection instead of opening both
ZWhy remove the cache? It seems to be much faster. Just trying to understand
Uhyperdrive already adds a cache so that would just double cache now
ZTrue, but for some reason the Hyperdrive cache is way slower. It adds about 80ms of latency
ZWould cloudflare D1 be better for my use case? I just want the lowest latency possible
ID1 would be lower latency in the location where it's created, but it's also SQLite (not Postgres) so anything Postgres specific won't work with D1.
DI am using photon-rs using WebAssembly, and the worker throws
Error 1102: Workers Resources Limit, I think it's due to CPU time limit. How can I check the cpu time taken by a fetch handler?
EHi, everyone. Sorry for bothering you, but I need your help
I hosted a static website using Cloudflare workers to optimize the performance
how can I increase the page speed? what should I do, like configuring or anything else?
I hosted a static website using Cloudflare workers to optimize the performance
how can I increase the page speed? what should I do, like configuring or anything else?
JI just switched to paid workers plan. Is there something like a safety limit or something, so I don't end up spending big money by a mistake, since it's paid on additional requests as-you-go?
CIf your site is purely static then I would recommend pages
UThere's no hard limits you can impose, setting up WAF rules to try and block any bot traffic and rate limiting rules to disallow spam would be things you can do to try and ensure expected usage levels.
Normally you could also setup notifications for when you reach a certain request amount but seems due to the billing changes recently made to workers you cannot do this yet with the updated billing model.
Normally you could also setup notifications for when you reach a certain request amount but seems due to the billing changes recently made to workers you cannot do this yet with the updated billing model.
CNuxtJS SSR worker, my code is fetching my dotnet endpoint in azure using a cloudflare origin certificate. I have strict TLS turned on and my nuxt worker is getting 522 errors on request to dotnet endpoint. Do i need to somehow get worker to do an origin pull? If i turn off strict TLS worker goes back to functional
Mhi I can't find the api to create a new worker https://developers.cloudflare.com/api/operations/worker-script-delete-worker ? how do i create a new worker from api. Thank
Interact with Cloudflare's products and services via the Cloudflare API
Emy website is the build of react. how to deploy it using pages
EReact is a popular framework for building reactive and powerful front-end applications, built by the open-source team at Facebook.
WWhat are your go to rest api framework for cf worker?
EPersonally I use Hono
WThanks! I’ll try to look at it
WStill a newbie with serverless concept
WDoes each api call invoke a function and each invocation spawn a worker, is it still preferable to write async?
WAnd how about service which have to wait for user input, let’s say an otp service.
- User hit api
- Api send otp via sms
- Api wait for 30 sec for user inputting otp
ZEach time a request is made to your worker, the fetch() function is ran with the request information. In workers, multiple requests can share the same isolate (the thing that actually runs the code). You should write workers using async because if you don't do that, you wont be able to do many operations, as they often require async.
I would re-frame the problem here as instead of having the server wait for the user to input the OTP, the server give the user a time limit of 30 seconds to enter the OTP. There are many ways you could do this. You could send the user a JWT that they need to send back that expires after 30 seconds, or you could store the login attempt in a datastore like #d1-beta or #durable-objects.
I would re-frame the problem here as instead of having the server wait for the user to input the OTP, the server give the user a time limit of 30 seconds to enter the OTP. There are many ways you could do this. You could send the user a JWT that they need to send back that expires after 30 seconds, or you could store the login attempt in a datastore like #d1-beta or #durable-objects.
WThanks! Now it’s more clear.
I just see durable object, it looks like redis cache
which I think suit the otp use case.
But the jwt method looks more interesting, how does it work? Isn’t jwt token is too long for otp which is usually only four to six digit?
I just see durable object, it looks like redis cache
which I think suit the otp use case.But the jwt method looks more interesting, how does it work? Isn’t jwt token is too long for otp which is usually only four to six digit?
EI believe whats being suggested is the user is presented with a jwt and then within 30 seconds they must return both the jwt and the totp code, which mitigates the need to maintain any state yourself