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 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据

词条统计

浏览:113 次

字数:1146

最后编辑:7 年前

编辑次数:0 次

    我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
    原文