Open
Bug 1440593
Opened 7 years ago
Updated 3 years ago
https://tiles.services.mozilla.com don't use HTTP2
Categories
(Firefox :: New Tab Page, enhancement, P3)
Firefox
New Tab Page
Tracking
()
NEW
People
(Reporter: bugs, Unassigned)
Details
Attachments
(1 file)
16.86 KB,
image/png
|
Details |
https://tiles.services.mozilla.com doesn't use http2 presumably to support older clients. Upgrading can significantly improve new tab performance.
Comment 1•7 years ago
|
||
:jbuck - could you weigh in on this?
Flags: needinfo?(jbuckley)
Priority: -- → P3
Comment 2•7 years ago
|
||
https://tiles.services.mozilla.com is currently being load balanced by an Elastic Load Balancer (ELB) which doesn't support http2. To be able to use http2 we'd need to migrate to an Application Load Balancer (ALB). A list of things we should look at before doing this change:
- Are the same ciphers supported on ELB and ALB? I need to see the list of supported ciphers, and also pull ELB logs to see what ciphers are being used
- What's the cost difference of ELB vs ALB?
- Can we test the speed difference between ELB/ALB somehow? Is there some existing telemetry in Firefox that could be used for this?
- How should this be rolled out? We can use DNS for % of total requests, but I wonder if it's worth testing this before rolling it out to everyone. Maybe setup a new ALB and change the browser.newtabpage.activity-stream.telemetry.ping.endpoint config to the new ALB for a subset of users?
Updated•7 years ago
|
Flags: needinfo?(jbuckley)
status-firefox66:
--- → disabled
status-firefox67:
--- → disabled
status-firefox68:
--- → disabled
status-geckoview66:
--- → disabled
Updated•6 years ago
|
status-firefox66:
disabled → ---
status-firefox67:
disabled → ---
status-firefox68:
disabled → ---
status-geckoview66:
disabled → ---
Assignee | ||
Updated•6 years ago
|
Component: Activity Streams: Application Servers → New Tab Page
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•