Check you site with Ghostery, the CSS does not load.
sounds like a bug in Ghostery?
Lessons learned tuning TCP and Nginx in EC2
11–15 of 15 posts
Re: Lessons learned tuning TCP and Nginx in EC2
#12Check you site with Ghostery, the CSS does not load.
sounds like a bug in Ghostery?
I see this issue a lot with blogs related to tracking companies (Mixpanel, for example). These companies are serving their blog CSS from the same hostname as they serve their tracking code, so Ghostery blocks it.
Re: Lessons learned tuning TCP and Nginx in EC2
#13If I understand this correctly then the huge improvement in latency (from 200ms to 3ms) comes from not having to deal with slow clients directly. Traffic to your front-end server are now only from ELB, and ELB is "spoon-feeding" the web-clients. This is true if you are using ELB in "http-mode".
This also explains why you can cut the front-end servers by 20% - as each request is handled more efficiently (lower latency equals higher throughput). Also, connection-reuse is more efficient as the set of servers in the ELB-pool is more limited that the set of web-clients.
Re: Lessons learned tuning TCP and Nginx in EC2
#14Re: Lessons learned tuning TCP and Nginx in EC2
#15ELBs have terrible TLS support... Cipher suite choice and ordering support is abysmal, and they only recently started supporting newer TLS versions. OCSP stapling isn't supported either.
https://wiki.mozilla.org/Security/Server_Side_TLS#Amazon_Web... gives more information if you're curious.