Firefox Startup Performance Weekly Summary

Current numbers are available on the Performance Snapshot page.

Summary, relative to Firefox 3.5:

• Warm startup: For Mac, 36% better on 3.6 and 35% better on 3.7. For Windows, 5% and 5%. Flat on Linux. Also, Warm startup for Mac on 3.6 is a whopping 13% better than last week, due to the landing of bug 517804.
• Cold startup:  For Mac, 20% better on both 3.6 and 3.7. For Windows, not measuring yet. For Linux, we’re seeing a regression of ~9% across branch and trunk in the snapshot but not on the graphs, so I need to figure out where the discrepancy is.

This week’s activity:

• Dirty-cold-Ts went live this week, thanks to Alice and Lukas. Example: cold startup with a large places.sqlite on Mac.
• Joel is making progress on making a super-static Firefox in bug 525013.
• Ben is making progress on the fastload replacement in bug 520309.
• No updates on Windows cold-startup testing for Talos on bug 522807. I need to test on Vista, and turn off Pre/Superfetch.
• Taras has patches up for service caching (bug 516085) and super-fast-path-ing of Components.* (bug 512584), however the latter he’s hit a wall, passing on to Blake or someone else who knows that code.
• Ted landed rebasing on Windows in bug 484799.
• Jonathan Kew has a new patch in bug 519445 for further reductions in Mac startup time spent in font system initialization, just about there…
• Ryan Flint put a patch to minify JS on bug 524858, not working yet, but significantly reduced the size of shipped JavaScript files.

Projects in a holding pattern:

• JARification: David abandoned moving JS modules into a JAR file, since those files are fastloaded. However, since we want things like post-extension-install restarts to be fast, and those cause fastload cache invalidation, we might want to do things like this anyways. I filed a bug for the same treatment for components. These are lower priority, since they’re not the normal startup case. Follow along with all JAR-ification via the tracker bug.
• Startup Timeline: No updates, still not landed. Add [ft] in the whiteboard of your bug w/ the function names you want timed and David will generate it and update the bug.
• Static Analysis: No progress on bug 506128. David needs to file a bug with the final log of named-yet-uncalled functions.
• Dirty Profile Testing: No progress. Need to list scenarios, file bugs for each, generate Talos config patches and profile data, and then move it into Rel-Eng territory. Also, need to get a separate Tinderbox tree, since it’s going to cause a bazillion new columns.
• Joel Reymont noted in bug 513076 that there are serious drawbacks to getting our libraries in the dyld shared cache on Mac, so has deprioritized that work.
• No updates on Zack’s CSS parser changes in bug 513149.

As usual, more details and links are available on the project wiki, and we’re available to answer questions in #startup on irc.mozilla.org.

Easing Orange: Jetpack for Correlating Tinderbox Test Failures with Bugs

This is a Jetpack feature for finding out if a bug is already filed for a test failure on Tinderbox. When viewing log files for failed test runs, the Jetpack will add a link next to the test failure summary at the top of the log, that looks like “(maybe bug XXXXXX?)”. This allows sheriff’s and other awesome community members to easily mark known-oranges, and update the bug with log’s URL.

Install the Jetpack feature.

Notes:

• So far it only pulls file names out of error text, so won’t match leaks, crashes or oranges without a filename in the summary.
• Only searches the bug summary, and only searches known orange bugs (ie: has “[orange]” in the bug whiteboard).
• Scrapes bugzilla.mozilla.org, since the new REST api is very very slow, so might break with bugzilla upgrades.
• It doesn’t run until the log has completed loading, which sometimes can be a while. Load that shit in a background tab and be patient yo.

Let me know if this helps you out, or any bugs or improvements you’d like to see!

Firefox Startup Performance Weekly Summary

Current numbers are available on the Performance Snapshot page. Thanks to Chris Atlee for deploying it to the graph server. The snapshot is updated every 5 minutes with fresh data from Talos.

Summary, relative to Firefox 3.5:

• Warm startup: For Mac, 26% better on 3.6 and 31% better on 3.7. For Windows, 4% and 7%. Flat on Linux.
• Cold startup:  For Mac, 22% better on 3.6, 23% better on 3.7. For Windows, not measuring yet. For Linux, 3% and 9%.

