Allow running perf client and server within dockers

[stormshield-damiend]

Add a way to run perf_client and perf_server within two dockers with optional simulated latency.

To build the binaries and the docker, use :
build.sh

To launch the server, use :
./run-server.sh -l 10 -L 0.1 -c -o

This will :

• simulate a latency of 10ms using Linux kernel QOS
• simulate a packet loss of 0.1% using Linux kernel QOS
• capture all packets using tcpdump inside the docker
• open the capture with wireshark using the dumped keys

To launch the client, use :
./run-client.sh -l 10 -L 0.1

This will launch perf_client for 5sec with a simulated latency of 10ms (we will the have a RTT of 10ms) and a packet loss of 0.1%.

/!\ For now the GSO is disabled otherwise wireshark is not capable of deciphering packets.

[Ralith]

Maybe add set -eu to the shell scripts for robustness?

[Ralith]

This gets further now, but still fails before doing any testing:

> ./build.sh
[...]
[+] Building 33.1s (12/12) FINISHED                                             docker:default
 => [server internal] load build definition from Dockerfile                               0.0s
 => => transferring dockerfile: 353B                                                      0.0s
 => [server internal] load .dockerignore                                                  0.0s
 => => transferring context: 2B                                                           0.0s
 => [server internal] load metadata for docker.io/library/debian:bookworm-slim            0.0s
 => [server 1/7] FROM docker.io/library/debian:bookworm-slim                              0.0s
 => [server internal] load build context                                                  1.3s
 => => transferring context: 207.54MB                                                     1.3s
 => [server 2/7] RUN apt-get update && apt-get install -y procps iputils-ping iproute2   24.9s
 => [server 3/7] WORKDIR /root                                                            0.0s
 => [server 4/7] RUN mkdir -p .local/share/quinn                                          0.4s
 => [server 5/7] COPY ./entrypoint.sh .                                                   0.0s 
 => [server 6/7] COPY ./target/perf_client .                                              3.6s 
 => [server 7/7] COPY ./target/perf_server .                                              3.7s 
 => [server] exporting to image                                                           0.5s 
 => => exporting layers                                                                   0.5s
 => => writing image sha256:9daaad82df8dffc2849b4d3fb52d3121012ea804ff536c829ca67d6d518d  0.0s
 => => naming to docker.io/library/quinn_perf                                             0.0s
> ./run-server.sh -l 10 -c -o
Launching docker server
[+] Building 0.0s (0/0)                                                         docker:default
[+] Running 2/2
 ✔ Network docker_quinn-perf  Created                                                     0.1s 
 ✔ Container docker-server-1  Started                                                     0.0s 
Enforcing a latency of 10ms
Starting capture within docker
Launching quinn perf server
Error response from daemon: OCI runtime exec failed: exec failed: unable to start container process: exec /root/perf_server: no such file or directory: unknown

[stormshield-damiend]

This gets further now, but still fails before doing any testing:

> ./build.sh
[...]
[+] Building 33.1s (12/12) FINISHED                                             docker:default
 => [server internal] load build definition from Dockerfile                               0.0s
 => => transferring dockerfile: 353B                                                      0.0s
 => [server internal] load .dockerignore                                                  0.0s
 => => transferring context: 2B                                                           0.0s
 => [server internal] load metadata for docker.io/library/debian:bookworm-slim            0.0s
 => [server 1/7] FROM docker.io/library/debian:bookworm-slim                              0.0s
 => [server internal] load build context                                                  1.3s
 => => transferring context: 207.54MB                                                     1.3s
 => [server 2/7] RUN apt-get update && apt-get install -y procps iputils-ping iproute2   24.9s
 => [server 3/7] WORKDIR /root                                                            0.0s
 => [server 4/7] RUN mkdir -p .local/share/quinn                                          0.4s
 => [server 5/7] COPY ./entrypoint.sh .                                                   0.0s 
 => [server 6/7] COPY ./target/perf_client .                                              3.6s 
 => [server 7/7] COPY ./target/perf_server .                                              3.7s 
 => [server] exporting to image                                                           0.5s 
 => => exporting layers                                                                   0.5s
 => => writing image sha256:9daaad82df8dffc2849b4d3fb52d3121012ea804ff536c829ca67d6d518d  0.0s
 => => naming to docker.io/library/quinn_perf                                             0.0s
> ./run-server.sh -l 10 -c -o
Launching docker server
[+] Building 0.0s (0/0)                                                         docker:default
[+] Running 2/2
 ✔ Network docker_quinn-perf  Created                                                     0.1s 
 ✔ Container docker-server-1  Started                                                     0.0s 
Enforcing a latency of 10ms
Starting capture within docker
Launching quinn perf server
Error response from daemon: OCI runtime exec failed: exec failed: unable to start container process: exec /root/perf_server: no such file or directory: unknown

i will rebase the work as it is quite old and see if i also have the issue.

[stormshield-damiend]

I added support for extra args for quinn-perf, i also added a README.md file.

[djc]

I appreciate the efforts, but not sure it makes sense to maintain this in this repository...

[stormshield-damiend]

i can move it to a dedicated repository, just tell me

[djc]

@Ralith thoughts?

[gretchenfrage]

I guess the benefit of it being part of this repo is if we wanna do some sort of regression test to make sure internal tweaks don't make it noticeably slower? But by default it seems like the kind of thing that doesn't need to be merged into this repo. But a regression test as such could be valuable...

[Ralith]

While I very much appreciate this work, I lean towards keeping this externally-maintained for now, just because I think we're not likely to use it much personally and it will probably bitrot as a result. Regression tests are attractive, but they need to be built and automated and operated in a controlled environment, none of which can be taken for granted.

[stormshield-damiend]

Hi, i will move it to its own repository.