[AlexanderKaran]

Now each benchmark has unit inside it we can drop the unit names from some of the keys. This can seem like a large PR due to the migration of existing results you only need to review:

• b57a68d
• ed3507b
• 6cec356

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	framework-performance	8ee1c26	Commit Preview URL Branch Preview URL	Nov 12 2026, 04:19 AM

[dreyfus92]

small naming thought: we now have coldBuildDuration / warmBuildDuration next to installTime / time / elapsedTime, might be worth picking one of time or duration while we're renaming anyway. config keys like durationMs / warmupDurationMs still have the suffix, which i guess is on purpose since they're not measurements?

[AlexanderKaran]

@dreyfus92 I think constancy in naming approach should be its own PR to help make it clear what choices were made i.e this part

small naming thought: we now have coldBuildDuration / warmBuildDuration next to installTime / time / elapsedTime, might be worth picking one of time or duration while we're renaming **anyway.**

As for durationMs / warmupDurationMs still have the suffix yes this is on purpose they are config sets up, storing what was done for warm up and stuff. However maybe we could rip these out and they can just be part of the config here:

packages/results/src/measurements.ts

They are unlikely to change and if they ever do you can just check the git history would keep the results slimmer as well. Would also be its own PR

[dreyfus92]

agree on the naming, makes sense as its own pr so the choices are clear ✌🏻