Skip to content

Deliver Postgres queue messages in process - #3322

Open
NathanColosimo wants to merge 2 commits into
nathanc/eager-flow-handler-initfrom
nathanc/postgres-direct-execution
Open

NathanColosimo wants to merge 2 commits into
nathanc/eager-flow-handler-initfrom
nathanc/postgres-direct-execution

Conversation

@NathanColosimo

@NathanColosimo NathanColosimo commented Aug 4, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Replace the Postgres World HTTP loopback with direct Graphile Worker delivery and start it only after each framework has registered the generated handler.

  • Register the Core queue handler and call it directly from the Graphile task.
  • Encode the existing queue message as JSON bytes instead of reconstructing HTTP requests and responses.
  • Initialize the generated handler before Next.js, SvelteKit, Astro, Nest, Nitro, and Nuxt start background workers.
  • Preserve the callable handler and its initialize property through framework wrappers.
  • Keep enqueue-only processes producer-only; workers start only after handler registration.
  • Remove the local World and Vercel Queue transport dependencies.
  • Return 404 from the generated flow route for every Postgres request, including ?__health.

Stored task names and message payloads remain compatible with queued work. WORKFLOW_LOCAL_BASE_URL no longer affects the Postgres World.

Refs #2658 #2656

Validation

  • @workflow/world-postgres: 195 passing tests
  • @workflow/core: 2,335 passing tests, 3 expected failures, 1 skipped
  • Nest, Nitro, and SvelteKit: 72 passing tests
  • Next.js webpack flow-route HMR fuzz test against a staged tarball workbench
  • Monorepo package build and typecheck

Stack created with GitHub Stacks CLI • Give Feedback 💬

@changeset-bot

changeset-bot Bot commented Aug 4, 2026 •

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 869e2e0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 17 packages
Name Type
@workflow/astro Patch
@workflow/nest Patch
@workflow/nitro Patch
@workflow/next Patch
@workflow/sveltekit Patch
@workflow/world-testing Patch
@workflow/world-postgres Patch
workflow Patch
@workflow/nuxt Patch
@workflow/core Patch
@workflow/builders Patch
@workflow/cli Patch
@workflow/vitest Patch
@workflow/web-shared Patch
@workflow/web Patch
@workflow/rollup Patch
@workflow/vite Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel

vercel Bot commented Aug 4, 2026 •

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
example-nextjs-workflow-turbopack Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
example-nextjs-workflow-webpack Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
example-workflow Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
workbench-astro-workflow Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
workbench-express-workflow Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
workbench-fastify-workflow Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
workbench-hono-workflow Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
workbench-nestjs-workflow Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
workbench-nitro-workflow Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
workbench-nuxt-workflow Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
workbench-python-workflow Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
workbench-sveltekit-workflow Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
workbench-tanstack-start-workflow Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
workbench-vite-workflow Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
workflow-docs Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
workflow-swc-playground Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
workflow-tarballs Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC
workflow-web Ready Ready Preview, v0 Sep 2, 2026 11:31pm UTC

@github-actions

github-actions Bot commented Aug 4, 2026 •

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

✅ All tests passed

⚠️ Flaky E2E Tests (passed on retry)

These tests failed at least once and passed on a retry. A recurring entry here is a real race worth investigating.

  • cancelRun via CLI - cancelling a running workflow (nextjs-turbopack)
  • cancelRun via CLI - cancelling a running workflow (nextjs-webpack)

🛠 Infra Events (absorbed by the harness)

Platform anomalies the e2e harness detected and worked around (e.g. a run the queue never picked up, replaced by a fresh run). Clustered timestamps indicate a backend blip; a steady drip indicates a platform issue worth escalating.

  • cold-start-warmup · suite warmup (tanstack-start) · at 23:31:11Z · abandoned wrun_01M1J7BSWQS4VV4KWKMJF340SN

E2E Test Summary

Summary
Passed Failed Skipped Total
✅ ▲ Vercel Production 3632 0 688 4320
✅ 💻 Local Development 3922 0 558 4480
✅ 📦 Local Production 3922 0 558 4480
✅ 🐘 Local Postgres 3922 0 558 4480
✅ 🪟 Windows 320 0 0 320
✅ 🌐 Cross-language Conformance 64 0 77 141
✅ vercel-http-transport 817 0 143 960
✅ vercel-multi-region 27 0 0 27
✅ vercel-ws-transport 553 0 87 640
Total 17179 0 2669 19848
Details by Category

