Marketplace/Performance optimization: Difference between revisions
Jump to navigation
Jump to search
(updated with strategies, added refs for bugzilla IDs (for those who know them offhand)) |
|||
| Line 6: | Line 6: | ||
Ask about things in #marketplace. | Ask about things in #marketplace. | ||
== Mitigation strategies == | |||
# [https://bugzilla.mozilla.org/show_bug.cgi?id=900241 Feature/Memory/Device detection (reliable) (900241)] | |||
# Speed and Performance bugs, general (P1-P5s listed below) | |||
## Establish target benchmarks & KPIs for performance | |||
# Front and Back-end Performance adjustments (pending benchmark results) | |||
Possibly Tarako-specific: | |||
# Front and Back-end Performance adjustments | |||
## new "low resource" responsive state | |||
## Filtering apps for device (UI) | |||
## payment flow slimming/changes? | |||
# UI updates to accommodate RTL & other local language requirements (pending target markets) | |||
== Open issues == | == Open issues == | ||
<b>These are immediate issues:</b> | <b>These are immediate issues:</b> | ||
* should change [https://bugzilla.mozilla.org/show_bug.cgi?id=957388 investigate using SPDY] to "using SPDY?" -- does this need a separate ticket? | * should change [https://bugzilla.mozilla.org/show_bug.cgi?id=957388 investigate using SPDY (957388)] to "using SPDY?" -- does this need a separate ticket? | ||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=983815 Use CDN ( | * [https://bugzilla.mozilla.org/show_bug.cgi?id=983815 Use CDN, etc (983815)] <-- Jeremy from IT is looking at using one CDN for images, one for API? | ||
<b>These are future issues:</b> | <b>These are future issues:</b> | ||
* [http://bugzilla.mozilla.org/show_bug.cgi?id=897156 Becoming a real packaged app] appears to be blocked by external factors (Persona, still?) -- but is this even possible for Tarako? | * [http://bugzilla.mozilla.org/show_bug.cgi?id=897156 Becoming a real packaged app (897156)] appears to be blocked by external factors (Persona, still?) -- but is this even possible for Tarako? | ||
* Related, [https://bugzilla.mozilla.org/show_bug.cgi?id=983502 having the feature detection API] as [https://bugzilla.mozilla.org/show_bug.cgi?id=900241 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. | * Related, [https://bugzilla.mozilla.org/show_bug.cgi?id=983502 having the feature detection API (983502)] as [https://bugzilla.mozilla.org/show_bug.cgi?id=900241 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 == | == Performance bugs == | ||
Revision as of 20:59, 25 March 2014
This is a page to aggregate information about Marketplace performance efforts; it will be maintained as they morph into Tarako-specific issues.
Want to contribute?
Log new bugs in Bugzilla, with the "perf" keyword
Ask about things in #marketplace.
Mitigation strategies
- Feature/Memory/Device detection (reliable) (900241)
- Speed and Performance bugs, general (P1-P5s listed below)
- Establish target benchmarks & KPIs for performance
- Front and Back-end Performance adjustments (pending benchmark results)
Possibly Tarako-specific:
- Front and Back-end Performance adjustments
- new "low resource" responsive state
- Filtering apps for device (UI)
- payment flow slimming/changes?
- UI updates to accommodate RTL & other local language requirements (pending target markets)
Open issues
These are immediate issues:
- 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?
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
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. But here they are: