Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

docs: fix typos in ssr-benchmarks README.md

Browse source 
Corrected typos in modules/ssr-benchmarks/README.md: mesure→measure, Struture→Structure, render→renders, benckmark→benchmark, capitalized DevTools, and clarified the flame chart instruction.

(cherry picked from commit 13c198ae63)
This commit is contained in:
splincode 2026-03-21 11:06:18 +03:00 committed by Leon Senft
parent 1af0db5742
commit fb7a10fb18
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
modules/ssr-benchmarks/README.md
View file

@ -1,12 +1,12 @@
## Intro
This small benchmark suite is dedicated to mesure & describe how compute time is spent when rendering an application like in SSR.
This small benchmark suite is dedicated to measure & describe how compute time is spent when rendering an application like in SSR.
## Struture
## Structure
- `./main.ts` is the entry point to run the benchmark
- `./src` contains a sample app that exports a `render` function.
- This app render a table of variable size, which depends on data (`initData()`)
- This app renders a table of variable size, which depends on data (`initData()`)
- This app is then rendered X numbers of times
- Individual function calls are measured with `startMeasuring()`/`stopMeasuring()` from the core package.
@ -20,16 +20,16 @@ This small benchmark suite is dedicated to mesure & describe how compute time is
`pnpm bazel run //modules/ssr-benchmarks:run_browser`
This bazel target will build the benchmark, start a http-server with a html that will load the benckmark script.
This bazel target will build the benchmark, start a http-server with a html that will load the benchmark script.
The benchmark script with this target will have DOM Emulation disabled.
The result will be visible in the devtools console.
The result will be visible in the DevTools console.
Note: Due to the CLI adding some polyfills, @angular/build is patched to disable DOM emulation and running server code inside a browser:
1. removing an import from `node:module` in `polyfills.server.mjs` (with `tail ...`)
2. removing the import of `platform-server/init`.
To run create a usable flame chart, prepare a narrowed run (like `benchmarkRun(10000, 20);`).
To create a usable flame chart, prepare a narrowed run (like `benchmarkRun(10000, 20);`).
Then in the performance tab of the devtools, trigger "Record & Reload" to generate a profile.
### Deopt Explorer