benchmark nginx vs lsws - linode 1gb instance

gistfile1.txt

h2load - 1kstatic.html
lsws 5.4        finished in       0.76 seconds,  132261.00 req/s,      15.53 MB/s,          0 failures
nginx 1.16.0    finished in       4.40 seconds,   22710.60 req/s,       5.07 MB/s,          0 failures
wrk - 1kstatic.html
lsws 5.4        finished in       5.00 seconds,   60256.80 req/s,      22.76 MB/s,        N/A failures
nginx 1.16.0    finished in       5.00 seconds,   18618.40 req/s,       6.75 MB/s,        N/A failures
h2load - 1knogzip.jpg
lsws 5.4        finished in      62.05 seconds,    1595.50 req/s,       1.60 MB/s,       1000 failures
nginx 1.16.0    finished in       3.10 seconds,   32253.60 req/s,      35.44 MB/s,          0 failures
wrk - 1knogzip.jpg
lsws 5.4        finished in       5.00 seconds,   58411.80 req/s,      75.76 MB/s,        N/A failures
nginx 1.16.0    finished in       5.00 seconds,   27123.20 req/s,      32.69 MB/s,        N/A failures
h2load - wordpress
lsws 5.4        finished in       3.31 seconds,   30226.40 req/s,     117.48 MB/s,          0 failures
nginx 1.16.0    finished in      27.50 seconds,    3636.90 req/s,      14.72 MB/s,          0 failures
wrk - wordpress
lsws 5.4        finished in       5.00 seconds,   19523.90 req/s,      81.78 MB/s,        N/A failures
nginx 1.16.0    finished in       5.00 seconds,    3397.89 req/s,      14.24 MB/s,        N/A failures

Tested a few times on my Linode server and it sometimes shows failures on different items due to high traffic gets blocked automatically. So the next test case will show a failure.
If you try /opt/benchmark.sh -i 10 --no-check (which will sleep 10s before each test, and skip the CPU check to save some resources from the server side) then every test case works well. So far that's been my experience on my test server.

Just FYI, it's better to test on a higher bandwidth cloud environment like DigitalOcean (around 2GB bandwidth for my test).