1449785 - BMO is not serving using HTTP/2.0 any more

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: Infrastructure, defect)

Description

[Dylan Hardison [:dylan] (he/him)]

I just noticed we're not serving content as HTTP/2.0 post-migration. BMO benefits immensely from that -- quite a difference in perceived performance.

Comment 1

[Dylan Hardison [:dylan] (he/him)]

+ if it will be a while before we can have that, we're going to need to re-apply asset concatenation and minification.

Comment 2

[Chris Kolosiwsky [:ckolos] (ckolos has left the building)]

Re-enabling this will require a not-insignificant architecture change to ALB's from ELB's. In order to do that, I'd like to:

1) Collect ~1 months worth of traffic data on the ELB's
2) Analyze it because  ELB -> ALB traffic isn't a 1:1 comparison
3) Test *extensively* in dev/stage prior to moving to prod.

Right now, we (ops) aren't ready for this effort, but we will put this on the short list of things to get done ASAP.

Comment 3

[Kohei Yoshino [:kohei]]

If it takes time to re-enable HTTP/2, we should probably re-enable the CSS/JavaScript file concatenation. I hesitate to add new JavaScript files because of this.

Comment 4

[u673061]

I have captured a file reproducing this bug using Wireshark and the file is on Google Drive here because it exceeds the 10MB limit:
https://drive.google.com/file/d/13EL_rL_3BOXQFtzEKtcAMt2csBNkM8la/view?usp=sharing

Comment 5

[u673061]

It seems that the issue is resolved as of today (March 14 2022 PDT) and the production bugzilla.mozilla.org is serving through HTTP/2.0 properly.
Please confirm if it is fixed.

Comment 6

[David Lawrence [:dkl]]

This has been remedied so this can be closed now.