This week’s activity:

• Using the data from bug 524202, Joel is tracking down exactly how and when dynamic library code is loaded. They’re past diagnostics, and are now into implementation, coaxing the linker into ordering functions in the optimal sequence. See this comment for a good summary of the issue. Joel put up a very detailed blog post about the work they’ve been doing.
• Ryan Flint updated the spellcheck bug with some new findings.
• I got a working (so far) patch for Windows cold-startup testing for Talos on bug 522807.
• Taras is in the patch review cycle for service caching in bug 516085.
• Re-enabling rebasing on Windows in bug 484799 has review now, just needs landing.
• John Dagget and Jonathan Kew have a bunch of new findings in bug 519445 for further reductions in Mac startup time spent in font system initialization. Sometimes the patch helps, sometimes it doesn’t.
• Bug 512645, removing the setTimeout 10ms wait in chrome JS has landed.
• Drew’s work on bug 506814, getting rid of Change GetPersistentDescriptor/SetPersistentDescriptor on Mac, has landed.

Projects in a holding pattern:

• Ben Hsieh has been prototyping a whole Fastload cache replacement in bug 520309.
• JARification: David abandoned moving JS modules into a JAR file, since those files are fastloaded. However, since we want things like post-extension-install restarts to be fast, and those cause fastload cache invalidation, we might want to do things like this anyways. I filed a bug for the same treatment for components. These are lower priority, since they’re not the normal startup case. Follow along with all JAR-ification via the tracker bug.
• Startup Timeline: No updates, still not landed. Add [ft] in the whiteboard of your bug w/ the function names you want timed and David will generate it and update the bug.
• Static Analysis: No progress on bug 506128. David needs to file a bug with the final log of named-yet-uncalled functions.
• Dirty Profile Testing: No progress. Need to list scenarios, file bugs for each, generate Talos config patches and profile data, and then move it into Rel-Eng territory. Also, need to get a separate Tinderbox tree, since it’s going to cause a bazillion new columns.
• Joel Reymont noted in bug 513076 that there are serious drawbacks to getting our libraries in the dyld shared cache on Mac, so has deprioritized that work.
• No updates on Zack’s CSS parser changes in bug 513149.

As usual, more details and links are available on the project wiki, and we’re available to answer questions in #startup on irc.mozilla.org.

Firefox Startup Performance Weekly Summary

This week brings a boost in visibility of results, not just for startup, but for all the performance testing we’re doing on all branches and platforms. As I mentioned last week, I was working on an automated method of generating the cross-branch startup results. Luckily Johnath and Chris Atlee had done the hard work when making the performance dashboard. It has a JSON file that contains a roll-up of the previous 7 days performance data, which is updated every 5 minutes with new Talos results. Using that as the datasource, I wrote  a script summarizes the results for each test+branch+OS combination across all the boxes that returned results, as well as stable branch and previous week differences. The final product gives a snapshot view of how each branch compares to the stable branch.

This is useful for a few different reasons. First, we (and the press and our users and our managers and everyone really) are able to know at-a-glance how any branch compares to the stable release branch. An example of another use is that before the JS team does a Tracemonkey merge, they can quickly see if any major performance effects can be expected.

The table shows red or green for any differences that are outside of a 2% threshold, to take test noise into account. This is quite liberal, as I’ve already calculated the numbers to take into account whether the difference is within the standard deviation. Reducing the noise in the tests would be a big help – perhaps some researcher will take up Roc’s challenge. A second point of trust is my math I’m not a statistician, so please view source and let me know where I’ve miscalculated.

An example of the full report is here. I’m going to file a bug and work with release-engineering to get it pushed out to the graph server, where the dashboard lives. The data from this week’s startup table is copied below (though sans the color-coding of the real thing. Actually, now WordPress keeps stripping out my styles, so you get an ugly table this week).

Ts

	Firefox3.5	Firefox3.6	Firefox	TraceMonkey
