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

D

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

K

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.

K

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...

J

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...

J

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!

U

UnsmartOP•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...

J

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?

K

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

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

K

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

That log can include

WorkerCPUTime

WorkerCPUTime

WorkerCPUTime

WorkerCPUTime and

WorkerWallTimeUs

WorkerWallTimeUs

WorkerWallTimeUs

WorkerWallTimeUs

J

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?

K

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

Correct, total of the request.

J

juri•12/19/23, 8:41 PM

Is the

TimestampMs

TimestampMs

TimestampMs

TimestampMs for every item inside the

Logs

Logs

Logs

Logs array wall-clock time or is it based on the same time

performance.now

performance.now

performance.now

performance.now/

Date.now

Date.now

Date.now

Date.now use?

K

kian•12/19/23, 8:43 PM

Same as performance/date

K

kian•12/19/23, 8:43 PM

There is nothing that provides accurate time for individual events in Workers that is available to non-employees.

J

juri•12/19/23, 10:59 PM

Another idea: could we use Workers Analytics Engine for this? When you call

writeDataPoint

writeDataPoint

writeDataPoint

writeDataPoint, I would expect it to insert data with a correct timestamp.

J

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

There must be some way to gather metrics inside of a worker reliably.

Jjuri There must be some way to gather metrics inside of a worker reliably.

K

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

It's intentionally not supposed to be possible.

K

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

https://developers.cloudflare.com/workers/learning/security-model/#step-1-disallow-timers-and-multi-threading

F

Fizzy Kombucha•12/19/23, 11:43 PM

i am trying to build a sveltekit SSR app that will be deployed to pages. in my app i'm using mongodb. I can't build the project because the workers runtime apparently expects node js apis to be imported with the syntax 'node:crypto'. i have no control over how the mongodb client does its imports. i have no idea how to fix this or proceed.
related issue: https://community.cloudflare.com/t/cloudflare-pages-not-compatible-with-node-modules/566178
https://developers.cloudflare.com/workers/runtime-apis/nodejs

i am building my svelte kit app with 'CF_PAGES=1 vite build'.

Cloudflare Community

Cloudflare Pages not compatible with Node modules

I am having an error when deploying a SvelteKit app that uses some Node.js packages in the server. I get this error in the logs: The package “path” wasn’t found on the file system but is built into node. Are you trying to bundle for node? You can use “platform: ‘node’” to do that, which will remove this error. So, where do I have to use “plat...

Node.js compatibility · Cloudflare Workers docs

Implemented Node.js runtime APIs and enablement instructions for your Worker project.

F

Fizzy Kombucha•12/19/23, 11:43 PM

getting a bunch of errors like:

> Using @sveltejs/adapter-cloudflare
Starting mongo...
✘ [ERROR] Could not resolve "dns"

    node_modules/.pnpm/mongodb@6.3.0/node_modules/mongodb/lib/sdam/srv_polling.js:4:20:
      4 │ const dns = require("dns");
        ╵                     ~~~~~

  The package "dns" wasn't found on the file system but is built into node. Are you trying to bundle
  for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "stream"

> Using @sveltejs/adapter-cloudflare
Starting mongo...
✘ [ERROR] Could not resolve "dns"

    node_modules/.pnpm/mongodb@6.3.0/node_modules/mongodb/lib/sdam/srv_polling.js:4:20:
      4 │ const dns = require("dns");
        ╵                     ~~~~~

  The package "dns" wasn't found on the file system but is built into node. Are you trying to bundle
  for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "stream"

> Using @sveltejs/adapter-cloudflare
Starting mongo...
✘ [ERROR] Could not resolve "dns"

    node_modules/.pnpm/mongodb@6.3.0/node_modules/mongodb/lib/sdam/srv_polling.js:4:20:
      4 │ const dns = require("dns");
        ╵                     ~~~~~

  The package "dns" wasn't found on the file system but is built into node. Are you trying to bundle
  for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "stream"

