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.