e27b7e996d
A number of changes here. I recommend viewing the diff with the <a href="?w=1">whitespace flag enabled</a>.
- OpenTelemetry is replaced with a custom and lightweight tracing solution.
- Three trace targets are currently supported: console, Zipkin, and NextJS.
- Tracing is now governed by environment variables rather than `--require instrument.js`.
+ `TRACE_TARGET`: one of `CONSOLE`, `ZIPKIN`, or `TELEMETRY`; defaults to `TELEMETRY` if unset or invalid.
+ `TRACE_ID`: an 8-byte hex-encoded value used as the Zipkin trace ID; if not provided, this value will be randomly generated and passed down to subprocesses.
Other sundry:
- I'm missing something, probably a setup step, with the Zipkin target. Traces are captured successfully, but you have to manually enter the Trace ID in order to view the trace - it doesn't show up in queries.
- I'm generally unhappy with [this commit](
|
||
|---|---|---|
| .. | ||
| pages | ||
| readdir | ||
| recursive-copy | ||
| recursive-delete | ||
| capture-trace.js | ||
| package.json | ||
| readme.md | ||
Next.js server-side benchmarks
Installation
Follow the steps in contributing.md
Both benchmarks use ab. So make sure you have that installed.
Usage
Before running the test:
npm run start
Then run one of these tests:
- Stateless application which renders
<h1>My component!</h1>. Runs 3000 http requests.
npm run bench:stateless
- Stateless application which renders
<li>This is row {i}</li>10.000 times. Runs 500 http requests.
npm run bench:stateless-big