Leopard	median: 1469deviation: 110mean: 1481 from last week: 2%	median: 1115 deviation: 59 mean: 1096 from last week: 3% from 3.5: 26%	median: 1036 deviation: 48 mean: 1006 from last week: 1% from 3.5: 32%	median: 1014 deviation: 38 mean: 1000 from last week: 0% from 3.5: 32%
Linux	median: 625 deviation: 7 mean: 626 from last week: 0%	median: 632 deviation: 7 mean: 633 from last week: 0% from 3.5: -1%	median: 619 deviation: 10 mean: 623 from last week: 1%	median: 628 deviation: 7 mean: 628 from last week: 0%
Vista	median: 538 deviation: 8 mean: 540 from last week: 0%	median: 533 deviation: 13 mean: 537 from last week: 1% from 3.5: 1%	median: 503 deviation: 23 mean: 509 from last week: 0% from 3.5: 6%	median: 511 deviation: 41 mean: 531 from last week: 11% from 3.5: 2%
XP	median: 461 deviation: 6 mean: 461 from last week: 0%	median: 464 deviation: 6 mean: 464 from last week: 1% from 3.5: -1%	median: 448 deviation: 7 mean: 448 from last week: 0% from 3.5: 3%	median: 530 deviation: 38 mean: 501 from last week: 10% from 3.5: -9%

This week’s activity:

• Taras and Joel are still working on bug 524202, tracking down exactly how and when dynamic library code is loaded. They’re past diagnostics, and are now into implementation, coaxing the linker into ordering functions in the optimal sequence. See this comment for a good summary of the issue. Joel put up a very detailed blog post about the work they’ve been doing.
• Ryan Flint posted an update on his startup bug activity this week.
• Have a patch enabling Windows cold-startup testing for Talos for bug 522807, but it’s causing the whole OS to freeze, only recoverable via reboot. Fun! I also added some details and links about how Prefetch/SuperFetch work on Windows to the wiki.
• Rob Strong pushed bug 311965 to mozilla-central, comm-central and 1.9.2 while also ensuring not to break all the toolkit apps that depend on this code. Truly a gentleman of the Mozilla ecosystem.
• Taras put a new patch up for service caching in bug 516085.
• Everything is about ready for re-enabling rebasing on Windows in bug 484799, just needs landing.
• John Dagget posted some test times in bug 519445 for yet further reductions in Mac startup time spent in font system initialization, just needs review.
• Bug 512645, removing the setTimeout 10ms wait in chrome JS, is ready to land. I’ll try to land this weekend if the bug owner doesn’t get around to it first (hint hint).

Projects in a holding pattern:

• Drew has a patch up for bug 506814, getting rid of Change GetPersistentDescriptor/SetPersistentDescriptor on Mac, just needs review from Josh.
• Ben Hsieh has been prototyping a whole Fastload cache replacement in bug 520309.
• JARification: David abandoned moving JS modules into a JAR file, since those files are fastloaded. However, since we want things like post-extension-install restarts to be fast, and those cause fastload cache invalidation, we might want to do things like this anyways. I filed a bug for the same treatment for components. These are lower priority, since they’re not the normal startup case. Follow along with all JAR-ification via the tracker bug.
• Startup Timeline: No updates, still not landed. Add [ft] in the whiteboard of your bug w/ the function names you want timed and David will generate it and update the bug.
• Static Analysis: No progress on bug 506128. David needs to file a bug with the final log of named-yet-uncalled functions.
• Dirty Profile Testing: No progress. Need to list scenarios, file bugs for each, generate Talos config patches and profile data, and then move it into Rel-Eng territory. Also, need to get a separate Tinderbox tree, since it’s going to cause a bazillion new columns.
• Joel Reymont noted in bug 513076 that there are serious drawbacks to getting our libraries in the dyld shared cache on Mac, so has deprioritized that work.
• No updates on Zack’s CSS parser changes in bug 513149.

As usual, more details and links are available on the project wiki, and we’re available to answer questions in #startup on irc.mozilla.org.

UPDATE: Fixed link to full report.

Firefox Startup Performance Weekly Summary

No numbers summary this week, as 1) there weren’t any major landings and 2) I’m working on a script to automate the generation of these summarized numbers. Updates on the week’s activity is below. As usual, more details and links are available on the project wiki, and we’re available to answer questions in #startup on irc.mozilla.org.

