Marketplace/Performance optimization
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 Tarako-specific issues.
Want to contribute?
Log new bugs in Bugzilla, with the "perf" keyword
Ask about things in #marketplace.
Open issues
These are immediate issues:
- should change investigate using SPDY to "using SPDY?" -- does this need a separate ticket?
- Use CDN (etc) <-- Jeremy from IT is looking at using one CDN for images, one for API?
- cache API responses in localForage has a PR open already -- worth keywording as perf at this point?
These are future issues:
- Becoming a real packaged app appears to be blocked by external factors (Persona, still?) -- but is this even possible for Tarako?
- Related, having the feature detection API 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: