Skip to content
This repository has been archived by the owner on Nov 24, 2022. It is now read-only.

[WIP] Add nofib testing #640

Draft
wants to merge 90 commits into
base: master
Choose a base branch
from
Draft

[WIP] Add nofib testing #640

wants to merge 90 commits into from

Conversation

gkaracha
Copy link
Member

@gkaracha gkaracha commented May 7, 2020

Closes #639.

Set up the nofib directory:

  • Gather nofib main programs and their arguments from the upstream nofib repo.
  • Flatten the structure (only two levels) and fix/remove symlinks.
  • Remove tests that don't apply to asterius yet and other redundant files.
  • Replace local Makefiles with explicit FAST_OPTS, NORM_OPTS and SLOW_OPTS input files.

After that move on to CI-related tasks:

  • Set up the native/asterius comparison and set it up as a standalone CI job.
  • Generate V8 CPU/heap profiler report and serve them as CI artifacts, so we can examine the bottlenecks visually.

@TerrorJack
Copy link
Member

TerrorJack commented May 17, 2020

Additional notes:

  • We'll likely need to evaluate the influence of different link-time options (e.g. enabling tail calls, yolo mode, different gc thresholds), since they can have a significant impact on the overall clock time. Also, certain node V8 command-line options (use node --v8-options to get a complete list; will discuss which options to test later)
  • For getting a flame graph from V8 profiling reports, I tried a few tools and 0x seems to be pleasant to use. Use the --verbose-err link-time option to ensure wasm function names are visible in the output flame graph.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add nofib performance testing
2 participants