Marketplace/Performance optimization
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:
- Feature/Memory/Device detection (reliable) (900241)
- Speed and Performance bugs, general at this point (see below)
- Establish target benchmarks & KPIs for performance
- Front and Back-end Performance adjustments (pending benchmark results -- currently the mark is "as fast as possible")
Tarako-specific:
- new "low resource" responsive state
- Filtering apps for "low resource" device
- UI updates to accommodate RTL & other local language requirements (pending target markets)
Open issues
These are immediate questions:
- should change investigate using SPDY (957388) to "using SPDY?" -- does this need a separate ticket?
- Use CDN, etc (983815) <-- Jeremy from IT is looking at using one CDN for images, one for API?
- There is an open github issue with Persona
These are future issues:
- Becoming a real packaged app (897156) appears to be blocked by external factors (Persona, still?) -- but is this even possible for Tarako?
- Related, having the feature detection API (983502) as originally described -- this isn't a Marketplace bug, so we're implementing something else for 1.3 and hope to have this for 1.4, 1.5 at the latest.
Performance bugs, first batch
These bugs have been identified as delivering good performance increases; they are grouped here for ease of consideration. With two exceptions, they are fairly simplistic in effort. All bugs are open unless
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
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 dashboard
Not sure how these apply to bugs yet, because not sure how these poll yet. We're discussing other measurement tools, but here's what there is now: