Performance/Snappy
Jump to navigation
Jump to search
Snappy is a project that aims to improve Firefox responsiveness. This project is a responsiveness equivalent of Performance/Memshrink
Meetings
Meetings will happen every Friday at 1pm Pacific time.
- Dial-in: Audio-only conference# 95346
- People with Mozilla phones or softphones please dial x4000 Conf# 95346
- US/Toll-free: +1 800 707 2533, (pin 4000) Conf# 95346
- US/California/Mountain View: +1 650 903 0800, x4000 Conf# 95346
- US/California/San Francisco: +1 415 762 5700, x4000 Conf# 95346
- US/Oregon/Portland: +1 971 544 8000, x4000 Conf# 95346
- CA/British Columbia/Vancouver: +1 778 785 1540, x4000 Conf# 95346
- CA/Ontario/Toronto: +1 416 848 3114, x4000 Conf# 95346
- UK/London: +44 (0)207 855 3000, x4000 Conf# 95346
- FR/Paris: +33 1 84 88 37 37, x4000 Conf# 95346
- Gmail Chat (requires Flash and the Google Talk plugin): paste +1 650 903 0800 into the Gmail Chat box that doesn't look like it accepts phone numbers
- SkypeOut is free if you use the 800 number
- Vidyo: MTV-Sick Bay
- IRC: #perf
- Etherpad: snappy (copied to wiki after the meeting)
Ideally, these weekly meetings would only be needed for a medium length of time, say 1 or 2 quarters. Hopefully after that, things will have improved enough that meetings could be less frequent (bi-weekly or monthly) or not needed at all.
Minutes and Progress Reports
Bug Tracking
Bugs tracked by the Snappy project are prioritized by adding one of "Snappy:P1", "Snappy:P2" or "Snappy:P3" to the whiteboard.
- Unprioritized Snappy bugs. These are triaged regularly in meetings.
- Snappy:P1 bugs. These are discussed regularly in meetings.
- Snappy:P2 bugs. These are discussed occasionally in meetings. P2 is the default priority.
- Snappy:P3 bugs. These are discussed rarely in meetings.
Some other interesting bugs/lists.
- visible unresponsiveness metabug
- sync storage main-thread-io metabug
- cycle collector responsiveness metabug
Goals
- 50ms responsiveness when typing in a textbox
- 60fps animations on UI operations, ie closing tabs.
- track above via telemetry
Current Infrastructure
- Ted's event loop thing?
Additional Infrastructure
- Have metrics do continuous trend analysis to see if our telemetry stats are getting better over time.