Closed Bug 759627 Opened 13 years ago Closed 13 years ago

Add gzip compression to slavealloc UI requests

Categories

(Release Engineering :: General, defect, P2)

x86
All
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Assigned: nthomas)

Details

Loading slavealloc has become painful for me - 10 to 20 seconds to get http://slavealloc.build.mozilla.org/ui/#slaves ready for action. Not all of this can be blamed on soggy string connections to the South Pacific. The biggest offender is requests to http://slavealloc.build.mozilla.org/api/slaves [HTTP/1.1 200 OK 4101ms] Adding gzip compression helps in slavealloc-staging.
Bear I dropped this in /etc/nginx/conf.d/slavealloc-staging.conf gzip on; gzip_types text/css application/x-javascript application/json; gzip_comp_level 3; and got load times 2 to 3 times quicker on the slaves request. It deliberately leaves out text/plain so that gettac requests can't be regressed. I propose we put this in both slavealloc configs. How does it look ? Puppet doesn't seem to be running on this box, but scl3 nagios sure is persistent about wanting to talk to it.
(In reply to Nick Thomas [:nthomas] from comment #1) > Bear I dropped this in /etc/nginx/conf.d/slavealloc-staging.conf > gzip on; > gzip_types text/css application/x-javascript application/json; > gzip_comp_level 3; > and got load times 2 to 3 times quicker on the slaves request. It > deliberately leaves out text/plain so that gettac requests can't be > regressed. > > I propose we put this in both slavealloc configs. How does it look ? > > Puppet doesn't seem to be running on this box, but scl3 nagios sure is > persistent about wanting to talk to it. good catch! I'm surprised we went this long without noticing that we were *not* doing gzip. +1
I added the change to slavealloc.conf and slavealloc-staging.conf and reloaded nginx.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.