Better docs/name needed for "multi-threaded" benchmarking
Open
docs
help wanted
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.8k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
> Would it have been better if any of this would be in docs / is there anything brought up in this issue appears to be omitted in docs?
I think so, yes. Perhaps a sentence or two on the README regarding how the "multi-threaded" implementation spawns self-contained benchmark instances, and users should expect memory footprint for the benchmark program to grow linearly in the number of threads.
_Originally posted by @jmftrindade in https://github.com/google/benchmark/issues/806#issuecomment-488472617_
Contributor guide
Assessment
This issue has not been assessed yet.