Performance/Snappy/2012-10-11

From MozillaWiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Snappy Oct 11, 2012 Status (no meeting this week)

Actions

  • Gavin will write down Q4 frontend goal
  • Outreach with Twitter on bug 784920, twitter is causing sync layout which harm the browser when the tab is in the background
  • bug 792527 - bas to add Telemetry
  • CSS animation start jank - jeff/ehsan to ping david baron (bug 753139)
  • wlach to determine what time he has to work on Eideticker for desktop this quarter
    • wlach: still trying to determine this, hopefully will have a better estimate by next week. right now it's looking like eideticker-for-b2g will be consuming most of my attention for at least the next month. most of the base work is done, but it looks like there's still a considerable amount of work still to be done in automating the testing process and writing B2G-appropriate tests.
  • wlach to work with jaws to see if Camtasia Studio can be used a software-only capture solution for eideticker
    • wlach: Camtasia doesn't look like the right thing as it doesn't appear to be scriptable. Fraps (http://www.fraps.com/) might be more appropriate, need to look closer (it may only work with 3D accelerated games).

Incoming

Projects

Tab switch performance - jrmuizel

Results from the past week
  • Better tab switch telemetry has landed on inbound (bug 800031)
  • A fix for the image decoding stuff is coming soon (bug 799335, patch is up for review)
Todo this week

Profiler - jrmuizel/BenWa/Ehsan (and more)

Results from the past week
  • Working on providing startup profiling prototype. Not yet ready to ship you can try it out from BenWa's repo.

Tools and Automation: Eideticker, talos, peptest - mcote, ahal, wlach

Results from the past week
  • [ahal] all hands on deck for b2g this quarter, won't have time for peptest

Chrome hang reports - vlad

Results from the past week
  • confirmed that the proxy-hang fixes (bug 769764 and bug 787757) are good using the latest chrome hang data.