On Sun, Aug 6, 2017 at 10:48 AM, Otto van der Schaaf <
osc...@we-amp.com> wrote:
> I think a capture of the issue with:
> - chrome://net-internals/ of a delayed response may be helpful.
> - Plus verbose logs from squid for the same (if possible), it would be good
> to see what is going on between squid and the pagespeed enabled server in
> terms of timings and request/response headers.
> - Plus a log of memcached in verbose mode
good idea, otto.
> Maybe with those, we can figure out what happens.
yehyeh... hmmm.... chrome://net-internals shows a loootta info... i
have 50 tabs open and gmail seems to get stuff using AJAX... i'll have
to set up a separate chrome instance just to isolate the traffic...
before i do that, here's the relevant section of an appropriate
request - you can see a whopping 3 *seconds* in between request and
read response headers.
t=69785 [st= 303] +HTTP_TRANSACTION_SEND_REQUEST [dt=0]
t=69785 [st= 303] HTTP_TRANSACTION_SEND_REQUEST_HEADERS
--> GET
http://horseboxseller.com/ HTTP/1.1
Host:
horseboxseller.com
Proxy-Connection: keep-alive
Cache-Control: max-age=0
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (X11; Linux
x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76
Safari/537.36
Accept:
text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Referer:
http://horseboxseller.com/horseboxes-for-sale/detail/1772/3.5-ton/2006-model-55-vauxhaul-movano-coach-built-by-chaighley-76-000-miles-stalled-for-2-rear-facing-large-external-tack-locker/
Accept-Encoding: gzip, deflate, sdch
Accept-Language:
en-US,en;q=0.8,zh-CN;q=0.6,zh;q=0.4,pl;q=0.2
Cookie: [312 bytes were stripped]
t=69785 [st= 303] -HTTP_TRANSACTION_SEND_REQUEST
t=69785 [st= 303] +HTTP_TRANSACTION_READ_HEADERS [dt=3132]
t=69785 [st= 303] HTTP_STREAM_PARSER_READ_HEADERS [dt=3132]
t=72917 [st=3435] HTTP_TRANSACTION_READ_RESPONSE_HEADERS
--> HTTP/1.1 200 OK
Date: Sun, 06 Aug 2017 15:42:33 GMT
Server: Apache/2.4.10 (Debian)
Vary: Accept-Encoding
X-Mod-Pagespeed: 1.12.34.2-0
Cache-Control: max-age=0, no-cache
Content-Length: 33836
Content-Type: text/html; charset=UTF-8
Proxy-Connection: keep-alive
t=72917 [st=3435] -HTTP_TRANSACTION_READ_HEADERS
then here's one for a different page, you can see the time delay is...
tiny by comparison: st=280... st=779 i presume those are in
milliseconds, so around half a second (not three!!)
btw i'm in taiwan, server's in the UK, ping round-trips are
around...270ms over the VPN i'm running the proxy over. also i know
from webmaster tools that the response time of the server is around
200ms, so overall 500ms sounds about right.
more when i've got it set up.
t=4235 [st= 280] -HTTP_STREAM_REQUEST
t=4235 [st= 280] +HTTP_TRANSACTION_SEND_REQUEST [dt=0]
t=4235 [st= 280] HTTP_TRANSACTION_SEND_REQUEST_HEADERS
--> GET
http://horseboxseller.com/horseboxes-for-sale/ HTTP/1.1
Host:
horseboxseller.com
Proxy-Connection: keep-alive
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (X11; Linux
x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76
Safari/537.36
Accept:
text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Referer:
http://horseboxseller.com/
Accept-Encoding: gzip, deflate, sdch
Accept-Language:
en-US,en;q=0.8,zh-CN;q=0.6,zh;q=0.4,pl;q=0.2
Cookie: [544 bytes were stripped]
t=4235 [st= 280] -HTTP_TRANSACTION_SEND_REQUEST
t=4235 [st= 280] +HTTP_TRANSACTION_READ_HEADERS [dt=499]
t=4235 [st= 280] HTTP_STREAM_PARSER_READ_HEADERS [dt=499]
t=4734 [st= 779] HTTP_TRANSACTION_READ_RESPONSE_HEADERS
--> HTTP/1.1 200 OK
Date: Sun, 06 Aug 2017 15:57:35 GMT
Server: Apache/2.4.10 (Debian)
Vary: Accept-Encoding
X-Mod-Pagespeed: 1.12.34.2-0
Cache-Control: max-age=0, no-cache
Content-Length: 46140
Content-Type: text/html; charset=UTF-8
Proxy-Connection: keep-alive
t=4734 [st= 779] -HTTP_TRANSACTION_READ_HEADERS
t=4734 [st= 779] HTTP_CACHE_WRITE_INFO [dt=0]