• Taras and Joel are working on bug 524202, tracking down exactly how and when dynamic library code is loaded. See this comment for a good summary of the issue.
• I think I’ve found a scenario for stable cold startup numbers on Windows, which is basically: 1) Run consume.exe for N seconds where N is how long it takes to consume all physical RAM (and which also pegs the CPU), 2) sleep for 30 seconds (or however long it takes for the system to quiet down) and 3) measure startup time as usual. Next step is to get a Talos patch up, and work with Rel/Eng to get it deployed into testing so we can see numbers on real Talos boxes.
• Rob Strong split up the update service in bug 311965, has most reviews (affects all toolkit apps) and is about ready to land. This showed a significant win on WinCE startup.

Projects in a holding pattern:

• Drew has a patch up for bug 506814, getting rid of Change GetPersistentDescriptor/SetPersistentDescriptor on Mac, just needs review from Josh.
• Bug 512645, removing the setTimeout 10ms wait in chrome JS, is just waiting on review just needs to be landed (thanks jesse).
• Ben Hsieh has been prototyping a whole Fastload cache replacement in bug 520309.
• Ted has been looking at re-enabling rebasing on Windows in bug 484799 for a potential performance boost there.
• Service caching work in bug 516085 still needs to be pushed to the Places branch for testing.
• Moving font-loading out of the startup path on Mac: Jonathan Kew filed bug 519445 with a WIP patch for yet further reductions in Mac startup time spent in font system initialization.
• JARification: David abandoned moving JS modules into a JAR file, since those files are fastloaded. However, since we want things like post-extension-install restarts to be fast, and those cause fastload cache invalidation, we might want to do things like this anyways. I filed a bug for the same treatment for components. These are lower priority, since they’re not the normal startup case. Follow along with all JAR-ification via the tracker bug.
• Startup Timeline: No updates, still not landed. Add [ft] in the whiteboard of your bug w/ the function names you want timed and David will generate it and update the bug.
• Static Analysis: No progress on bug 506128. David needs to file a bug with the final log of named-yet-uncalled functions.
• Dirty Profile Testing: No progress. Need to list scenarios, file bugs for each, generate Talos config patches and profile data, and then move it into Rel-Eng territory. Also, need to get a separate Tinderbox tree, since it’s going to cause a bazillion new columns.
• Joel Reymont noted in bug 513076 that there are serious drawbacks to getting our libraries in the dyld shared cache on Mac, so has deprioritized that work.
• No updates on Zack’s CSS parser changes in bug 513149.

Firefox Startup Performance Weekly Summary

First, the numbers. This is the first round where all the posted numbers are from Talos. We’re getting closer to having Windows numbers for cold startup (details further down). The cold numbers didn’t have much in the way of results yet, only 3-5 boxes for today’s numbers, and given the variability we should probably put more boxes on those. The notable datapoint is that cold startup on Mac for 3.6 is better than for trunk, which is odd since it’s been the opposite in all of our manual testing, and most of the big wins haven’t made it to the branch yet. It could be because of the dearth of results so far. Next week I’ll include the dirty profile test results in these tables as well.

Cold Startup

Platform	3.5	3.6	Trunk
Mac Leopard (10/23)	15605ms	13120ms (-16%)	13859ms (-11%)
Win XP
Win Vista
Linux (10/23)	7056ms	7159ms (1%)	7204ms (2%)

Warm Startup

Platform	3.5	3.6	Trunk
Mac Leopard (10/23)	1451ms	1108ms (-23%)	1017ms (-30%)
Win XP (10/23)	459ms	462ms (0%)	449ms (-2%)
Win Vista (10/23)	535ms	544ms (1%)	506ms (-5%)
Linux (10/23)	625ms	632ms (1%)	629ms (0%)

As usual, more details and links are available on the project wiki, and we’re available to answer questions in #startup on irc.mozilla.org.

