nolanlawson/optimize-js

Use benchmark.js or similar, report standard deviation

Open

#23 创建于 2016年9月30日

在 GitHub 查看
 (0 评论) (1 反应) (0 负责人)JavaScript (3,761 star) (128 fork)batch import
enhancementhelp wanted

描述

Right now I'm taking the median of 251 runs, but I'm a bit unsatisfied with this because I have not confirmed that 251 is enough to eliminate unreasonable variance, nor does it tell me the standard deviation or any of those niceties. As pointed out in https://github.com/nolanlawson/optimize-js/issues/2#issuecomment-248308234, we should really have a more rigorous benchmark in place, especially as we start to potentially make changes to "improve" performance, which need to be proven to actually improve it.

I looked at benchmark.js but TBH couldn't figure out how to nicely integrate it with the current benchmark design; e.g. currently I request each script with a random query param to force the browser to re-parse and re-evaluate it, and the timings have to be inside the script itself, so it's very tricky to implement.

贡献者指南

技术栈
javascript
领域
performancetesting
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
JavaScriptBenchmark.js basicsCodebase familiarity
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
The issue requests replacing the current median based benchmark with a more rigorous approach using benchmark.js or similar, reporting standard deviation. The current benchmark runs 251 trials and takes median; the author notes difficulty integrating benchmark.js due to random query params and timing inside scripts. The linked comment in issue #2 provides context. The repository is unmaintained, so any implementation would be for learning purposes. Relevant files include the benchmark script (likely in the repository root or a 'bench' directory).