Skip to content

Conversation

@ijjk
Copy link
Member

@ijjk ijjk commented Feb 12, 2026

No description provided.

@changeset-bot
Copy link

changeset-bot bot commented Feb 12, 2026

⚠️ No Changeset found

Latest commit: 75e1cab

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

@vercel
Copy link
Contributor

vercel bot commented Feb 12, 2026

@github-actions
Copy link
Contributor

github-actions bot commented Feb 12, 2026

🧪 E2E Test Results

Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 490 0 38 528
✅ 💻 Local Development 508 0 68 576
✅ 📦 Local Production 463 0 65 528
❌ 🐘 Local Postgres 337 126 65 528
✅ 🪟 Windows 45 0 3 48
❌ 🌍 Community Worlds 12 42 3 57
✅ 📋 Other 123 0 21 144
Total 1978 168 263 2409

❌ Failed Tests

🐘 Local Postgres (126 failed)

nextjs-turbopack-stable (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

nextjs-webpack-canary (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

nextjs-webpack-stable (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router
🌍 Community Worlds (42 failed)

turso (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production
App Passed Failed Skipped
✅ astro 44 0 4
✅ example 44 0 4
✅ express 44 0 4
✅ fastify 44 0 4
✅ hono 44 0 4
✅ nextjs-turbopack 47 0 1
✅ nextjs-webpack 47 0 1
✅ nitro 44 0 4
✅ nuxt 44 0 4
✅ sveltekit 44 0 4
✅ vite 44 0 4
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 41 0 7
✅ express-stable 41 0 7
✅ fastify-stable 41 0 7
✅ hono-stable 41 0 7
✅ nextjs-turbopack-canary 45 0 3
✅ nextjs-turbopack-stable 45 0 3
✅ nextjs-webpack-canary 45 0 3
✅ nextjs-webpack-stable 45 0 3
✅ nitro-stable 41 0 7
✅ nuxt-stable 41 0 7
✅ sveltekit-stable 41 0 7
✅ vite-stable 41 0 7
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 41 0 7
✅ express-stable 41 0 7
✅ fastify-stable 41 0 7
✅ hono-stable 41 0 7
✅ nextjs-turbopack-stable 45 0 3
✅ nextjs-webpack-canary 45 0 3
✅ nextjs-webpack-stable 45 0 3
✅ nitro-stable 41 0 7
✅ nuxt-stable 41 0 7
✅ sveltekit-stable 41 0 7
✅ vite-stable 41 0 7
❌ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 41 0 7
✅ express-stable 41 0 7
✅ fastify-stable 41 0 7
✅ hono-stable 41 0 7
❌ nextjs-turbopack-stable 3 42 3
❌ nextjs-webpack-canary 3 42 3
❌ nextjs-webpack-stable 3 42 3
✅ nitro-stable 41 0 7
✅ nuxt-stable 41 0 7
✅ sveltekit-stable 41 0 7
✅ vite-stable 41 0 7
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 45 0 3
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
✅ redis-dev 3 0 0
✅ turso-dev 3 0 0
❌ turso 3 42 3
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 41 0 7
✅ e2e-local-postgres-nest-stable 41 0 7
✅ e2e-local-prod-nest-stable 41 0 7

📋 View full workflow run


Some E2E test jobs failed:

  • Vercel Prod: success
  • Local Dev: success
  • Local Prod: failure
  • Local Postgres: failure
  • Windows: success

Check the workflow run for details.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 12, 2026

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 0.032s (+25.3% 🔺) 1.005s (~) 0.973s 10 1.00x
💻 Local Nitro 0.032s (-4.2%) 1.004s (~) 0.972s 10 1.01x
💻 Local Next.js (Turbopack) 0.041s (~) 1.005s (~) 0.964s 10 1.29x
🐘 Postgres Express 0.418s (+324.0% 🔺) 1.035s (+2.5%) 0.618s 10 13.17x
🐘 Postgres Nitro 0.460s (+250.3% 🔺) 1.017s (+0.6%) 0.557s 10 14.52x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 0.671s (-26.3% 🟢) 1.879s (-16.1% 🟢) 1.208s 10 1.00x
▲ Vercel Nitro 0.839s (+10.1% 🔺) 2.217s (-2.1%) 1.378s 10 1.25x
▲ Vercel Express 1.041s (+18.5% 🔺) 2.578s (+18.4% 🔺) 1.538s 10 1.55x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.091s (-1.2%) 2.004s (~) 0.913s 10 1.00x
💻 Local Nitro 1.104s (-0.6%) 2.005s (~) 0.901s 10 1.01x
💻 Local Express 1.107s (+3.0%) 2.006s (~) 0.899s 10 1.01x
🐘 Postgres Express 2.263s (-8.5% 🟢) 3.014s (~) 0.751s 10 2.07x
🐘 Postgres Nitro 2.380s (-2.7%) 3.015s (~) 0.635s 10 2.18x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.469s (-12.8% 🟢) 3.303s (-15.6% 🟢) 0.834s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.522s (-13.4% 🟢) 3.461s (-13.7% 🟢) 0.939s 10 1.02x
▲ Vercel Express 2.800s (-1.3%) 3.596s (-15.0% 🟢) 0.796s 10 1.13x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 10.713s (~) 11.022s (~) 0.309s 3 1.00x
💻 Local Nitro 10.817s (-0.7%) 11.022s (~) 0.205s 3 1.01x
💻 Local Express 10.830s (+2.5%) 11.022s (~) 0.193s 3 1.01x
🐘 Postgres Express 20.102s (-1.2%) 21.054s (~) 0.952s 2 1.88x
🐘 Postgres Nitro 20.238s (-0.6%) 21.058s (~) 0.820s 2 1.89x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 18.386s (-13.9% 🟢) 19.977s (-13.6% 🟢) 1.591s 2 1.00x
▲ Vercel Nitro 18.570s (-15.8% 🟢) 20.182s (-12.4% 🟢) 1.613s 2 1.01x
▲ Vercel Next.js (Turbopack) 18.994s (-11.2% 🟢) 20.050s (-10.8% 🟢) 1.055s 2 1.03x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 27.216s (~) 28.053s (~) 0.837s 3 1.00x
💻 Local Nitro 27.462s (-0.5%) 28.050s (~) 0.588s 3 1.01x
💻 Local Express 27.504s (+2.6%) 28.052s (+3.7%) 0.547s 3 1.01x
🐘 Postgres Express 50.382s (~) 51.127s (+1.0%) 0.746s 2 1.85x
🐘 Postgres Nitro 50.508s (+0.6%) 51.137s (~) 0.628s 2 1.86x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 45.833s (-15.8% 🟢) 47.001s (-17.1% 🟢) 1.168s 2 1.00x
▲ Vercel Next.js (Turbopack) 46.873s (-15.5% 🟢) 47.731s (-16.3% 🟢) 0.858s 2 1.02x
▲ Vercel Nitro 48.572s (-10.9% 🟢) 49.909s (-10.7% 🟢) 1.337s 2 1.06x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 56.781s (~) 57.100s (~) 0.319s 2 1.00x
💻 Local Nitro 57.201s (~) 58.099s (~) 0.898s 2 1.01x
💻 Local Express 57.425s (+3.0%) 58.105s (+3.6%) 0.679s 2 1.01x
🐘 Postgres Express 77.977s (-22.3% 🟢) 78.678s (-22.3% 🟢) 0.701s 2 1.37x
🐘 Postgres Nitro 100.127s (~) 100.232s (-1.0%) 0.105s 1 1.76x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 96.586s (-16.5% 🟢) 98.177s (-15.8% 🟢) 1.591s 1 1.00x
▲ Vercel Express 97.243s (-10.7% 🟢) 98.563s (-10.7% 🟢) 1.320s 1 1.01x
▲ Vercel Next.js (Turbopack) 103.870s (-6.0% 🟢) 104.360s (-6.8% 🟢) 0.490s 1 1.08x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 1.391s (-2.8%) 2.005s (~) 0.613s 15 1.00x
💻 Local Next.js (Turbopack) 1.408s (~) 2.005s (~) 0.597s 15 1.01x
💻 Local Express 1.416s (+4.5%) 2.005s (~) 0.589s 15 1.02x
🐘 Postgres Express 2.034s (-11.8% 🟢) 2.225s (-26.1% 🟢) 0.191s 14 1.46x
🐘 Postgres Nitro 2.163s (~) 3.015s (+20.0% 🔺) 0.852s 10 1.55x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.799s (-1.4%) 3.885s (+5.2% 🔺) 1.086s 8 1.00x
▲ Vercel Express 2.926s (-5.7% 🟢) 4.324s (+1.5%) 1.397s 8 1.05x
▲ Vercel Nitro 3.054s (~) 4.729s (-9.9% 🟢) 1.675s 7 1.09x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 2.522s (+4.8%) 3.007s (~) 0.485s 10 1.00x
💻 Local Nitro 2.549s (-0.7%) 3.007s (~) 0.458s 10 1.01x
💻 Local Express 2.640s (+15.2% 🔺) 3.007s (~) 0.367s 10 1.05x
🐘 Postgres Nitro 6.826s (-25.7% 🟢) 7.434s (-22.0% 🟢) 0.608s 5 2.71x
🐘 Postgres Express 9.230s (+8.0% 🔺) 10.028s (+11.1% 🔺) 0.798s 3 3.66x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.784s (-8.9% 🟢) 3.558s (-23.4% 🟢) 0.774s 9 1.00x
▲ Vercel Next.js (Turbopack) 2.935s (-15.4% 🟢) 4.289s (-12.3% 🟢) 1.354s 7 1.05x
▲ Vercel Nitro 3.194s (+6.5% 🔺) 4.160s (-12.1% 🟢) 0.966s 8 1.15x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 6.987s (+6.6% 🔺) 7.618s (+1.4%) 0.631s 5 1.00x
💻 Local Nitro 7.387s (~) 8.020s (~) 0.632s 4 1.06x
💻 Local Express 7.878s (+24.9% 🔺) 8.268s (+17.9% 🔺) 0.390s 4 1.13x
🐘 Postgres Nitro 44.846s (-9.2% 🟢) 45.106s (-10.0% 🟢) 0.260s 1 6.42x
🐘 Postgres Express 47.135s (-1.0%) 48.121s (~) 0.986s 1 6.75x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.401s (-35.4% 🟢) 5.007s (-24.9% 🟢) 1.606s 6 1.00x
▲ Vercel Next.js (Turbopack) 3.887s (-33.6% 🟢) 5.189s (-30.8% 🟢) 1.302s 6 1.14x
▲ Vercel Express 4.254s (-7.8% 🟢) 6.196s (+3.2%) 1.942s 5 1.25x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 1.423s (+0.7%) 2.005s (~) 0.583s 15 1.00x
💻 Local Next.js (Turbopack) 1.425s (+1.3%) 2.005s (~) 0.580s 15 1.00x
💻 Local Express 1.459s (+7.5% 🔺) 2.004s (~) 0.545s 15 1.03x
🐘 Postgres Express 2.031s (~) 2.514s (-8.3% 🟢) 0.483s 12 1.43x
🐘 Postgres Nitro 2.130s (+6.7% 🔺) 2.474s (-4.8%) 0.344s 13 1.50x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.469s (-12.5% 🟢) 3.195s (-17.6% 🟢) 0.726s 10 1.00x
▲ Vercel Nitro 2.496s (-11.9% 🟢) 3.408s (-15.5% 🟢) 0.911s 9 1.01x
▲ Vercel Next.js (Turbopack) 2.815s (-6.7% 🟢) 3.387s (-23.8% 🟢) 0.572s 9 1.14x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 2.591s (+5.6% 🔺) 3.009s (~) 0.418s 10 1.00x
💻 Local Nitro 2.645s (~) 3.007s (~) 0.362s 10 1.02x
💻 Local Express 2.808s (+17.4% 🔺) 3.007s (~) 0.199s 10 1.08x
🐘 Postgres Express 12.017s (-0.6%) 12.701s (+2.7%) 0.685s 3 4.64x
🐘 Postgres Nitro 12.421s (+12.0% 🔺) 12.705s (+5.5% 🔺) 0.284s 3 4.79x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.619s (-13.8% 🟢) 4.466s (-2.0%) 1.848s 7 1.00x
▲ Vercel Express 2.673s (-16.6% 🟢) 3.854s (-14.0% 🟢) 1.182s 8 1.02x
▲ Vercel Next.js (Turbopack) 3.730s (+22.6% 🔺) 5.290s (+29.6% 🔺) 1.560s 6 1.42x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 7.553s (+5.9% 🔺) 8.017s (+6.6% 🔺) 0.464s 4 1.00x
💻 Local Nitro 7.786s (~) 8.018s (~) 0.232s 4 1.03x
💻 Local Express 8.309s (+14.7% 🔺) 9.024s (+12.6% 🔺) 0.715s 4 1.10x
🐘 Postgres Express 50.833s (-1.5%) 51.108s (-1.9%) 0.275s 1 6.73x
🐘 Postgres Nitro 50.986s (-4.9%) 51.120s (-5.6% 🟢) 0.134s 1 6.75x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.751s (+13.2% 🔺) 5.095s (+8.0% 🔺) 1.344s 6 1.00x
▲ Vercel Next.js (Turbopack) 3.848s (-12.9% 🟢) 4.881s (-11.3% 🟢) 1.033s 7 1.03x
▲ Vercel Express 3.998s (+5.6% 🔺) 5.403s (+10.4% 🔺) 1.404s 7 1.07x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Stream Benchmarks (includes TTFB metrics)
workflow with stream

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 0.140s (-4.4%) 1.001s (~) 0.011s (+7.8% 🔺) 1.017s (~) 0.876s 10 1.00x
💻 Local Nitro 0.172s (-6.9% 🟢) 1.002s (~) 0.011s (+3.8%) 1.016s (~) 0.844s 10 1.22x
💻 Local Express 0.172s (+55.7% 🔺) 1.002s (~) 0.011s (+13.5% 🔺) 1.016s (~) 0.844s 10 1.23x
🐘 Postgres Express 1.185s (-51.5% 🟢) 1.889s (-27.3% 🟢) 0.001s (+27.3% 🔺) 2.012s (-33.3% 🟢) 0.827s 10 8.45x
🐘 Postgres Nitro 2.241s (-5.5% 🟢) 2.804s (+11.1% 🔺) 0.002s (+21.4% 🔺) 3.015s (+3.4%) 0.775s 10 15.97x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - - -

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.413s (-13.2% 🟢) 2.895s (-13.5% 🟢) 0.164s (+12.0% 🔺) 3.698s (-12.1% 🟢) 1.285s 10 1.00x
▲ Vercel Nitro 2.448s (-13.3% 🟢) 2.837s (-13.7% 🟢) 0.237s (-13.5% 🟢) 3.742s (-12.6% 🟢) 1.294s 10 1.01x
▲ Vercel Next.js (Turbopack) 2.611s (-8.6% 🟢) 2.963s (-17.4% 🟢) 0.262s (-10.3% 🟢) 3.824s (-16.6% 🟢) 1.213s 10 1.08x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Next.js (Turbopack) 9/12
🐘 Postgres Express 10/12
▲ Vercel Nitro 5/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 💻 Local 9/12
Next.js (Turbopack) 💻 Local 10/12
Nitro 💻 Local 9/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

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