Disable shim logging to stdout

[radu-matei]

The way containerd handles shim logging, there is a ~17x performance penalty right now to throughput for a Spin application running through the shim because of logging to stdout:

Simple test on my current machine with the current version of the Spin shim:

Statistics        Avg      Stdev        Max
  Reqs/sec      7987.75    1452.81   24490.93
  Latency       63.75ms    34.08ms   290.82ms
  HTTP codes:
    1xx - 0, 2xx - 80503, 3xx - 0, 4xx - 0, 5xx - 0
    others - 0
  Throughput:     1.22MB/s

Compared against a branch that hard disables all logging per request:

Statistics        Avg      Stdev        Max
  Reqs/sec    149855.88    6520.46  163453.38
  Latency        3.41ms   735.86us    56.52ms
  HTTP codes:
    1xx - 0, 2xx - 1498034, 3xx - 0, 4xx - 0, 5xx - 0
    others - 0
  Throughput:    22.85MB/s

Note: setting the containerd --log-level flag seems to have no effect, so I had to manually go through the dependencies of the shim and comment out info logging...

cc @Mossaka @jsturtevant

[jsturtevant]

Note: setting the containerd --log-level flag seems to have no effect, so I had to manually go through the dependencies of the shim and comment out info logging...

this is coming from https://github.com/containerd/rust-extensions/blob/cc445f54c0fa8e9b35376550874422c932ad1566/crates/shim/src/logger.rs#L135-L139

Temporarily you should be able to disable logging via:

https://github.com/containerd/rust-extensions/blob/cc445f54c0fa8e9b35376550874422c932ad1566/crates/shim/src/synchronous/mod.rs#L257

example:

    shim_main::<WasmtimeInstance>("wasmtime", version!(), revision!(), "v1", Some(Config{no_setup_logger: true, ..Default::default()}));

[jsturtevant]

I've got a change that could help here: containerd/rust-extensions#247