Welcome to the svite benchmark challenge

Lets see who's got the fastest hot module updates in github town in 3 easy steps

1. install

mac/linux/wsl

npx degit dominikg/svite/examples/hmr-benchmark svite-bench && cd svite-bench && npm i 

windows

npx degit dominikg/svite/examples/hmr-benchmark svite-bench ; cd svite-bench ; npm i 

2. inside svite-bench directory execute

node benchmark --headless --gif # --gif only works with ImageMagick 'convert' in path.

3. add comment with output and svite-bench/dist/benchmark.gif below

FAQ

Whats on the line?

Bragging rights.

What does it do?

• start vite dev-server
• open chromium with dev page
• trigger hot module reloads (44)
  • write App.svelte, add 1 visible change (new text character or style color)
  • after each change, wait for the browser console to log the updated message
  • measure the time it took from writing the file to the rendered update
• close chromium
• stop dev-server
• create stats
• optionally create gif

Go read the code

help

    benchmark supports the following arguments:
      --headless    - render headless
      --gif         - create a gif in ./dist (requires ImageMagick 'convert' in path)
      --resultfile  - write stats to a timestamped file
      --throttle X  - wait X milliseconds between writes to the same file
      --help,-h     - print this message

gif output does not work

Sorry, ImageMagick convert binary has to be available in path

whats that throttle thing about?

The benchmark writes to the same file in very short intervals. sometimes so short, that the update watcher misses a write and then the process gets stuck as benchmark waits for an update to complete before writing the next step. It automatically adds a throttle to prevent this which increases 10ms every time it gets stuck. You can prevent this dance by providing a throttle argument at start