• Taras is zooming in on library IO, and posted some details and optimization approaches, and today posted a log of what’s loaded and how long it takes.
• Windows Cold Ts: As you can see above in the table, the new cold startup graphs are here for Mac and Linux. I’ve made progress on emulating cold startup on Windows using a utility from the Windows Server 2003 Resource Kit called Consume.exe. I found a reference to it in some random blog comment, and then found it on MDC as the #2 link on Google. The help file that the resource kit installer links from the start menu is… not actualy there, but I did find some tidbits of documentation. It will consume one of physical memory, cpu time, kernel pool memory, disk space (!) and the page file, for the number of seconds specified by the user. Running consume.exe for 15 seconds was enough to completely exhaust my physical ram, and subsequent starts of Firefox trunk are about 22 seconds. Next steps: I’ll continue to test to see what combination of these options gives us the best visibility into changes to cold startup time, and then work with Rel/Eng to get it deployed.
• Alfred Kayser landed bug 511754, which improves JAR file reading efficiency.
• Rob Strong has been making a bunch of changes in the update system to improve startup time, and posted a list of the changes.
• Drew has a patch up for bug 506814, getting rid of Change GetPersistentDescriptor/SetPersistentDescriptor on Mac, just needs review from Josh.
• Peter got review on bug 542615, removing the setTimeout 10ms wait in chrome JS.
• Ben Hsieh has been prototyping a whole Fastload cache replacement in bug 520309.
• Ben’s work on fastload cache invalidation in bug 511761 closed other bugs such as bug 517515 and bug 512827.
• Ted has been looking at re-enabling rebasing on Windows in bug 484799 for a potential performance boost there.

Projects in a holding pattern:

• Service caching work in bug 516085 still needs to be pushed to the Places branch for testing.
• Moving font-loading out of the startup path on Mac: Jonathan Kew filed bug 519445 with a WIP patch for yet further reductions in Mac startup time spent in font system initialization.
• JARification: David abandoned moving JS modules into a JAR file, since those files are fastloaded. However, since we want things like post-extension-install restarts to be fast, and those cause fastload cache invalidation, we might want to do things like this anyways. I filed a bug for the same treatment for components. These are lower priority, since they’re not the normal startup case. Follow along with all JAR-ification via the tracker bug.
• Startup Timeline: No updates, still not landed. Add [ft] in the whiteboard of your bug w/ the function names you want timed and David will generate it and update the bug.
• Static Analysis: No progress on bug 506128. David needs to file a bug with the final log of named-yet-uncalled functions.
• Dirty Profile Testing: No progress. Need to list scenarios, file bugs for each, generate Talos config patches and profile data, and then move it into Rel-Eng territory. Also, need to get a separate Tinderbox tree, since it’s going to cause a bazillion new columns.
• Joel Reymont noted in bug 513076 that there are serious drawbacks to getting our libraries in the dyld shared cache on Mac, so has deprioritized that work.
• No updates on Zack’s CSS parser changes in bug 513149.

Firefox Startup Performance Weekly Summary

The numbers aren’t updated yet, as they were oddly counter-intuitive. Firefox 3.5 showed a massive week-over-week improvement in cold startup on Windows, which from what I can tell is not expected. On Leopard, cold startup shows a couple of percentage point improvement over last week, which is expected. Warm startup for Mac shows a 20% improvement over 3.5, but a 10% *regression* from last week, contradicting the numbers from Ts. Again, counter-intuitive numbers given that we landed a bunch of changes focused squarely on startup performance during that period.

Fortuitously, Alice and the release engineering team deployed automated cold startup testing for Mac and Linux. This gives us per-checkin visibility of cold startup times, and removes the need for error-prone local measurements for those platforms. On Windows we haven’t yet figured out how to emulate cold startup reliably, so that’s the next step.

As usual, more details and links are available on the project wiki, and we’re available to answer questions in #startup on irc.mozilla.org.

Recent activity:

• Bug 511761 landed, Ben Hsieh’s work to optimize fastload cache invalidation, with a 3% win on warm startup of WinXP.
• Alfred Kayser put a patch up on bug 511754, which improves JAR file reading efficiency.
• Rob Strong closed bug 521956 and started some cleanup of nsUpdateService, further reducing the size of it for bug 311965.
• Drew has a patch up for bug 506814, getting rid of Change GetPersistentDescriptor/SetPersistentDescriptor on Mac.
• Bug 504858 pushes back the population of the bookmarks toolbar until after the browser window comes up. Dao put up a new patch. Measuring the wall-clock effect of this on startup, and determining what exactly is “gaming” the Ts test is part of the work here.
• Service caching work in bug 516085 still needs to be pushed to the Places branch for testing.

Projects in a holding pattern:

