misc/firestuff
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

h2load Process Request Failure

Browse Source
This commit is contained in:
Ian Gulliver
2019-04-28 23:31:23 +00:00
parent e32ffa277d
commit 383f973b54
4 changed files with 30 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
markdown/2019-04-28-h2load-process-request-failure.md Normal file
View File

@@ -0,0 +1,13 @@
<!--# set var="title" value="h2load Process Request Failure" -->
<!--# set var="date" value="2019-04-28" -->
<!--# include file="include/top.html" -->
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.
Someone should really implement reconnect in h2load, or at least some decent error messages.
<!--# include file="include/bottom.html" -->

1
markdown/index.md
View File

@@ -2,6 +2,7 @@
<!--# include file="include/top.html" -->
1. 2019-04-28: [h2load Process Request Failure](2019-04-28-h2load-process-request-failure.html)
1. 2019-04-21: [Old code roundup](2019-04-21-old-code-roundup.html)
1. 2019-04-14: [Reboot](2019-04-14-reboot.html)
1. 2016-05-17: [WiFi bridging redux](2016-05-17-wifi-bridging-redux.html)