sass/dart-sass

Benchmarks: Record Dart VM time with JIT'd/warm code

Open

#16 opened on Nov 1, 2016

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Dart (4,192 stars) (376 forks)batch import
help wantedinfrastructure

Description

At least internally, we spin up a worker and use it for incremental rebuilds. This means the code/snapshot is already loaded, already JITd, and kept warm for the development cycle. This is more likely than spinning up to do a one-time build and closing.

Contributor guide

Tech stack
None
Domain
performance
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.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with DartUnderstanding of JIT compilation
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the existing benchmark infrastructure in the repository (likely under a `benchmark/` or `perf/` directory) to understand how current benchmarks are run. Then add a new metric that records the Dart VM time after JIT compilation, possibly by using a warm up run before measurements. Consult any linked documentation or comments from maintainers for implementation details.