• Moving font-loading out of the startup path on Mac: Jonathan Kew filed bug 519445 with a WIP patch for yet further reductions in Mac startup time spent in font system initialization.
• JARification: David abandoned moving JS modules into a JAR file, since those files are fastloaded. However, since we want things like post-extension-install restarts to be fast, and those cause fastload cache invalidation, we might want to do things like this anyways. I filed a bug for the same treatment for components. These are lower priority, since they’re not the normal startup case. Follow along with all JAR-ification via the tracker bug.
• Startup Timeline: No updates, still not landed. Add [ft] in the whiteboard of your bug w/ the function names you want timed and David will generate it and update the bug.
• Static Analysis: No progress on bug 506128. David needs to file a bug with the final log of named-yet-uncalled functions.
• Dirty Profile Testing: No progress. Need to list scenarios, file bugs for each, generate Talos config patches and profile data, and then move it into Rel-Eng territory. Also, need to get a separate Tinderbox tree, since it’s going to cause a bazillion new columns.
• Joel Reymont noted in bug 513076 that there are serious drawbacks to getting our libraries in the dyld shared cache on Mac, so has deprioritized that work.
• No updates on Zack’s CSS parser changes in bug 513149.

Firefox Startup Performance Weekly Summary

Work on blockers for 3.6 stole some time last week, but some startup work advanced nonetheless, including a bunch of landings. I’ve posted the numbers from early last week below. The percentages are the difference from 3.5. Given the spate of landings later in the week after we measured,  I’ll have to update the numbers again to get the full effect of everything listed below. As usual, more details and links are available on the project wiki, and we’re available to answer questions in #startup on irc.mozilla.org.

Cold Startup (median results from Juan and myself)

Platform	3.5	3.6	Trunk
Mac Leopard (10/6)	12161	10440 (-14%)	10175 (-16%)
Win XP (10/4)	5610	5640 (0%)	4050 (-27.8%)

Warm Startup (median of results from Talos, updated 10/6)

Platform	3.5	3.6	Trunk
Mac Leopard	1500ms	1190ms (-20%)	1040ms (-30%)
Win XP	458ms	470ms (+2%)	468ms (+2%)
Win Vista	545ms	544ms (0%)	545ms (0%)
Linux	624ms	634ms (0%)	634ms (0%)

Recent landings:

• Ryan landed bug 475289 to lazily initialize the engineMetadataService, bug 520342 to consolidate service initialization in the microsummary service, and pushed bug 499123, coalescing browser about: pages, to the 3.6 branch.
• Taras landed a bunch of optimizations to the fastload system as well as his work on combining the different preference files.
• I turned on PGO for Places, mozStorage and SQLite.
• Alfred Kayser’s patch on bug 510844 landed, which should increase throughput of JAR file reading.
• Ben Hsieh got review on bug 510991, which removes some stats() from the startup path.

Recent activity:

• Ryan put up a patch for bug 520284, which utilizes an important change that happened recently in bug 471219 which allows components to register for periodic timer notifications *without* instantiating the service or component. An example is in Ryan’s patch, and the docs are in the source.
• Bug 504858 pushes back the population of the bookmarks toolbar until after the browser window comes up. Dao put up a new patch. Measuring the wall-clock effect of this on startup, and determining what exactly is “gaming” the Ts test is part of the work here.
• Ben Hsieh is in review cycles for bug 511761 which optimizes the fastload cache invalidation, and consolidates some of the invalidation triggers.
• Service caching work in bug 516085, still made no progress. This week I’ll try pushing this to the Places branch.
• No updates on Zack’s CSS parser changes in bug 513149.
• Cold Startup Testing: Alice put more patches on bug 510587, getting us ever closer to automated testing of cold startup.

Projects in a holding pattern:

