Technical metrics

Performance tuning

Measure and optimize first render, layout, updates, labels, and viewport interaction

View source on GitHub
  • Reuse backend coordinates when available and omit layout.
  • Control iterations for force layouts and consider worker: true.
  • Prefer deterministic layouts for large overview screens.
  • Use state and batch update APIs for high-frequency interaction.
  • Keep functional style callbacks inexpensive and precompute complex mappings.
  • Limit initial labels; reveal more by zoom, focus, or selection.
npm run benchmark -- --suite all --mode quick
npm run benchmark -- --suite browser --mode full

Compare only equivalent environments and configurations. Desktop Headless Chrome cannot replace real mobile or low-end device testing.

Performance metrics

Reproduce G6Lite Node and browser benchmarks with explicit environments and result boundaries

Bundle size

Reproduce the size-limit measurement and enforce the 120 kB brotli budget