Re: Specify a Vary: Accept-Encoding header

2017-07-24 Thread Peter Booth
Phillip, Right now this Rails website is almost too slow to tune, and so you will need to make some radical changes that you might later choose to undo. You should run the rails app in production mode, which, by default will cache everything. That should give you th breathing room needs dto ru

Re: Specify a Vary: Accept-Encoding header

2017-07-21 Thread Peter Booth
It looks as if the static content is being served by the Rails asset pipeline rather than directly by nginx and the impact is enormous. It took 25s for the base page - but it also took another 25s for the http://cryonics.org.au/assets/application.js

Re: Specify a Vary: Accept-Encoding header

2017-07-20 Thread Richard Stanway
The issue is not with your page size or gzip (or anything nginx related actually). Your Rails backend is generating the content far too slow. You should investigate why your backend is so slow. time_namelookup: 0.004209 time_connect: 0.241082 time_appconnec

Specify a Vary: Accept-Encoding header

2017-07-19 Thread Philip Rhoades
People, I have moved my (very low hit) web sites from a Digital Ocean server to my own Fedora 25 x86-64 server with 8GB RAM and an ADSL2+ upload speed of only about 1Mbit/sec. The plain HTML and Jekyll sites response times are not too bad but the Rails sites are very slow. Using: https: