Cloudflare Developers•3y ago

When you say call the worker with a service binding does that bypass the sub request limit?

KKDX_MW | Kaddex.xyz / Ecko.xyz When you say call the worker with a service binding does that bypass the sub req...

DaniFoldi•12/17/23, 7:26 PM

kind of, but there's also a limit to how many times you can call the worker

KDX_MW | Kaddex.xyz / Ecko.xyzOP•12/17/23, 7:26 PM

So let’s say I have worked A which goes through my 4000 customers using the analytics engine and populates the KV pair. If I use a service binding from worker B to worker A and have the from on worker B would that bypass the limit?

DaniFoldi•12/17/23, 7:26 PM

it resets the 1000 limit, but there is also a 32 recursion limit, so you can't continue resetting indefinitely, and it also counts as another worker invocation

KDX_MW | Kaddex.xyz / Ecko.xyzOP•12/17/23, 7:27 PM

Got it so I could theoretically get up to 32,000 invocations in one go

KDX_MW | Kaddex.xyz / Ecko.xyzOP•12/17/23, 7:27 PM

Presuming I recursively called at the end

Constantin•12/18/23, 12:49 AM

is there a problem with workers deployment/dns

Constantin•12/18/23, 12:52 AM

the wroker is beeing deployed via wrangler having this config

{
    "compatibility_date": "2023-12-06",
    "main": "src/index.ts",
    "account_id": "1cca8d8eb0cc2de3f76e07b7164f222e",
    "placement": {
        "mode": "smart"
    },
    "env": {
        "main": {
            "name": "worker-app-proxy",
            "route": {
                "zone_id": "0ae46da72468555b0841b3615fc6f14e",
                "pattern": "*.app.nefele.ai/*"
            }
        }
    }
}

{
    "compatibility_date": "2023-12-06",
    "main": "src/index.ts",
    "account_id": "1cca8d8eb0cc2de3f76e07b7164f222e",
    "placement": {
        "mode": "smart"
    },
    "env": {
        "main": {
            "name": "worker-app-proxy",
            "route": {
                "zone_id": "0ae46da72468555b0841b3615fc6f14e",
                "pattern": "*.app.nefele.ai/*"
            }
        }
    }
}

all good, however there's no Worker DNS record, and the url is not reacheable

kian•12/18/23, 1:03 AM

Did you create a DNS record for that route?

kian•12/18/23, 1:03 AM

Workers won’t do that for you unless you’re using custom domains.

Constantin•12/18/23, 1:13 AM

yep, i did ..

CConstantin yep, i did ..

Chaika•12/18/23, 1:22 AM

Are you saying you have a wildcard on nefele.ai pointing to app.nefele.ai, and thus you expect it to work for

*.app.nefele.ai

*.app.nefele.ai

?
If so, wildcards are a bit fun with DNS. It'll stop if it hits anything, and stop on any deeper labels too. Meaning, your wildcard stops recursing because you have a record created for app.nefele.ai.
You'd have to create another wildcard record for

*.app.nefele.ai

*.app.nefele.ai

That's also too deep for your free Universal certificate which only covers first level subdomains, you'd need Advanced Cert Manager (ACM)

Advany•12/18/23, 10:34 AM

will there ever be a new version of the cloudflare apps? I really though it was a powerfull concept!

piffie•12/18/23, 11:26 PM

Hey guys, we are getting updates from around 4k pricepoints, typically around 30-40 per second.
I first thought about running a worker for this, then maybe to query.
But then i reread the durable object API - and it seems i would best actually handle it inside a durable object to hold the values in memory, and give it from there access to others. Whats the best architecture for that?

Unsmart•12/18/23, 11:27 PM

Youre going to have to explain a bit more about what you are looking for if you want anything useful. With only that limited info no one can suggest anything really.

its so over•12/19/23, 7:41 AM

is it possible to make udp connections from a worker

Iits so over is it possible to make udp connections from a worker

Hello, I’m Allie!•12/19/23, 7:42 AM

its so over•12/19/23, 7:42 AM

njhjh•12/19/23, 11:32 AM

Hi all

I am wondering about Sentry Tails Worker pricing. Will attaching Sentry mean that I will get all the requests and pricing doubled? Because Tail workers are priced the same as workers and are automatically invoked after the invocation of a producer Worker

jacob•12/19/23, 1:43 PM

While it's possible to get a user's ip country from a worker, is it possible to get the context of where the worker itself is being run? An api I'm quering has different base urls depending on location, ideally I'd wanna call the region closest to the worker when it's being run

Jjacob While it's possible to get a user's ip country from a worker, is it possible to ...

Isaac McFadyen•12/19/23, 1:46 PM

The only way is to hit a

/cdn-cgi/trace

/cdn-cgi/trace

endpoint and look for the

colo

colo

field. So for example, https://cloudflare.com/cdn-cgi/trace shows EWR and EWR = New York airport, so Worker is being run in New York.

Isaac McFadyen•12/19/23, 1:47 PM

But also it's probably not necessary. Workers run in every datacenter on the Cloudflare network (350+) which means it will almost always be run close to your user.

Isaac McFadyen•12/19/23, 1:47 PM

So if you use the user's country/region it's almost guaranteed to be near the Worker.

IIsaac McFadyen So if you use the user's country/region it's almost guaranteed to be near the Wo...

