Categories: developers jetpack sdk

SDK 1.3 performance impact

Recently Jorge Villalobos ran some tests to measure the impact of using the SDK on Firefox start-up time. Jorge published his finding to the Jetpack google news group. His results were encouraging:

The results were very favorable this time, with the
empty add-on adding only 1.8% (11ms) to startup, and Infocon adding only
3.6% (22ms), on average. As a reference point, after our initial tests
we decided that 7% was roughly the line where add-on startup overhead
stopped being “Excellent” and began being just “Good”.

The methodology of these tests was to measure Firefox start-up time under three different scenarios:

  1. using a clean profile with no addons enabled.
  2. with a single ’empty’ SDK-based add-on enabled.
  3. with a non-trivial add-on enabled.

The great thing about this is that we now have solid data that indicates SDK version 1.3 itself has little effect on Firefox start-up time however, as Jorge suggests, there is much more testing that could be done. In particular, we should continue to run these tests to ensure that future versions of the SDK do not degrade start-up performance as we add new modules or make infrastructure changes to the SDK.

If you’re curious, we test start-up impact using Talos according to this methodology:

If you want to run the tests yourself, Talos is relatively straightforward to set up:

I should warn you that the tests themselves can take quite some time to complete!

One comment on “SDK 1.3 performance impact”

  1. adle wrote on