it works but it keeps saying Worker exceeded CPU time limit.
it works but it keeps saying Worker exceeded CPU time limit.
JWhen doing what?
Twhen I use the Unpdf package to extract the text from the pdf. maybe the CPU time for worker take long time to parse the whole pdf and extract the text
JRight.. if you're doing a lot of work you might exceed the limits
JTry splitting it up into tasks
LWill Worker to Worker communication (especially RPC Calls), be cheaper then normal Requests in the Future? I mean it's much less then a normal HTTP Request and should therefore be cheaper or not?
BIt will, they've said they're making it free I think
Bfor the request
HUnder the hood, Worker-to-Worker coms are via Capn'Proto messages, so it can't get much cheaper
Bcompute still costs, of course
B(I could be wrong, please correct me)
BI think I saw this in a tweet
LThanks for the quick answers. @HardlyWorkin' but it's still less then a Request from Outside of the Cloudflare Network.
LThe Request should be cheaper and compute time should still be charged ofc
HOh, like that. Thought you were talking about something else sorry
LI think it'll be cheaper otherwise no one would use the maybe announced Plugin Store ^^ bcs that would be hella expensive if i have like 10+ Plugins enabled
NWhich one is it?
Nnvm im blind
N10k a day = 300k/mo
B@sperand_io @elithrar @Cloudflare Two things here:
- We are working on (couldn't quite make it for this week) a change where when you call another Worker via a service binding, this won't be billed as a request. (so that pricing doesn't disincentivize breaking apart an app into many Workers) Coming soon.
4/5/24, 7:31 PM
BWe are working on (couldn't quite make it for this week) a change where when you call another Worker via a service binding, this won't be billed as a request
NOOOH NICE
LThats nice, ty
Bthe reason they can do this as far as I can tell is because they're colocating it
LThat will open up alot of possiblities actually
BRPC to another Worker (over a Service Binding) usually does not even cross a network. In fact, the other Worker usually runs in the very same thread as the caller, reducing latency to zero. Performance-wise, it’s almost as fast as an actual function call.
BYeah, so I think addresses the point about "they can't reduce it all the way" - with this architecture, it becomes super cheap
NIs workers AI free for beta models?
NOr am I misunderstanding.
IThat's correct, yes.
NSounds heavily profitable. I'm in.
JWhy does the queues documentation mention free tier of it's only available on the paid tier? And is there no free allowance on a paid plan? https://developers.cloudflare.com/queues/platform/pricing/
Cloudflare Docs
Cloudflare Queues requires the Workers Paid plan to use, but does not increase your monthly subscription cost.
SThere is a free tier inside the paid tier. So you need to subscribe to the $5 plan to get the free tier.
JAh that makes sense!
JI think what confused me was the splitting it into two columns. Really it's 1 tier but with 1mil inclusive operations
SYup! Should be renamed to "Included with subscription" or something like that
PHello! QQ, anybody here kjnows how to setup a scheduler worker trigger for it to run every 5 seconds? Thanks
CWorkers CRON/Scheduled Handler can only go down to per minute in granularity. If you need anything more specific, you'd need to use Durable Object Alarms or something else
Pgot it, i will look into that! Thanks
Jfeel like that's all going to be changing with the new RPC stuff..
Jlooking forward to some people making some videos / content about it
LIf you really want to dive deeper into that topic, I'd recommend some type of Microservices like one Worker (Service) for each set of Features
LThe new RPC Stuff will open up a lot of new Possibilities. You could have for example some kind of Worker before every Microservice that'll just call the Microservice via RPC and handle all the global Logic instead of adding a Set of global logic to every Micro Service
AI’ve noticed since the rollout of versions that I have no history for some metrics in the dashboard for workers that have had a deployment since the release of versions. Just a hockey stick for the latest version and nothing before that. Known issue?
AAnd I have “All deployed versions” selected. Maybe it’s just isolated to the Requests section, but I thought I saw it in several metrics earlier today.
DHi, so CF doesn't store worker logs? Looking at the docs I can only do real-time (tail them or dashboard tail) or create another worker? That then stores them whereever we have a DB to write to? Is this right? CF doesn't store logs / I can't view historical logs?
Jcorrect, you'll need to send them to a 3rd party service.. I've been experimenting with baselime recently
