Mobile app version of vmapp.org
Login or Join
Heady270

: Performance Issues Using SSL With Cloudflare I have been using Cloudflare for a while without much consideration to what it was doing. Today I have noticed that there is around 500ms of delay

@Heady270

Posted in: #Cdn #Cloudflare #Https #Performance #Ttfb

I have been using Cloudflare for a while without much consideration to what it was doing. Today I have noticed that there is around 500ms of delay when I view a web page over https when Cloudflare is turned on for the domain.

Both resources below confirm that the use of https on a website should have no impact on the performance.
stackoverflow.com/questions/149274/http-vs-https-performance https://www.keycdn.com/blog/https-performance-overhead/

I have 2 websites running on the same server. Both using SSL, but only one with cloudflare as a proxy. The normal https site has an average TTFB of 140ms (php home page) and the site using cloudflare has a TTFB of 600ms when viewing a 1kb html file. I setup a new subdomain and pointed it at the same site. I then setup an A record in Cloudflare and set it up so it would bypass the Cloudflare proxy. The same 1kb html file loaded with a TTFB of 84ms over http with the new subdomain.

My settings in the Crypto section of Cloudflare are as follows.


SSL : Active (Full)
Origin Certificates : None
Always Use HTTPS : No
HTTP Strict Transport Security: Off
Authenticated Origin Pulls: Off
Opportunistic Encryption: Off
TLS 1.3: Enabled+ORTT


Any help on this would be greatly appreciated.

10.01% popularity Vote Up Vote Down


Login to follow query

More posts by @Heady270

1 Comments

Sorted by latest first Latest Oldest Best

 

@Miguel251

should have no impact on the performance


That's not the case. And its not what I take from the content of the 2 URLs you cited. Having said that, the delays you describe sound unusually high.

Whether TTFB is a useful metric for measuring the performance impact (in the absence of a lot of other information) is somewhat dubious. If your application is configured to push out an early response without using chunking, then this is exactly the behaviour to be expected when the time to the last byte is lengthy (the SSL part will try to buffer a lot of the response).

What is your RTT from the browser to Cloudflare? From Cloudflare to your origin server? Are you using domain sharding? HTTP2?

The first place I would be looking is at the number of RTTs for the SSL handshake. Although I suspect there's not a lot you can do to influence this behaviour.

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme