Enable ssl_poll_perf test to run as client/server.

[Sashan]

This enables as to evaluate performance of OpenSSL QUIC stack against other QUIC implementations.

[Sashan]

those changes were tested with tqclient/tqserver:

# git clone --recurse https://github.com/Tencent/tquic
# cd tquic
# cargo build --all # to build also tools/examples
# echo $?

if build is successful tqserver can be launched:

# cd target/debug/
# ./tquic_server -l 127.0.0.1:7070 -c path/to/servercert.pem -k path/to/serverkey.pem
# echo 'payload' > payload

Feel free to use servercert.pem and serverkey.pem found in $OPENSSL_SRCDIR/test/certs.
Command above starts QUIC server listening to port 7070. Use command here to connect:

# cd $PERFTOOLS./source/build
# ./ssl_poll_perf -m c -a 0 -c 100 -b 1 -u 0 http://127.0.0.1:7070/payload

command above launches client which performs 100 connections to tquic_server. Each connection
opens single bi-directional stream and fetches file payload.

to run tquic_client against ssl_poll_perf server, launch server first:

# cd $PERFTOOLS./source/build
# ./ssl_poll_perf -p 8080  -m s -a 0 path/to/servercert.pem path/to/serverkey.pem

To download 7 bytes from server above use URL http://127.0.0.1:8080/7 using
tquic_client command below:

./tquic_client \
    -t 1 \ # use one thread
    --max-concurrent-conns 100 \ # 100 concurrent connections
    --max-concurrent-requests 100 \ # 100 concurrent requests
    --max-requests-per-conn 1 \ # one request per connection
    --total-requests-per-thread 100 \ # 100 requests
    -d 0 # wait until all requests are completed
    -a http/0.9 # use http/0.9
    http://127.0.0.1:8080/7

[quarckster]

I'm wondering how to better run this in our performance benchmark lab. Is it enough to run both server and client on the same machine? Or the client and the server must be resided on separate hosts. In that case does it matter the platform of the counterpart? It will also bring questions of the simultaneous access to the counterpart from different testing machines. How will it affect on the results?

[jogme]

First iteration

[t8m]

I'm wondering how to better run this in our performance benchmark lab. Is it enough to run both server and client on the same machine? Or the client and the server must be resided on separate hosts. In that case does it matter the platform of the counterpart? It will also bring questions of the simultaneous access to the counterpart from different testing machines. How will it affect on the results?

IMO it SHOULD run on the same machine over loopback to avoid network latencies, etc.

[Sashan]

I'm wondering how to better run this in our performance benchmark lab. Is it enough to run both server and client on the same machine? Or the client and the server must be resided on separate hosts. In that case does it matter the platform of the counterpart? It will also bring questions of the simultaneous access to the counterpart from different testing machines. How will it affect on the results?

this is should be sufficient:

lifty$ ./ssl_poll_perf -t /path/to/certs/servercert.pem /path/to/certs/serverkey.pem  
268.1150

The output is the time it took to establish 10 connections. each connection opens 10 bidirectional streams and 10 unidirectional stream pairs. each stream performs http/1.0 request to obtaub 64bytes. This is a default pre-set. We can either change defaults here:

3405     const char *ccountstr = "10";
3406     const char *bstreamstr = "10";
3407     const char *ustreamstr = "10";
3408     const char *rep_sizestr = "64";
3409     const char *req_sizestr = "64";

Or you can pass commandline options which control those settings. command below performs the same workload as ./ssl_poll_perf -t /path/to/certs//... comands

./ssl_poll_test -c 10 -b 10 -u 10 -w 64 -s 64 -t /path/to/certs/servercert.pem /path/to/certs/serverkey.pem  

Or are you asking how to cross test OpenSSL quic stack with other QUIC clients/servers?

[jogme]

Looks good to me, thank you!

[Sashan]

merged via 513dec3