Updated Performance (markdown)
Tweak pprof wording for santization
Document profiling with pprof-it & pprof. (#338)
* Document profiling with pprof-it & pprof.
* Point out `PPROF_SANITIZE`.
* More warning blocks.
feat: add details re diagnostics
chore: format one sentence per line
Callout performance characteristics of ts-server
While reading the guide with an eye for improving the editor experience,
I was not sure how ts-server behaves, or how fixing hotspots I view
during tracing would change the editing experience. I ended up jumping
into Discord for clarity, and this is a summary of what I learned.
Remove mention of --trace-ic in favor of dexnode
Updated Performance (markdown)
Updated Performance (markdown)
Fix Performance dropdown closing </details> tag
More "easy-to-compile code" content.
Updated Performance (markdown)
Updated Performance (markdown)
Updated Performance (markdown)
Recommend @typescript/analyze-trace
Clarify why we ask for a tsc trace
Update the Project References section based on recent perf investigations
Updated Performance (markdown)
Tracing tweaks
Mainly use a single `about://tracing` URL which works in both Edge and
Chrome.
Few other minor tweaks (including reducing the very long link texts).
Add TOC link to Performance Tracing
Apply suggestions from code review
Added section about 'Performance Tracing' in the 'Performance' page.
Updated Performance (markdown)
Updated Performance (markdown)
Updated Performance (markdown)
Updated Performance (markdown)