✅ ▲ Vercel Production

App Passed Failed Skipped
✅ astro-node 132 0 28
✅ astro-quickjs 132 0 28
✅ example-node 132 0 28
✅ example-quickjs 132 0 28
✅ express-node 132 0 28
✅ express-quickjs 132 0 28
✅ fastify-node 132 0 28
✅ fastify-quickjs 132 0 28
✅ hono-node 132 0 28
✅ hono-quickjs 132 0 28
✅ nest-node 132 0 28
✅ nest-quickjs 132 0 28
✅ nextjs-turbopack-node 157 0 3
✅ nextjs-turbopack-quickjs 157 0 3
✅ nextjs-webpack-node 157 0 3
✅ nextjs-webpack-quickjs 157 0 3
✅ nitro-node 132 0 28
✅ nitro-quickjs 132 0 28
✅ nuxt-node 132 0 28
✅ nuxt-quickjs 132 0 28
✅ python-node 62 0 98
✅ sveltekit-node 151 0 9
✅ sveltekit-quickjs 151 0 9
✅ tanstack-start-node 132 0 28
✅ tanstack-start-quickjs 132 0 28
✅ vite-node 132 0 28
✅ vite-quickjs 132 0 28

✅ 💻 Local Development

App Passed Failed Skipped
✅ astro-stable-node 134 0 26
✅ astro-stable-quickjs 134 0 26
✅ express-stable-node 134 0 26
✅ express-stable-quickjs 134 0 26
✅ fastify-stable-node 134 0 26
✅ fastify-stable-quickjs 134 0 26
✅ hono-stable-node 134 0 26
✅ hono-stable-quickjs 134 0 26
✅ nest-stable-node 134 0 26
✅ nest-stable-quickjs 134 0 26
✅ nextjs-turbopack-canary-node 141 0 19
✅ nextjs-turbopack-canary-quickjs 141 0 19
✅ nextjs-turbopack-stable-node 160 0 0
✅ nextjs-turbopack-stable-quickjs 160 0 0
✅ nextjs-webpack-canary-node 141 0 19
✅ nextjs-webpack-canary-quickjs 141 0 19
✅ nextjs-webpack-stable-node 160 0 0
✅ nextjs-webpack-stable-quickjs 160 0 0
✅ nitro-stable-node 134 0 26
✅ nitro-stable-quickjs 134 0 26
✅ nuxt-stable-node 134 0 26
✅ nuxt-stable-quickjs 134 0 26
✅ sveltekit-stable-node 153 0 7
✅ sveltekit-stable-quickjs 153 0 7
✅ tanstack-start-node 134 0 26
✅ tanstack-start-quickjs 134 0 26
✅ vite-stable-node 134 0 26
✅ vite-stable-quickjs 134 0 26

✅ 📦 Local Production

App Passed Failed Skipped
✅ astro-stable-node 134 0 26
✅ astro-stable-quickjs 134 0 26
✅ express-stable-node 134 0 26
✅ express-stable-quickjs 134 0 26
✅ fastify-stable-node 134 0 26
✅ fastify-stable-quickjs 134 0 26
✅ hono-stable-node 134 0 26
✅ hono-stable-quickjs 134 0 26
✅ nest-stable-node 134 0 26
✅ nest-stable-quickjs 134 0 26
✅ nextjs-turbopack-canary-node 141 0 19
✅ nextjs-turbopack-canary-quickjs 141 0 19
✅ nextjs-turbopack-stable-node 160 0 0
✅ nextjs-turbopack-stable-quickjs 160 0 0
✅ nextjs-webpack-canary-node 141 0 19
✅ nextjs-webpack-canary-quickjs 141 0 19
✅ nextjs-webpack-stable-node 160 0 0
✅ nextjs-webpack-stable-quickjs 160 0 0
✅ nitro-stable-node 134 0 26
✅ nitro-stable-quickjs 134 0 26
✅ nuxt-stable-node 134 0 26
✅ nuxt-stable-quickjs 134 0 26
✅ sveltekit-stable-node 153 0 7
✅ sveltekit-stable-quickjs 153 0 7
✅ tanstack-start-node 134 0 26
✅ tanstack-start-quickjs 134 0 26
✅ vite-stable-node 134 0 26
✅ vite-stable-quickjs 134 0 26

