facebookarchive/prepack

Collect statistics that help understand Prepack effects

Open

#934 opened on Aug 26, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (520 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (14,268 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Prepack runs the global code, and we could collect some runtime information to help assess what Prepack does:

  • How many objects get created when running the interpreter? (And how many survive and get serialized?)
  • How many object properties get updated? (And how many are serialized?)
  • How many times does each type of AST node get evaluated? (Pretty much all of those computations, except for some literals, object allocations, property updates, will get eliminated by Prepack.)

When forking and merging control-flow, compute the maximum value for each explored case.

Contributor guide

Research direction
Explore the Prepack interpreter code to understand object creation and property updates, then implement counters for AST node evaluations, object allocations, and property updates. Consider handling control flow merging by taking the maximum of counters across paths.
Tech stack
javascript
Domain
toolingperformance
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40