5c24670227
@timneutkens this adds a trace capturing script alongside the other tracing sundry. This will be utilized by the performance automation. Additionally, its nice to have an option other than running the ZipKin JAR to get at the raw data. |
||
|---|---|---|
| .. | ||
| pages | ||
| readdir | ||
| recursive-copy | ||
| recursive-delete | ||
| capture-trace.js | ||
| instrument.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