google/benchmark

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

Open

#813 建立於 2019年5月2日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)C++ (7,968 star) (1,539 fork)batch import
docshelp wanted

描述

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

貢獻者指南

技術棧
cpp
領域
documentation
議題類型
documentation
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
1
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
無
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
95
研究方向
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.
Better docs/name needed for "multi-threaded" benchmarking · google/benchmark#813 | Good First Issue