TTFB is very high on Proxmox VE 5.0

rarirureluis

Renowned Member
Jul 14, 2015
9
0
66
When I updated Proxmox VE 5.0, My web site's TTFB(Time to First Byte) is very high.(35sec).
My proxmox server is 1 node that is working 20 lxc containers.

I break down the issue into parts, I configured Router directs access to Mac(web server),
TTFB is 1sec.

Why the container that is web server on proxmox is very high TTFB?

```
proxmox-ve: 5.0-20 (running kernel: 4.10.17-2-pve)
pve-manager: 5.0-30 (running version: 5.0-30/5ab26bc)
pve-kernel-4.10.1-2-pve: 4.10.1-2
pve-kernel-4.10.17-2-pve: 4.10.17-20
pve-kernel-4.10.17-1-pve: 4.10.17-18
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve3
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-15
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-6
libpve-storage-perl: 5.0-14
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-4
pve-container: 2.0-15
pve-firewall: 3.0-2
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.11-pve17~bpo90
```
 
usually these kind of very long accesses are non working reverse DNS lookups
I don't think this is something which has to do with PVE. Or you need to run the Web server in PVE, and compare the TTFB with the web server running in the host vs web server running inside the guest.
 
Thanks maru.

My local dns server is working reverse dns lookup.
[root@dns ~]# host 192.168.20.15
15.20.168.192.in-addr.arpa domain name pointer nginx.luis.local.
[root@dns ~]# host 192.168.20.8
8.20.168.192.in-addr.arpa domain name pointer app.luis.local.
These servers work in PVE.
nginx.luis.local is reverse proxy and app.luis.local is web server.

When I nginx.luis.local proxy to Mac, TTFB is 1sec.