• Moving font-loading out of the startup path on Mac: Jonathan Kew filed bug 519445 with a WIP patch for yet further reductions in Mac startup time spent in font system initialization.
• JARification: David abandoned moving JS modules into a JAR file, since those files are fastloaded. However, since we want things like post-extension-install restarts to be fast, and those cause fastload cache invalidation, we might want to do things like this anyways. I filed a bug for the same treatment for components. These are lower priority, since they’re not the normal startup case. Follow along with all JAR-ification via the tracker bug.
• Startup Timeline: No updates, still not landed. Add [ft] in the whiteboard of your bug w/ the function names you want timed and David will generate it and update the bug.
• Static Analysis: No progress on bug 506128. David needs to file a bug with the final log of named-yet-uncalled functions.
• Dirty Profile Testing: No progress. Need to list scenarios, file bugs for each, generate Talos config patches and profile data, and then move it into Rel-Eng territory. Also, need to get a separate Tinderbox tree, since it’s going to cause a bazillion new columns.
• Joel Reymont noted in bug 513076 that there are serious drawbacks to getting our libraries in the dyld shared cache on Mac, so has deprioritized that work.

The awesomebar for command-line filesystem traversal… for Windows

Autojump is a command-line utility that “learns” from your filesystem navigation via the “cd” command, and allows you to jump quickly to oft-travelled-to directories. Source, installation and usage information are at Github. After seeing this tweet from Dion, I went to install it, only to remember that I’m on Windows 7 now. Bah. So, I tweaked it a bit to run inside the MozillaBuild environment. Assuming you’ve cloned/downloaded Autojump, here are the steps to get it working:

1. Open Mingw, navigate to the autojump source directory
2. Remove all instances of “sudo” from the install.sh file
3. Get your Python path: $ which python
4. Replace /usr/bin/python with your Python path in the autojump file
5. Run install.sh

Firefox Startup Performance Weekly Summary

This week brought a big win on Mac, and a slew of changes that are about to land.

Recent activity:

• Bug 517045 is fixed and brings another win on Mac. Found by Joel Reymont and fixed by John Daggett, it improves cold startup by ~20% and warm startup by ~4%. It gets better: Jonathan Kew filed bug 519445 with a WIP patch for yet further reductions in Mac startup time spent in font system initialization.
• Taras Glek’s work on combining the different preference files into a single one is ready to land.
• We now have unit-tested optimized builds, thanks to Release Engineering’s work on bug 486783. This means we can now turn on PGO for Places, mozStorage and SQLite, which I’ll land presently.
• Bug 504858 pushes back the population of the bookmarks toolbar until after the browser window comes up. The patch has review, is ready to land.
• Alfred Kayser’s patch on bug 510844 which should increase throughput of JAR file reading, is ready to land.
• Ben Hsieh got review on bug 510991, which removes some stats() from the startup path.
• I’m no longer able to reproduce the cold startup regression from 3.5 to 3.6. I turned of SuperFetch, which resulted in more stable numbers, but there was no visible regression, even in builds going back a couple of months. Juan is going to test on Windows XP.
• Ben Hsieh has a patch up for review on bug 511761, which removes needless stat()s of component files, and improves and clarifies current cache invalidation behavior.
• Service caching work in bug 516085, made no progress. Next week I’ll try pushing this to the Places branch to get a better idea of the total performance impact of the change.
• Zack is working on major CSS parser changes in bug 513149.

Projects in a holding pattern:

• Cold Startup Testing: Drew and Alice made a bunch of progress on bug 510587, to create a new Ts that measures cold startup. Alice is working on mobile Talos though, so this is sidelined for a bit. The only issue left is reliable Windows measurement, but we’re not going to block on it, can live with Mac and Linux to start off.
• JARification: David abandoned moving JS modules into a JAR file, since those files are fastloaded. However, since we want things like post-extension-install restarts to be fast, and those cause fastload cache invalidation, we might want to do things like this anyways. I filed a bug for the same treatment for components. These are lower priority, since they’re not the normal startup case. Follow along with all JAR-ification via the tracker bug.
• Startup Timeline: No updates, still not landed. Add [ft] in the whiteboard of your bug w/ the function names you want timed and David will generate it and update the bug.
• Static Analysis: No progress on bug 506128. David needs to file a bug with the final log of named-yet-uncalled functions.
• Dirty Profile Testing: No progress. Need to list scenarios, file bugs for each, generate Talos config patches and profile data, and then move it into Rel-Eng territory. Also, need to get a separate Tinderbox tree, since it’s going to cause a bazillion new columns.
• Joel Reymont noted in bug 513076 that there are serious drawbacks to getting our libraries in the dyld shared cache on Mac, so has deprioritized that work.