You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bench(protobuf): compare each runtime's real path, not forced protobuf-es
esrun now decodes with its native runtime:serialization Protobuf; Node/Bun/Deno
keep protobuf-es. Same wire bytes, so the row reflects each runtime's actual
protobuf handling. Regenerated site numbers: esrun leads on time and memory
(small 77ms/37MB, large 4.1s/108MB).
Copy file name to clipboardExpand all lines: site/app/docs/benchmarks/page.jsx
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -182,9 +182,9 @@ export default function BenchmarksDoc() {
182
182
<BenchChartmetrics={parserWorkloads}/>
183
183
</div>
184
184
185
-
<h2className="mt-12 text-xl font-semibold text-zinc-900">Protobuf (same library, all runtimes)</h2>
185
+
<h2className="mt-12 text-xl font-semibold text-zinc-900">Protobuf (each runtime's own path)</h2>
186
186
<pclassName="mt-2 text-sm text-zinc-500">
187
-
Every runtime runs the same library — <code>protobuf-es</code> (<code>@bufbuild/protobuf</code>) — decoding identical bytes, so this measures the runtime, not the library.
187
+
esrun decodes with its native <code>runtime:serialization</code> Protobuf (pure-JS, reflective); Node, Bun, and Deno decode with <code>protobuf-es</code> (<code>@bufbuild/protobuf</code>). Identical bytes, each runtime's real protobuf path.
0 commit comments