[英]TTFB increated by 200+ ms after enabling SSL via Nginx Ingress controller & cert-manager
Right after enabling cert-manager in Ingress Controller by TTFB (time to first byte) increased by 200+ms in most of the regions.在通过 TTFB(到第一个字节的时间)在Ingress Controller 中启用 cert-manager 之后,在大多数区域中增加了 200+ms。 Without SSL, it was <200ms to 80% of the regions.在没有 SSL 的情况下,80% 的区域不到 200 毫秒。 After enabling SSL only 30% have TTFB <200ms启用 SSL 后,只有 30% 的 TTFB <200ms
My Ingress definition:我的入口定义:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: test-ingress
annotations:
kubernetes.io/ingress.class: nginx
certmanager.k8s.io/cluster-issuer: letsencrypt-prod
kubernetes.io/tls-acme: "true"
spec:
rules:
- host: gce.wpspeedmatters.com
http:
paths:
- path: /
backend:
serviceName: wordpress
servicePort: 80
tls:
- secretName: tls-prod-cert
hosts:
- gce.wpspeedmatters.com
Switched to TLS 1.3 and I was able to above shave off extra 50-150ms!切换到 TLS 1.3,我能够节省额外的 50-150 毫秒!
I wrote a detailed blog post too: https://wpspeedmatters.com/tls-1-3-in-wordpress/我也写了一篇详细的博客文章: https : //wpspeedmatters.com/tls-1-3-in-wordpress/
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.