pveproxy has peformance problem with keep alive connection

[languanghao]

When many people use novnc, the api server(web gui, novnc) will not response for new connection. But the novnc alreay opend still working, and the command 'pveproxy status' shows the service is running.

After edit the /usr/share/perl5/PVE/Service/pveproxy.pm, change the 'max_workers' option, pveproxy can accept more connection.

my %daemon_options = (
    max_workers => 3, # change it to 7
    restart_on_error => 5,
    stop_wait_time => 15,
    leave_children_open_on_reload => 1,
    setuid => 'www-data',
    setgid => 'www-data',
    pidfile => '/var/run/wayproxy/wayproxy.pid',
);

Also I metioned :

Proxmox VE 3.0 completely replaces Apache2 with a new event driven API server (pveproxy). This allows efficient support for HTTP keep-alive.

Maybe the pveproxy can not hold keep alive connection very well?

Is there a way to repalces pveproxy with nginx?

 

[dietmar]

Maybe the pveproxy can not hold keep alive connection very well?

Works for me - How many connections do you talk about?

 

[languanghao]

Works for me - How many connections do you talk about?

I have a 3 nodes cluster, and all user visit one node. About 20 novnc connections, the server will lost connection. Restart pveproxy will solve this problem.