Benchmark memory

[jprendes]

This PR adds a memory usage benchmark to CI.

Fixes #802 , at least for the single container use case.

The PR is based on #775, I'll rebase once that is merged.
Marking as draft until then.

[jprendes]

Here's how the benchmark shows in CI
https://github.com/containerd/runwasi/actions/runs/12904819293/job/35982768369?pr=808#step:7:61

github-action-benchmark was run successfully! 
Data: {
  commit: {
    author: { name: 'jprendes', username: 'jprendes' },
    committer: { name: 'jprendes', username: 'jprendes' },
    id: '4a89cedbb35496fbab8cae5fdf2d239cf6e1aeaf',
    message: 'Benchmark memory',
    timestamp: '2025-01-07T09:23:28Z',
    url: 'https://github.com/containerd/runwasi/pull/808/commits/4a89cedbb35496fbab8cae5fdf2d239cf6e1aeaf'
  },
  date: 1737537142444,
  tool: 'customSmallerIsBetter',
  benches: [
    {
      name: 'wamr/memory-usage',
      value: 16044,
      unit: 'kB',
      range: undefined,
      extra: 'shim: 10624 kB\nzygote: 5420 kB'
    },
    {
      name: 'wasmedge/memory-usage',
      value: 67004,
      unit: 'kB',
      range: undefined,
      extra: 'shim: 51968 kB\nzygote: 15036 kB'
    },
    {
      name: 'wasmer/memory-usage',
      value: 19060,
      unit: 'kB',
      range: undefined,
      extra: 'shim: 13440 kB\nzygote: 5620 kB'
    },
    {
      name: 'wasmtime/memory-usage',
      value: 22712,
      unit: 'kB',
      range: undefined,
      extra: 'shim: 16256 kB\nzygote: 6456 kB'
    }
  ]
}

[andreiltd]

Nice! At what point in the process’s lifetime we take a snapshot of memory usage? IIUC, those values represent the peak usage during the process’s runtime, so ideally we should capture the snapshot just before terminating the process?

[jprendes]

Indeed, the snapshot is taken after shutting down the shim server, just before exiting the main function.

[jprendes]

And yes, they represent peak usage as reported by the kernel.