setting fasthttp MaxConnsPerHost to be equal to concurrency

[jonoden]

fasthttp has an internal default limit of 512 max connections per host. This causes network errors if you use a concurrency higher than 512. Made a change to set the fasthttp MaxConnsPerHost to be equal to the concurrency configured in the gobench execution.

Before:

$ gobench -c 750 -t 5 -u http:https://openresty/
Dispatching 750 clients
Waiting for results...
Requests:                          4842824 hits
Successful requests:                  5990 hits
Network failed:                    4836833 hits
Bad requests failed (!2xx):              0 hits
Successful requests rate:             1198 hits/sec
Read throughput:                   1435200 bytes/sec
Write throughput:                   105332 bytes/sec
Test time:                               5 sec

After:

$ ./gobench -c 750 -t 5 -u http:https://openresty/
Dispatching 750 clients
Waiting for results...
Requests:                            52296 hits
Successful requests:                 52296 hits
Network failed:                          0 hits
Bad requests failed (!2xx):              0 hits
Successful requests rate:            10459 hits/sec
Read throughput:                  11546956 bytes/sec
Write throughput:                   859345 bytes/sec
Test time:                               5 sec

[cmpxchg16]

Cool :)
Thanks for this update.

[jonoden]

Oops, you might want to revert the error printing, was using it to debug kernel parameter tuning and backend issues. I was going to add a -v parameter that would enabling printing a bunch of errors but I haven't quite finished it yet due to the larger task of benchmarking. :)