> Using @sveltejs/adapter-cloudflare
Starting mongo...
✘ [ERROR] Could not resolve "dns"

    node_modules/.pnpm/mongodb@6.3.0/node_modules/mongodb/lib/sdam/srv_polling.js:4:20:
      4 │ const dns = require("dns");
        ╵                     ~~~~~

  The package "dns" wasn't found on the file system but is built into node. Are you trying to bundle
  for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "stream"

F

Fizzy Kombucha•12/19/23, 11:44 PM

i've been scouring google and can't seem to find a solution. was hoping someone here would know

F

Fizzy Kombucha•12/19/23, 11:50 PM

welp it looks like i found my answer. mongodb simply won't work on workers

https://www.mongodb.com/community/forums/t/cloudflare-workers-integration-is-now-possible/226708/11

MongoDB Developer Community Forums

Cloudflare Workers integration is now possible

Hi @Alex_Bjorlig, We are working with Cloudflare on this still, however at the moment we are blocked as Atlas requires TLS for all connections, however Cloudflare Workers only supports mTLS at the moment (and TLS cannot be disabled in Altas).

K

kian•12/20/23, 1:49 AM

nodejs_compat

nodejs_compat

nodejs_compat

nodejs_compat relies on them using the

node:

node:

node:

node: prefix when importing &

node_compat

node_compat

node_compat

node_compat are just best-effort polyfills.

K

kian•12/20/23, 1:49 AM

Puppeteer won't work in Workers unless you're using Cloudflare's fork with #browser-rendering-api-beta

F

Fizzy Kombucha•12/20/23, 1:51 AM

yea it really sucks. i built a small app with mongodb. was running it all locally and everything works fine. then i go to actually build and deploy it... now i have to swap out mongo for another db

K

kian•12/20/23, 1:55 AM

Workers can't spawn subprocesses or have a filesystem, so I don't think Puppeteer would ever work anyways.

K

kian•12/20/23, 1:55 AM

#browser-rendering-api-beta is a fork that talks to a remote browser hosted elsewhere on CF's infra

K

kian•12/20/23, 1:58 AM

You'd use CF's Puppeteer fork and pass it the binding, which then controls the remote browser.

K

kian•12/20/23, 1:58 AM

https://developers.cloudflare.com/browser-rendering/get-started/screenshots/#5-code

K

kian•12/20/23, 2:05 AM

What are you trying to do?

S

SSDD•12/20/23, 10:16 AM

can we turn off caching in cf workers?

Z

zegevlier•12/20/23, 10:25 AM

Worker responses aren't cached, what are you referring to?

Zzegevlier Worker responses aren't cached, what are you referring to?

S

SSDD•12/20/23, 10:30 AM

I have a worker deployed.. which executes graphql requests, it fetches data from other website which takes 1-3 secs.

1st request takes around the expected time but after that it's always ~300ms response time

S

SSDD•12/20/23, 10:32 AM

and I do not have any type of caching in the code that I deployed

Z

zegevlier•12/20/23, 10:44 AM

300ms seems very slow if it was actually caching the worker responses. Perhaps the GraphQL server your code is contacting is caching it?

M

mukhtharcm•12/20/23, 10:44 AM

Quick question #urgent

the daily limit of 100k request is a hard limit?

will the worker fail after that?

Z

zegevlier•12/20/23, 10:44 AM

Yup, hard limit.

Z

zegevlier•12/20/23, 10:45 AM

https://developers.cloudflare.com/workers/platform/limits/#daily-request

Zzegevlier Yup, hard limit.

M

mukhtharcm•12/20/23, 10:46 AM

Okk

Zzegevlier 300ms seems *very* slow if it was actually caching the worker responses. Perhaps...

S

SSDD•12/20/23, 12:28 PM

I don't code is caching.. ig I can put manual delay for each response to see if cf is caching

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

Similar Threads

Similar Threads

Similar Threads