Marketplace/Performance optimization

From MozillaWiki
Jump to navigation Jump to search

This is a page to aggregate information about Marketplace performance efforts; it will be maintained as they morph into and overlap with Tarako-specific issues.

Want to contribute?

Log new bugs in Bugzilla, with the "perf" keyword

Ask about things in #marketplace.

Mitigation strategies

The short version is that we need to optimize things that should be optimized regardless of other constraints (device constraints, network constraints, etc). Only then can we differentiate between strategic investment and Doing Things The Right Way.

At a high level, these are the strategies being considered for marketplace.firefox.com:

  1. Feature/Memory/Device detection (reliable) (900241)
  2. Speed and Performance bugs, general at this point (see below)
    1. Establish target benchmarks & KPIs for performance
  3. Front and Back-end Performance adjustments (pending benchmark results -- currently the mark is "as fast as possible")

Tarako-specific:

  1. new "low resource" packaged app
  2. Filtering apps for "low resource" device
  3. UI updates to accommodate RTL & other local language requirements (pending target markets)

Open issues

These are immediate questions:

These are future issues:

Open performance bugs

These bugs have been identified as delivering good performance increases; they are grouped here for ease of consideration.

Note that not all of these are Marketplace bugs, and thus not all are in the priority groupings at the bottom of the page.

overall speed

  • 991301
  • 871683 -- NOTE: not Marketplace. Server Ops. Note: thus far, SPDY tests have not demonstrated substantial improvements. Still investigating.

improve API response time

improve caching techniques

optimize asset delivery

optimize synchronous delivery

  • 847679 -- this one is big, mostly because it depends on...

optimize first run

  • 897156 -- ... becoming a real packaged app.

Performance bugs (general)

This is a listing of Marketplace bugs only, by priority. If a priority has not been applied, you will have to find it directly. Here's a good place to start

Open P1-P3

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Open P4-P5

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Resolved: Fixed

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Resolved: Deferred

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Performance data dashboards