[CI-Examples] Nginx

[dimakuv]

Description of the problem

Our benchmark-http.sh script uses wrk under the hood. Wrk seems to ignore error code 403, and happily continues execution and reports some (meaningless) statistics:

$ gramine-sgx ./nginx
...

# wget correctly complains
$ wget --no-proxy http://127.0.0.1:8002/random/10K.1.html
--2024-10-15 07:45:28--  http://127.0.0.1:8002/random/10K.1.html
Connecting to 127.0.0.1:8002... connected.
HTTP request sent, awaiting response... 403 Forbidden
2024-10-15 07:45:28 ERROR 403: Forbidden.

# wrk doesn't complain
$ wrk -c 300 -d 30 -t 1 -R 10000 http://127.0.0.1:8002/random/10K.1.html
Running 30s test @ http://127.0.0.1:8002/random/10K.1.html
  1 threads and 300 connections
  Thread calibration: mean lat.: 1.956ms, rate sampling interval: 10ms
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     2.99ms   12.39ms 204.93ms   98.75%
    Req/Sec    10.71k     8.31k   57.33k    75.40%
  289281 requests in 30.00s, 84.97MB read
  Non-2xx or 3xx responses: 289281
Requests/sec:   9642.13
Transfer/sec:      2.83MB

This was detected during #2018.

Our CI should either:

• run wget <file under test> before wrk,
• or modify benchmark-http.sh script somehow.

Currently our CI just runs benchmark-http.sh script that invokes wrk, and such errors are not noticed:

gramine/.ci/lib/stage-test-sgx.jenkinsfile

Line 89 in 91c90b4

LOOP=1 CONCURRENCY_LIST="1 32" ../common_tools/benchmark-http.sh http://127.0.0.1:8002

Gramine commit hash

91c90b4