jacob•12/19/23, 1:48 PM

Thanks

Chaika•12/19/23, 2:11 PM

You could also just get request.cf.colo if you just wanted the datacenter in a Worker, doesn't work in DOs though

CChaika You could also just get request.cf.colo if you just wanted the datacenter in a W...

Isaac McFadyen•12/19/23, 2:29 PM

Oh yeah true lul

kian•12/19/23, 3:36 PM

Should be the original

kian•12/19/23, 3:36 PM

pages-discussions

sanetram•12/19/23, 4:42 PM

Hey, hopefully this is allowed, but would anyone be interested in me releasing this codegen tool for the fastest possible 0-dep routers?

sanetram•12/19/23, 4:44 PM

aim was to generate switch cases with string literals to use v8 parse-time optimisations. it's also meant to be readable so i'm not custom rolling any "few"-case minifications into if statements etc and move that to the bundler

juri•12/19/23, 6:51 PM

Does anyone have a reliable way to track timings inside of a worker? I am aware that

Date.now

Date.now

and

performance.now

performance.now

are only ever updated when I/O occurs, but how do you guys go about debugging internal latency issues?

juri•12/19/23, 6:52 PM

For example, if my worker is apparently doing some heavy internal work but you can't find out where, how would you go about that?

Jjuri For example, if my worker is apparently doing some heavy internal work but you c...

DaniFoldi•12/19/23, 6:57 PM

I'm not entirely sure because I've never tested this, but during local development if you open an inspector, do you not see accurate timing data there?

Jjuri Does anyone have a reliable way to track timings inside of a worker? I am aware ...

kian•12/19/23, 6:59 PM

Internal as in how does Cloudflare do it, or the community?

DDaniFoldi I'm not entirely sure because I've never tested this, but during local developme...

juri•12/19/23, 7:00 PM

Would you consider these numbers as "true" then?

juri•12/19/23, 7:01 PM

I think my issue is more about an operation inside of the worker taking longer than expected (parsing data, for example), which is not I/O so

Date.now

Date.now

is never updated.

Kkian Internal as in how does Cloudflare do it, or the community?

juri•12/19/23, 7:02 PM

Oh, internal as in code inside the worker taking a long time to execute — but at the same time not being able to identify what piece of code is responsible because comparing

Date.now

Date.now

inside the worker is not accurate.

kian•12/19/23, 7:04 PM

There isn't really a whole lot you can do. Timing with local development should be accurate, but not in remote development or when published.

juri•12/19/23, 7:06 PM

This will be really hard then, I assume. I unfortunately cannot use the worker locally as it requires being connected to a Dispatch Namespace and D1

DaniFoldi•12/19/23, 7:07 PM

yeah dispatch namespaces don't yet have support in local development, still in an early PR phase meowsad

Unsmart•12/19/23, 7:07 PM

I mean you can always pull out a test where you dont use dispatch namespaces and run it locally to test

DaniFoldi•12/19/23, 7:08 PM

of course you can perform an isolated test to check the timings there, but it's not the best developer experience

kian•12/19/23, 7:11 PM

Yeahhh. Measuring anything latency or CPU/RAM related is a dead end on Workers which sucks as eventually the only billing model is based on CPU runtime that you can only measure on a "whole Worker" basis using the analytics.

kian•12/19/23, 7:18 PM

Well, you can get accurate per-request CPU time if you feel like paying for Enterprise and using LogPush :^)

UUnsmart I mean you can always pull out a test where you dont use dispatch namespaces and...

juri•12/19/23, 7:21 PM

Unfortunately the whole process requires access to Dispatch Namespaces :/

Kkian Well, you can get accurate per-request CPU time if you feel like paying for Ente...

juri•12/19/23, 7:22 PM

We should most definitely have access to that, I have not used it before, I'll try out another solution I was proposed and will then check LogPush out!

Unsmart•12/19/23, 7:22 PM

a fetch to a dispatch namespace uses 0ms cpu time so you can figure out where your cpu usage is by taking out specific code blocks and trying to figure out what uses the most cpu there

Kkian Well, you can get accurate per-request CPU time if you feel like paying for Ente...

juri•12/19/23, 7:34 PM

How would you suggest to go about this? Send individual logs to LogPush at the desired spots? The idea is that LogPush then reveals the actual wall-clock times when the logs were pushed, correct?

kian•12/19/23, 7:35 PM

LogPush creates a log per request, you can't send anything to it

kian•12/19/23, 7:36 PM

That log can include WorkerCPUTimeWorkerCPUTime and WorkerWallTimeUsWorkerWallTimeUs

juri•12/19/23, 7:38 PM

Oh, I see, I also just read that when setting it up. But this is only the total of the request and not individual "checkpoints" I can track during code execution?

{ "compatibility_date": "2023-12-06", "main": "src/index.ts", "account_id": "1cca8d8eb0cc2de3f76e07b7164f222e", "placement": { "mode": "smart" }, "env": { "main": { "name": "worker-app-proxy", "route": { "zone_id": "0ae46da72468555b0841b3615fc6f14e", "pattern": "*.app.nefele.ai/*" } } } }

When you say call the worker with a service binding does that bypass the sub request limit?

Similar Threads

Similar Threads

Similar Threads