A Quick Update on Snappy Progress

The Performance team has retired the Snappy name, and the individual project leads are now blogging their projects’ progress instead of Taras doing regular Snappy blog posts.

However, I think there might still be some interest in seeing the performance improvements summarized in one place, and since I’m already doing Performance team updates at the Platform meeting, I thought I would try my hand at regularly blogging about ongoing performance work.

So without further ado, these are a few highlights from the past 2 weeks:

  • bug 859558: John Daggett is working on eliminating font jank. The font bugs currently tracked in this meta-bug are top offenders according to chrome-hang reports.
  • Honza Bambas wrote a draft proposal for a new network cache design. The locking in the current network cache is a common source of Firefox jank.
  • bug 830492: Gregory Szorc changed SQLite behavior in FHR to require fewer fsyncs
  • Kyle Lahnakoski developed a tool for comparing Telemetry simple measures. This tool is in the prototype stage and is currently only being used to look for correlations between slow startups and other Telemetry variables (more on that in another blog post). Since Kyle & I are currently the only users of this tool, the page is only accessible from Mozilla’s Toronto network. You will also have to disable mixed-content protection on the page.

A recent bug affected Telemetry submission rates on Firefox 21, 22, and 23 for several weeks. It has since been resolved (bug 844331 and bug 862599), but you’ll need to exercise caution when interpreting dashboard results from the affected time period. Specifically, you may want to exclude data from time periods with relatively few Telemetry submission counts.

Finally, there were several blog posts from the individual project leads:

2 Responses to A Quick Update on Snappy Progress

  1. Great update, thanks!

    Looking forward to more =)

  2. Thanks for doing this. It is a real pain trying to keep up with a number of different blogs. especially when certain parts of the project only occasionally interest me.