Process Request Failure:1
That number at the end seems to be the number of failed requests. Tellingly, it happened after exactly 1000 successful requests each time. Restart h2load, get another 1000 successful requests. I tried keepalive_requests in my nginx config, but no luck. Finally, after going through the nginx source for instances of "1000", I found http2_max_requests, which defaults to 1000. Increase that to an enormous number, restart nginx, everything works fine.
+That number at the end seems to be the number of failed requests. Tellingly, it happened after exactly 1000 successful requests each time. Restart h2load, get another 1000 successful requests. I tried keepalive_requests in my nginx config, but no luck. Finally, after going through the nginx source for instances of "1000", I found http2_max_requests, which defaults to 1000. Increase that to an enormous number, restart nginx, everything works fine.
Someone should really implement reconnect in h2load, or at least some decent error messages.
diff --git a/include/style.css b/include/style.css index a3afe22..aae98f7 100644 --- a/include/style.css +++ b/include/style.css @@ -92,22 +92,23 @@ ul li, ol li { } code { + font-family: monospace, Courier; + font-size: 16px; + color: #22bb00; +} + +pre code { display: block; white-space: pre; - font-family: monospace, Courier; - font-size: 16px; - - line-height: 1.3; - - color: #22bb00; - border: 1px solid grey; + overflow: scroll; + padding: 1ch; margin: 1ch; - overflow: scroll; + line-height: 1.3; } @media (max-width: 500px) { diff --git a/markdown/2019-04-28-h2load-process-request-failure.md b/markdown/2019-04-28-h2load-process-request-failure.md index 6238189..62cddb8 100644 --- a/markdown/2019-04-28-h2load-process-request-failure.md +++ b/markdown/2019-04-28-h2load-process-request-failure.md @@ -6,7 +6,7 @@ I went looking for an HTTP/2 replacement for [Ab](https://httpd.apache.org/docs/2.4/programs/ab.html) and found [h2load](https://nghttp2.org/documentation/h2load-howto.html). Perfect, awesome, just what I need. My first few test runs work fine, then as I'm ramping up test size... Process Request Failure:1 -That number at the end seems to be the number of failed requests. Tellingly, it happened after exactly 1000 successful requests each time. Restart h2load, get another 1000 successful requests. I tried **keepalive\_requests** in my nginx config, but no luck. Finally, after going through the nginx source for instances of "1000", I found [http2\_max\_requests](https://nginx.org/en/docs/http/ngx_http_v2_module.html#http2_max_requests), which defaults to 1000. Increase that to an enormous number, restart nginx, everything works fine. +That number at the end seems to be the number of failed requests. Tellingly, it happened after exactly 1000 successful requests each time. Restart h2load, get another 1000 successful requests. I tried `keepalive_requests` in my nginx config, but no luck. Finally, after going through the nginx source for instances of "1000", I found [`http2_max_requests`](https://nginx.org/en/docs/http/ngx_http_v2_module.html#http2_max_requests), which defaults to 1000. Increase that to an enormous number, restart nginx, everything works fine. Someone should really implement reconnect in h2load, or at least some decent error messages.