✅ 🐘 Local Postgres

App Passed Failed Skipped
✅ astro-stable-node 134 0 26
✅ astro-stable-quickjs 134 0 26
✅ express-stable-node 134 0 26
✅ express-stable-quickjs 134 0 26
✅ fastify-stable-node 134 0 26
✅ fastify-stable-quickjs 134 0 26
✅ hono-stable-node 134 0 26
✅ hono-stable-quickjs 134 0 26
✅ nest-stable-node 134 0 26
✅ nest-stable-quickjs 134 0 26
✅ nextjs-turbopack-canary-node 141 0 19
✅ nextjs-turbopack-canary-quickjs 141 0 19
✅ nextjs-turbopack-stable-node 160 0 0
✅ nextjs-turbopack-stable-quickjs 160 0 0
✅ nextjs-webpack-canary-node 141 0 19
✅ nextjs-webpack-canary-quickjs 141 0 19
✅ nextjs-webpack-stable-node 160 0 0
✅ nextjs-webpack-stable-quickjs 160 0 0
✅ nitro-stable-node 134 0 26
✅ nitro-stable-quickjs 134 0 26
✅ nuxt-stable-node 134 0 26
✅ nuxt-stable-quickjs 134 0 26
✅ sveltekit-stable-node 153 0 7
✅ sveltekit-stable-quickjs 153 0 7
✅ tanstack-start-node 134 0 26
✅ tanstack-start-quickjs 134 0 26
✅ vite-stable-node 134 0 26
✅ vite-stable-quickjs 134 0 26

✅ 🪟 Windows

App Passed Failed Skipped
✅ nextjs-turbopack-node 160 0 0
✅ nextjs-turbopack-quickjs 160 0 0

✅ 🌐 Cross-language Conformance

App Passed Failed Skipped
✅ python 64 0 77

✅ vercel-http-transport

App Passed Failed Skipped
✅ example 132 0 28
✅ express 132 0 28
✅ hono 132 0 28
✅ nextjs-turbopack 157 0 3
✅ nitro 132 0 28
✅ vite 132 0 28

✅ vercel-multi-region

App Passed Failed Skipped
✅ nextjs-turbopack 27 0 0

✅ vercel-ws-transport

App Passed Failed Skipped
✅ example 132 0 28
✅ express 132 0 28
✅ nextjs-turbopack 157 0 3
✅ vite 132 0 28

📋 View full workflow run

@NathanColosimo

Copy link
Copy Markdown
Contributor Author

