Trying to figure out how memory captured by this package-benchmark works. See that repo for getting setup to run on macOS.
- Run the benchmarks:
swift package benchmark
- Run the benchmarks via docker:
docker build --tag memory-benchmark-test .
docker run memory-benchmark-test
Learnings from this post.
- Each memory benchmark should be in a separate target (if you're trying to understand memory growth). Non-memory benchmarks (CPU, malloc counts, context switches, etc.) can be in a single target.
- Look at
Memory (resident peak)
to understand how process memory size is changing. A growing process will see a clear progression from p0 -> p100.