View source for 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 [https://bugzilla.mozilla.org/enter_bug.cgi?assigned_to=nobody@mozilla.org&bug_status=NEW&cc=ddurst@mozilla.com&contenttypemethod=autodetect&contenttypeselection=text/plain&form_name=enter_bug&keywords=perf&priority=--&product=Marketplace 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:

# [https://bugzilla.mozilla.org/show_bug.cgi?id=900241 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 ==
<b>These are immediate questions:</b>
* [https://github.com/mozilla/persona/issues/4105 There is an open github issue with Persona about ETags...]
* [https://github.com/mozilla/persona/issues/3778 ...and one about it failing with packaged apps.]

<b>These are future issues:</b>
* 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.

== 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 ===
* {{Bugzilla|991301}}
* {{Bugzilla|871683}} -- NOTE: not Marketplace. Server Ops. Note: thus far, SPDY tests have not demonstrated substantial improvements. Still investigating.

=== improve API response time ===
* {{Bugzilla|988557}}
* {{Bugzilla|989181}}
* {{Bugzilla|991955}}

=== improve caching techniques ===
* {{Bugzilla|957383}}
* {{Bugzilla|985291}}
* {{Bugzilla|985292}}
* {{Bugzilla|985293}}
* {{Bugzilla|985804}}

=== optimize asset delivery ===
* {{Bugzilla|874999}}
* {{Bugzilla|987403}}
* {{Bugzilla|987851}}
* {{Bugzilla|988674}}

=== optimize synchronous delivery ===
* {{Bugzilla|847679}} -- this one is big, mostly because it depends on...

=== optimize first run ===
* {{Bugzilla|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. [https://bugzilla.mozilla.org/buglist.cgi?priority=--&keywords=perf&keywords_type=allwords&list_id=9800214&resolution=---&query_format=advanced&product=Marketplace Here's a good place to start]

=== Open P1-P3 ===
<bugzilla>
{
    "product": "Marketplace",
    "status": ["NEW", "ASSIGNED"],
    "resolution": "---", 
    "priority": ["P1", "P2", "P3"],
    "keywords": "perf",
    "include_fields": "id, product, component, priority, severity, status, summary, assigned_to, last_change_time"
}
</bugzilla>


=== Open P4-P5 ===
<bugzilla>
{
    "product": "Marketplace",
    "status": ["NEW", "ASSIGNED"],
    "resolution": "---", 
    "priority": ["P4", "P5"],
    "keywords": "perf",
    "include_fields": "id, product, component, priority, severity, status, summary, assigned_to, last_change_time"
}
</bugzilla>


=== Resolved: Fixed ===
<bugzilla>
{
    "product": "Marketplace",
    "status": "RESOLVED",
    "resolution": "FIXED", 
    "keywords": "perf",
    "include_fields": "id, product, component, priority, severity, status, summary, assigned_to, last_change_time"
}
</bugzilla>


=== Resolved: Deferred ===
<bugzilla>
{
    "product": "Marketplace",
    "status": "RESOLVED",
    "resolution": "WONTFIX", 
    "keywords": "perf",
    "include_fields": "id, product, component, priority, severity, status, summary, assigned_to, last_change_time"
}
</bugzilla>


== Performance data dashboards ==
* [https://metaplace.paas.allizom.org/apikiosk/ API Speed dashboard]
* [http://eideticker.mozilla.org/b2g/#/inari/b2g-marketplace-startup/timetostableframe Time to full display of Marketplace app (warm)]
* [http://dashboard.mktadm.ops.services.phx1.mozilla.com/graphite-api (VPN required) ops level dashboard]