Automated performance testing and sheriffing 编辑
We have several test harnesses that test Firefox for various performance characteristics (page load time, startup time, etc.). We also generate some metrics as part of the build process (like installer size) that are interesting to track over time. Currently we aggregate this information in the Perfherder web application where performance sheriffs watch for significant regressions, filing bugs as appropriate.
Current list of automated systems we are tracking (at least to some degree):
- Talos: The main performance system, run on virtually every check-in to an integration branch
- build_metrics: A grab bag of performance metrics generated by the build system
- AreWeFastYet: A generic JavaScript and Web benchmarking system
- AreWeSlimYet: A memory benchmarking tool
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论