/vega-benchmarks

Scripts to benchmark Vega's performance
  1. HTML 81.7%
  2. JavaScript 16.9%
  3. Shell 1.2%
  4. CSS 0.2%
HTML JavaScript Shell CSS
Find file
Latest commit 20ad5e8 Feb 5, 2016 @arvind arvind Remove erroneously generator includes.
Failed to load latest commit information.
interaction Remove erroneously generator includes. Feb 5, 2016
lib Use consistent input data, streaming tuples, and interaction events a… Aug 1, 2015
results Results and summary script. Aug 1, 2015
scripts Results and summary script. Aug 1, 2015
streaming Use consistent input data, streaming tuples, and interaction events a… Aug 1, 2015
.gitignore Results and summary script. Aug 1, 2015
LICENSE Initial commit Jul 20, 2015
README.md Updated readme with results. Aug 3, 2015
index.js Use consistent input data, streaming tuples, and interaction events a… Aug 1, 2015
interaction.sh Adding runner scripts. Jul 28, 2015
package.json Initial port+refactor of uwdata/vega benchmarks. Jul 21, 2015
streaming.sh Adding runner scripts. Jul 29, 2015

README.md

vega-benchmarks

Scripts to benchmark Vega's performance.

Results

Streaming benchmarks

Average performance of rendering (non-interactive) streaming visualizations: (top-bottom) scatterplot, parallel coordinates, and trellis plot; (left-right) initialization time, average frame time, and average frame rate. Dashed lines indicate the threshold of interactive updates.

Interaction benchmarks

Average frame rates for three interactive visualizations: (left-right) brushing and linking on a scatterplot matrix; brushing and linking on an overview+detail visualization; panning and zooming on a scatterplot. Dashed lines indicate the threshold of interactive updates.

Benchmark Process

Usage: ./index.js <visualization> [options]

Options:
  --benchmark  Benchmark operation to run.                   [string] [required]
  --renderer   Vega renderer (canvas or svg).       [string] [default: "canvas"]
  -R           Number of repetitions to perform.                   [default: 10]
  -N           Number of data tuples.                             [default: 100]
  -C           Number of data categories.                          [default: 50]
  -P           % of data tuples to stream.                       [default: 0.01]
  --help       Show help                                               [boolean]

  1. Run npm install in the benchmarks directory, and then npm start.

  2. Individual benchmarks can be run via the index.js script. See usage help text above.

  3. Benchmark suites, as reported in the paper, are available via the streaming.sh and interaction.sh bash scripts.

  4. Results concatenated against existing results found in the results/raw folder. By default, we included the results reported in the paper. Clearing these results will generate new files instead.

  5. A script to summarize raw results is provided for convenience (scripts/summary.js).