[FR] Allow ThreadRange Multiplier to be different from Arg Ranges one · google/benchmark#1531

(0 comments) (1 reaction) (0 assignees)C++ (7,968 stars) (1,539 forks)batch import

enhancementhelp wanted

Description

Is your feature request related to a problem? Please describe. Once a RangeMultiplier is set, the threadrange also uses the exact same one, it would be easier if one could either set a ThreadRangeMultiplier or a multiplier argument to ThreadRange(min,max,multiplier)

Describe the solution you'd like A simple solution could be accepting a multiplier argument to the the ThreadRange arguments which can be used in case you'd need a customization on ThreadRange different from RangeMultiplier

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

Contributor guide

Tech stack: cpp
Domain: performance
Issue type: feature
Difficulty: 3
Estimated time: half day
Activity status: stale
Clarity: clear
Prerequisites: C++Google Benchmark library basics
Newbie friendliness: 65
Research direction: Start by examining the current implementation of ThreadRange and RangeMultiplier in the benchmark library. The relevant code is likely in include/benchmark/benchmark.h and src/benchmark.cc. Implement an additional parameter for multiplier in ThreadRange, following the pattern of the existing RangeMultiplier. Then update the documentation and tests accordingly.