Skip to content

Clock-sync both sides of fetchHandler so handlerMs is real #1676

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
RhysSullivan merged 1 commit into from
Aug 18, 2026
Merged

Clock-sync both sides of fetchHandler so handlerMs is real #1676

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions apps/cloud/src/server.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -129,8 +129,14 @@ const fetchHandler = async (
): Promise<Response> => {
const wasWarm = startHandledInThisIsolate;
startHandledInThisIsolate = true;
// Sync the clock on BOTH sides. Without the trailing `scheduler.wait(0)`,
// a handler that performs no I/O leaves `Date.now()` pinned and reports
// 0ms for work that actually took seconds — which is exactly what the
// first run of this probe showed (handlerMs 0 against 6002ms wall).
await scheduler.wait(0);
const startedAt = Date.now();
const response = await rawFetchHandler(request, env, ctx);
await scheduler.wait(0);
const handlerMs = Date.now() - startedAt;
console.log(
JSON.stringify({
Expand Down
Loading