Local validation of the stack (PRs #3320–#3324 combined):

  • @workflow/world-postgres full suite: 168 passed (unit + shared real-Postgres world spec via testcontainers)
  • @workflow/world-testing embedded local-world suite: 15 passed
  • @workflow/core unit suites (runtime, trace-mode, world): green
  • Full packages/core/e2e/e2e.test.ts: 137/137 passed against a production next start of workbench/nextjs-turbopack built with WORKFLOW_TARGET_WORLD=@workflow/world-postgres — the graphile runner started at boot via instrumentation and every job executed in-process (no HTTP loopback; WORKFLOW_LOCAL_BASE_URL/port detection removed).

@NathanColosimo
NathanColosimo force-pushed the nathanc/postgres-direct-execution branch from ef018c8 to 814e1a4 Compare August 4, 2026 07:24
@github-actions

github-actions Bot commented Aug 4, 2026 •

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit 869e2e0 · Wed, 02 Sep 2026 23:51:12 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric Scenario Best (ms) P75 (ms) P90 (ms) P99 (ms) Samples
TTFS step 1265 (+552%) 🔻 1384 🔴 (+34%) 🔻 1416 🔴 (+24%) 🔻 1686 🔴 (+16%) 🔻 30
TTFS stream 221 (+49%) 🔻 1339 🔴 (+31%) 🔻 1414 🔴 (+37%) 🔻 1589 🔴 (+36%) 🔻 30
TTFS hook + stream 452 (+1.3%) 1600 🔴 (+11%) 1648 🔴 (-63%) 💚 1828 🔴 (-64%) 💚 30
Fan-out TTFS Promise.all(100 steps) 586 (-0.7%) 1955 (+161%) 🔻 2029 (+30%) 🔻 2107 (+24%) 🔻 10
Fan-out TTLS Promise.all(100 steps) 1810 (±0%) 3772 (+43%) 🔻 5396 (+76%) 🔻 8680 (+26%) 🔻 10
STSO 1020 steps (inline) 111 (+6.7%) 137 (+3.0%) 159 (+0.6%) 216 (-87%) 💚 1019
WO 1020 steps 136694 (-21%) 💚 136694 (-21%) 💚 136694 (-21%) 💚 136694 (-21%) 💚 1
CRTT first chunk (pooled) 62 (+19%) 🔻 103 (±0%) 149 (+16%) 🔻 438 (+108%) 🔻 28

Streams

Scenario CRTT 1st p75 p90 p99 CDV max iters
paced control (100/s, 60B) 81 (+4%) 157 (+23%) 310 (+44%) 618 (+47%) 168 (+15%) 10
size sweep (100/s, 160B-12KB) 87.5 (+2%) 178 (+30%) 223 (+9%) 403 (+14%) 148 (+3%) 10
replay gateway-gpt-5.4-nano-2000t (1x) 83 (-33%) 135 (+4%) 167 (-15%) 497 (+18%) 260 (+1%) 3
replay eve-gpt-5.6-sol-2000t (1x) 82 (-37%) 169 (+19%) 1212 (+205%) 4695 (+35%) 3596 (+72%) 2
replay eve-gpt-5.6-sol-2000t (2x) 149 (+45%) 187 (+11%) 234 (-4%) 341 (-41%) 254 (-9%) 3
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 172379ms → this run 135417ms (Δ -36962ms, -21%)

  100-150 ms  ██████████████████████┃█  main 873  this 853   -20
  150-200 ms  ███┃                      main 111  this 152   +41
  200-250 ms  ┃                         main   6  this  12    +6
  250-300 ms  ┃                         main   2  this   0    -2
  300-350 ms  ┃                         main   1  this   2    +1
 950-1000 ms  ┃                         main   1  this   0    -1
1000-1050 ms  ┃                         main   3  this   0    -3
1050-1100 ms  ┃                         main   1  this   0    -1
1100-1150 ms  ┃                         main   1  this   0    -1
1150-1200 ms  ┃                         main   1  this   0    -1
1250-1300 ms  ┃                         main   1  this   0    -1
1300-1350 ms  ┃                         main   1  this   0    -1
1350-1400 ms  ┃                         main   2  this   0    -2
1400-1450 ms  ┃                         main   1  this   0    -1
1500-1550 ms  ┃                         main   1  this   0    -1
1550-1600 ms  ┃                         main   2  this   0    -2
1650-1700 ms  ┃                         main   1  this   0    -1
1750-1800 ms  ┃                         main   2  this   0    -2
2000-2050 ms  ┃                         main   1  this   0    -1
2050-2100 ms  ┃                         main   2  this   0    -2
2100-2150 ms  ┃                         main   1  this   0    -1
2200-2250 ms  ┃                         main   1  this   0    -1
2250-2300 ms  ┃                         main   1  this   0    -1
2400-2450 ms  ┃                         main   1  this   0    -1
2550-2600 ms  ┃                         main   1  this   0    -1
📈 CRTT drill-down vs main (RTT distributions & profiles)
variant  RTT 1ms→5s+             avg         p50           p90          p99     n
control  ······▄█▂▁···  138.5 (+26%)  123 (+24%)    310 (+44%)   618 (+47%)  3000
sweep    ······▃█▂····  136.9 (+16%)  126 (+20%)     223 (+9%)   403 (+14%)  3000
gw 1x    ·····▁▅█▁▁···   119.6 (+7%)  110 (+12%)    167 (-15%)   497 (+18%)  5295
eve 1x   ·····▁▇█▁▁▁▂·    349 (+56%)   101 (-3%)  1212 (+205%)  4695 (+35%)  5186
eve 2x   ·····▁▃█▂····   141.7 (+1%)   124 (+4%)     234 (-4%)   341 (-41%)  7779

RTT over stream progress (avg per tenth of stream, bars scaled min→max):

control  ▅▄▃█▃▃▃▁▁▂  123–169ms
sweep    █▅▄▁▃▅▂▄▃▂  118–165ms
gw 1x    ▂▃▄▃▁▂▂▂▂█  104–161ms
eve 1x   ▁▁█▂▄▁▁▁▁▁  100–1617ms
eve 2x   ▆▂▂▃▁▁▆█▃▂  123–177ms

RTT by chunk size (avg per log size bin, ~160B → ~12KB serialized, bars scaled min→max):

sweep  ▁▃▅█▇▆▁  135–139ms

Delivery jitter over stream progress (avg positive CDV per tenth of stream, bars scaled min→max):

control  ▁▄▄▆▂█▃▄▂▄  33–44ms
sweep    █▆▅▁█▆▄▆▆▃  42–57ms
gw 1x    ▂▅▃▂▂▁▁▃▂█  30–45ms
eve 1x   ▂▂█▂▅▁▁▂▁▁  20–65ms
eve 2x   █▄▁▁▃▁▁▃▁▅  20–29ms
📜 Previous results (1)

2c85ee1

Wed, 02 Sep 2026 22:48:48 GMT · run logs

vercel / nextjs-turbopack

Metric Scenario Best (ms) P75 (ms) P90 (ms) P99 (ms) Samples
TTFS step 178 (-82%) 💚 1306 🔴 (+15%) 1333 🔴 (+13%) 1380 🔴 (+11%) 30
TTFS stream 197 (-69%) 💚 1185 🔴 (+5.8%) 1219 🔴 (+3.0%) 1734 🔴 (+36%) 🔻 30
TTFS hook + stream 547 (-59%) 💚 1538 🔴 (+6.7%) 1603 🔴 (+7.9%) 1663 🔴 (+9.2%) 30
Fan-out TTFS Promise.all(100 steps) 607 (-11%) 1960 (+8.7%) 1968 (-0.7%) 2090 (+1.3%) 10
Fan-out TTLS Promise.all(100 steps) 1726 (-24%) 💚 3951 (+4.7%) 4068 (-0.5%) 4446 (-47%) 💚 10
STSO 1020 steps (inline) 83 (-30%) 💚 141 (-18%) 💚 168 (-13%) 262 (+1.2%) 1019
WO 1020 steps 140591 (-18%) 💚 140591 (-18%) 💚 140591 (-18%) 💚 140591 (-18%) 💚 1
CRTT first chunk (pooled) 66 (-11%) 105 (-17%) 💚 120 (-20%) 💚 248 (+35%) 🔻 28

Streams

Scenario CRTT 1st p75 p90 p99 CDV max iters
paced control (100/s, 60B) 87.5 (-17%) 156 (-22%) 243 (-14%) 840 (-1%) 122 (-32%) 10
size sweep (100/s, 160B-12KB) 82 (-23%) 148 (-44%) 205 (-41%) 383 (-75%) 121 (-28%) 10
replay gateway-gpt-5.4-nano-2000t (1x) 101 (-17%) 139 (-27%) 178 (-40%) 321 (-60%) 276 (-50%) 3
replay eve-gpt-5.6-sol-2000t (1x) 99.5 (0%) 158 (-16%) 209 (-17%) 383 (-47%) 415 (-9%) 2
replay eve-gpt-5.6-sol-2000t (2x) 114 (-8%) 211 (-65%) 294 (-85%) 676 (-83%) 417 (+16%) 3
ℹ️ Metric definitions & methodology

Streams: first-chunk RTT (the stream-open path, before any buffering/backpressure), CRTT percentiles, and worst delivery stall (CDV max). Cells are medians across iterations; per-run values in the artifacts. No 🔴/🟢 marks until targets attach.

The collapsed STSO distribution section above buckets every step gap, split inline (same warm process — pure framework overhead) vs queue-hop (fresh process — dispatch, reinit, replay). █ = main, ┃ = this run, ░ = fill.

The collapsed CRTT drill-down: per-variant RTT histograms (fixed log bins, · = empty) and mean RTT/positive-CDV profile lines over stream progress and chunk size. Histograms, avgs, and profiles merge exactly across runs; p50–p99 are percentile-of-percentiles. Per-index rows live in the artifacts.

Best/P75/P90/P99 deltas compare against the most recent benchmark run on main at the time of this run. 🔻 flags a delta worse than +15%, 💚 one better than −15%.

Metrics — TTFS: time to first step body (in-deployment start() → first step body) · Fan-out TTFS: fan-out time to first step (in-deployment start() → first of the parallel step bodies to complete) · Fan-out TTLS: fan-out time to last step (in-deployment start() → last of the parallel step bodies to complete, i.e. when the Promise.all resolves) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · CRTT: chunk round-trip time (per-chunk write → read latency, one clock domain: deployment → stream backend → same deployment) · CDV: chunk delay variation / delivery jitter (inter-arrival gap minus inter-write gap per seq-adjacent pair; skew-free; the row is each run's MAX positive value, so one stall moves it)

Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · Promise.all(100 steps): 100 trivial no-op steps started together in a single Promise.all; Fan-out TTFS is the first of them to complete and Fan-out TTLS the last, both from the in-deployment clientStart, so their gap is the spread the runtime adds across the fan-out · paced control (100/s, 60B): the control: 300 tiny (~60B) deltas metronome-paced at 100/s — zero workload structure, so it reads the transport floor and flush cadence, and disambiguates transport-wide vs workload-specific when a replay row moves · size sweep (100/s, 160B-12KB): same pacing as the control with deltas padded in rotation across seven log-spaced sizes (~160B–12KB) — rotation decouples size from stream position, so it isolates whether chunk size causes latency · replay gateway-gpt-5.4-nano-2000t (1x): raw provider SSE cadence captured at the AI gateway boundary (gpt-5.4-nano, the most popular gateway model; per-token deltas p50 208B = the modal production chunk size), replayed exactly as measured — the typical customer's workload; its CDV is the typical customer's real delivery jitter · replay eve-gpt-5.6-sol-2000t (1x): a captured eve turn (gpt-5.6-sol, the most-used demanding eve model; ~2000 output tokens = production p50 turn length) replayed exactly as measured — eve's envelope protocol re-ships the cumulative message so sizes ramp 142B→13KB; the demanding outlier tenant's reality · replay eve-gpt-5.6-sol-2000t (2x): the same eve capture at 2x — the headroom/stress row; real fast-tier models emit the same chunk sizes at proportionally higher rate, so time compression is a faithful speed model · first chunk (pooled): every run's seq-0 RTT pooled across all stream scenarios — the first chunk precedes any workload differentiation, so pooling samples one shared stream-open path with exact percentiles

Replay cadences (semantic sha256) — eve-gpt-5.6-sol-2000t eaf22f5946e7c61f3c65c7006d550df180cfabd4e706254a09f22aec0cfb420d · gateway-gpt-5.4-nano-2000t 6f24ac518b6b83ff1d0e85a5fe78230db192716d66a7fc6b2fe022752001d041

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600

All timestamps are deployment-side; runs are triggered in-deployment, so the CI runner and api.vercel.com sit outside every measured window. TTFS = start() → first step body (includes dispatch + any cold start); Fan-out TTFS/TTLS = first/last step completion of one Promise.all from the same anchor (the gap is the runtime’s fan-out spread); STSO/WO between step bodies; CRTT inside the workflow (excludes the api.vercel.com read path).

Cold starts stay in the numbers (real bursty-workload latency, inflates P75+); Best is the warm floor.

@NathanColosimo
NathanColosimo force-pushed the nathanc/postgres-direct-execution branch from 3ba1592 to 15f7971 Compare September 1, 2026 22:04
@NathanColosimo NathanColosimo changed the title Execute Postgres queue jobs in-process, dropping the HTTP loopback Execute Postgres queue jobs in-process and remove the HTTP loopback Sep 1, 2026
@github-actions

github-actions Bot commented Sep 1, 2026 •

Copy link
Copy Markdown
Contributor

Sim World

Simulated world deterministic testing for races. Traces

🟠 world-sim scenario book — 1 fail of 41 total

fence=per-spec

scenario outcome events virt replay violations
✅ smoke-no-steps completed 3 0ms ok 0
✅ smoke-one-step completed 6 0ms ok 0
✅ hook-at-step-started completed 12 0ms ok 0
✅ hook-at-step-completed completed 12 0ms ok 0
✅ hook-at-hook-created completed 12 0ms ok 0
✅ deadline-hook-wins completed 7 1.0h ok 0
✅ deadline-expires completed 7 1.0h ok 0
✅ long-sleep completed 11 30.0d ok 0
✅ hook-never-arrives stalled 3 0ms skipped 0
✅ step-retries-twice completed 10 2.0s ok 0
✅ parallel-steps completed 9 0ms ok 0
✅ hook-on-execution-state completed 12 0ms ok 0
✅ peek-hook-before-branch completed 12 0ms ok 0
✅ peek-hook-after-branch completed 12 0ms ok 0
✅ peek-hook-at-registration completed 12 0ms ok 0
✅ race-hook-before-probe completed 12 0ms ok 0
✅ race-hook-after-probe completed 12 0ms ok 0
✅ race-duplicate-delivery completed 13 0ms ok 0
✅ attr-hook-before-step completed 11 0ms ok 0
✅ attr-hook-after-step completed 11 0ms ok 0
✅ attr-from-step-body completed 13 0ms ok 0
✅ fork-hook-after-timeout completed 14 1.0m ok 0
✅ fork-hook-before-timeout completed 14 1.0m ok 0
✅ count-hook-after-timeout completed 17 1.0m ok 0
✅ count-hook-before-timeout completed 20 1.0m ok 0
✅ stale-read-step-count-fork completed 20 1.0m ok 0
✅ stale-read-equal-step-counts completed 14 1.0m ok 0
✅ step-vs-step-fork completed 12 0ms ok 0
✅ step-vs-step-fork-fenced completed 12 0ms ok 0
✅ fence-catches-benign-direction completed 12 5ms ok 0
✅ in-flight-before-decision completed 17 1.0m ok 0
❌ in-flight-before-decision-counted completed 17 1.0m ok 0
✅ in-flight-after-decision completed 19 2.0m ok 0
✅ stale-read-step-count-fork-fenced completed 20 1.0m ok 0
✅ fork-hook-wins completed 13 1.0m ok 0
✅ fork-timeout-wins completed 13 1.0m ok 0
✅ unclaimed-payload-under-fork completed 17 1.0m ok 0
✅ claimed-payload-under-fork completed 17 1.0m ok 0
✅ writers-independent-step-bodies completed 12 0ms ok 0
✅ writers-scripted-tempo completed 12 0ms ok 0
✅ cancel-mid-step cancelled 7 0ms skipped 0

Full trace: world-sim.txt

@github-actions

github-actions Bot commented Sep 1, 2026 •

Copy link
Copy Markdown
Contributor
Framework Flow route Step reg. Framework output
hono 200.9 KiB (±0) 40.6 KiB (±0) 1.77 MiB (-430 B)
nextjs-turbopack 206.3 KiB (±0) 439 B (±0) 765.2 KiB (-556 B)
About these numbers

Sizes are gzip; parentheses show the change against main.
Flow route and Step reg. gate this job, on raw bytes rather than the gzip shown, at max(2%, 50.0 KiB). Framework output is informational.

869e2e0 · run

This branch was successfully deployed

18 active deployments
Preview – workflow-swc-playground — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – workflow-docs — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – example-nextjs-workflow-webpack — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – workbench-nuxt-workflow — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – example-nextjs-workflow-turbopack — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – workbench-tanstack-start-workflow — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – example-workflow — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – workbench-sveltekit-workflow — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – workbench-express-workflow — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – workbench-astro-workflow — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – workbench-vite-workflow — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – workflow-web — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – workflow-tarballs — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – workbench-fastify-workflow — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – workbench-hono-workflow — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – workbench-nitro-workflow — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – workbench-nestjs-workflow — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Preview – workbench-python-workflow — 869e2e09 Deployed Sep 2, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant