google/benchmark

Better docs/name needed for "multi-threaded" benchmarking

Open

#813 opened on May 2, 2019

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C++ (7,968 stars) (1,539 forks)batch import
docshelp wanted

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

Tech stack
cpp
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
95
Research direction
The issue requests adding a few sentences to the README explaining that the multi threaded benchmark spawns self contained benchmark instances and memory usage scales linearly with threads. The relevant file is likely README.md in the repository root. The comment referenced in issue #806 provides additional context. No linked PRs or assignees exist, so the issue is open for a documentation contribution.