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 (376 forks)batch import
help wantedinfrastructure

Repository metrics

Stars
 (4,192 stars)
PR merge metrics
 (Avg merge 8d 8h) (18 merged PRs in 30d)

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

Research direction
Investigate how to measure Dart VM execution time for a JIT compiled Sass compilation process. Use the Stopwatch class or dart:developer to benchmark the compilation time after the VM has warmed up. Set up a worker that keeps the Dart VM warm and record times for incremental rebuilds.
Tech stack
dart
Domain
tooling
Issue type
Performance
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.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Dart
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55