Misc

Linux Plumbers

A few of us attend LinuxPlumbers last month, I gave talk. Basic summary: kernel + toolchain could add a few straight-forward features to make Firefox and other apps start faster and use less memory.

Performance Team

I am no longer alone on my quest of performance whack-a-mole. Since spring I’ve been growing a team of extremely talented people to help make Firefox faster and slimmer. As a manager I do more people tasks now, so I have less ” ____ sucks” blog posts to write. We are currently working on massively speeding up Fennec startup via incremental decompression (sort of like an efficient UPX for android), fixing SQLite + other IO usage in Firefox, reordering binaries for faster startup, faster shutdown. The idea is to focus on all areas of browser performance other than rendering the web (for now).

Performance Help

“Perf work is cool, but I wouldn’t know where to start with finding a good first perf-bug” <– is this you? Would any of my readers be interested in a roundup of next set of “low hanging fruit” perf-improvements to be had?

Example bugs:

5 comments

  1. Congrats (on becoming a manager)

  2. ‘Would any of my readers be interested in a roundup of next set of “low hanging fruit” perf-improvements to be had?’

    Yes, please.

  3. I’d definitely be interested, please

  4. Something I’ve found with MemShrink is that it’s not easy for newbies to help because it covers the entire browser, and I think you’ll have much the same problem.

    It’s much easier for a newbie who says “I want to help with IonMonkey” or something like that, because it’s a small component that doesn’t require large amounts of cross-browser knowledge.

  5. maybe I’m missing something but:
    662397 is listed for linux but docs talk about windows
    686805 is listed for mac but it’s android
    693485 is listed for windows but it’s android