It appreciate if you could test bullseye as well. Thanks!
Have updated a server with Buster (on which I've tested Varnish
v6.1.1-1+deb10u3 before) to Bullseye and upgraded Varnish to
6.5.1-1+deb11u2.
The results are pretty much the same as with Buster.
The hosted pages work correctly with HTTP 1.1 trough Varnish.
The same for HTTP2.
Locust against Varnish with 100 req/sec gives stable results for 10min
testing.
user@host:~$ sudo varnishd -V
varnishd (varnish-6.5.1 revision
1dae23376bb5ea7a6b8e9e4b9ed95cdc9469fb64)
Copyright (c) 2006 Verdens Gang AS
Copyright (c) 2006-2020 Varnish Software
user@host:~$ sudo varnishstat -n $(hostname) -1
MGT.uptime 1054 1.00 Management process uptime
MGT.child_start 1 0.00 Child process started
MGT.child_exit 0 0.00 Child process normal exit
MGT.child_stop 0 0.00 Child process unexpected
exit
MGT.child_died 0 0.00 Child process died (signal)
MGT.child_dump 0 0.00 Child process core dumped
MGT.child_panic 0 0.00 Child process panic
MAIN.summs 74450 70.57 stat summ operations
MAIN.uptime 1055 1.00 Child process uptime
MAIN.sess_conn 25393 24.07 Sessions accepted
MAIN.sess_fail 0 0.00 Session accept failures
MAIN.sess_fail_econnaborted 0 0.00 Session accept
failures: connection aborted
MAIN.sess_fail_eintr 0 0.00 Session accept
failures: interrupted system call
MAIN.sess_fail_emfile 0 0.00 Session accept
failures: too many open files
MAIN.sess_fail_ebadf 0 0.00 Session accept
failures: bad file descriptor
MAIN.sess_fail_enomem 0 0.00 Session accept
failures: not enough memory
MAIN.sess_fail_other 0 0.00 Session accept
failures: other
MAIN.client_req_400 0 0.00 Client requests
received, subject to 400 errors
MAIN.client_req_417 0 0.00 Client requests
received, subject to 417 errors
MAIN.client_req 35030 33.20 Good client
requests received
MAIN.cache_hit 33703 31.95 Cache hits
Cheers,
Andreas
