No, I think it's correct

When I did a dry run, it gave me this

and this

Oh huh, that's new...

At least it used to inline them

Yeah it's definitely new

I'm guessing the bundled gzip is stored in quicksilver in this case, and unzipped for cold starts, then kept alive

but I don't know enough about workerd

wait you can really save a .txt file and then just import it in your worker?

this would have been nice to know

yep you can 🙂

Heyo, are there any ways to help figure out why

Error: Script startup exceeded CPU time limit.

is happening? I understand the script startup is taking too long, but how can I measure it?

The script startup counts as all of the code that's happening outside of your request handler, i.e. in the global scope. Anything you're running there that can be done inside your fetch handler, I recommend moving

The startup includes parsing and running all code in the worker, correct?

It could also be the fault of libraries you're importing

The parsing yes, the running of code, not all. It's only the code outside your handler

Its not the import, the creation of the

agent

here:

Oh yeah, the agent is outside the handler

It's very possible that's doing it, yes

am I just out of luck with Cloudflare then?

FYI console.time isn't accurate at all AFAIA

Just move it inside your handler

but then wouldn't that put my handler over the 10ms?

200ms startup, 10ms handler. Correct?

That's cpu time, not wall time

Oh and the startup isn't CPU Time?

No

> but how can I measure it? You can't very well unfortunately. Observability for Workers is a pain point with DX right now. But yeah as @Skye mentions, the most common form of this is initialising things outside of the fetch handler. Your best option is to move it inside of the handler, and then if you really see a benefit, you can cache it on

globalThis

or something. I would heavily doubt it consumes much CPU time to be an issue just doing it inside the handler though.

That makes sense, let me try that!

this confuses so many people i think, i don't think the docs are very clear that startup time is measured in real ms not CPU