sass/dart-sass

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

Open

#16 建立於 2016年11月1日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)Dart (4,192 star) (376 fork)batch import
help wantedinfrastructure

描述

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.

貢獻者指南

技術棧
無
領域
performance
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Familiarity with DartUnderstanding of JIT compilation
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
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.