Struct iai_callgrind::LibraryBenchmarkConfig
source · pub struct LibraryBenchmarkConfig(/* private fields */);
Expand description
The main configuration of a library benchmark.
See LibraryBenchmarkConfig::raw_callgrind_args
for more details.
Examples
use iai_callgrind::{LibraryBenchmarkConfig, main};
main!(
config = LibraryBenchmarkConfig::default()
.raw_callgrind_args(["toggle-collect=something"]);
library_benchmark_groups = some_group
);
Implementations§
source§impl LibraryBenchmarkConfig
impl LibraryBenchmarkConfig
sourcepub fn with_raw_callgrind_args<I, T>(args: T) -> Self
pub fn with_raw_callgrind_args<I, T>(args: T) -> Self
Create a new LibraryBenchmarkConfig
with raw callgrind arguments
See also LibraryBenchmarkConfig::raw_callgrind_args
.
Examples
use iai_callgrind::{LibraryBenchmarkConfig, main};
main!(
config =
LibraryBenchmarkConfig::with_raw_callgrind_args(["toggle-collect=something"]);
library_benchmark_groups = some_group
);
sourcepub fn raw_callgrind_args<I, T>(&mut self, args: T) -> &mut Self
pub fn raw_callgrind_args<I, T>(&mut self, args: T) -> &mut Self
Add callgrind arguments to this LibraryBenchmarkConfig
The arguments don’t need to start with a flag: --toggle-collect=some
or
toggle-collect=some
are both understood.
Not all callgrind arguments are understood by iai-callgrind
or cause problems in
iai-callgrind
if they would be applied. iai-callgrind
will issue a warning in
such cases. Some of the defaults can be overwritten. The default settings are:
--I1=32768,8,64
--D1=32768,8,64
--LL=8388608,16,64
--cache-sim=yes
(can’t be changed)--toggle-collect=*BENCHMARK_FILE::BENCHMARK_FUNCTION
(this first toggle can’t be changed)--collect-atstart=no
(overwriting this setting will have no effect)--compress-pos=no
--compress-strings=no
Note that toggle-collect
is an array and the entry point for library benchmarks
is the benchmark function. This default toggle switches event counting on when
entering this benchmark function and off when leaving it. So, additional toggles
for example matching a function within the benchmark function will switch the
event counting off when entering the matched function and on again when leaving
it!
See also Callgrind Command-line Options
Examples
use iai_callgrind::{LibraryBenchmarkConfig, main};
main!(
config = LibraryBenchmarkConfig::default()
.raw_callgrind_args(["toggle-collect=something"]);
library_benchmark_groups = some_group
);
sourcepub fn raw_callgrind_args_iter<I, T>(&mut self, args: T) -> &mut Self
pub fn raw_callgrind_args_iter<I, T>(&mut self, args: T) -> &mut Self
Add elements of an iterator over callgrind arguments to this LibraryBenchmarkConfig
See also LibraryBenchmarkConfig::raw_callgrind_args
Examples
use iai_callgrind::{LibraryBenchmarkConfig, main};
main!(
config = LibraryBenchmarkConfig::default()
.raw_callgrind_args_iter(["toggle-collect=something"].iter());
library_benchmark_groups = some_group
);
sourcepub fn env_clear(&mut self, value: bool) -> &mut Self
pub fn env_clear(&mut self, value: bool) -> &mut Self
Clear the environment variables before running a benchmark (Default: true)
Examples
use iai_callgrind::{LibraryBenchmarkConfig, main};
main!(
config = LibraryBenchmarkConfig::default().env_clear(false);
library_benchmark_groups = some_group
);
sourcepub fn env<K, V>(&mut self, key: K, value: V) -> &mut Self
pub fn env<K, V>(&mut self, key: K, value: V) -> &mut Self
Add an environment variables which will be available in library benchmarks
These environment variables are available independently of the setting of
LibraryBenchmarkConfig::env_clear
.
Examples
An example for a custom environment variable, available in all benchmarks:
use iai_callgrind::{LibraryBenchmarkConfig, main};
main!(
config = LibraryBenchmarkConfig::default().env("FOO", "BAR");
library_benchmark_groups = some_group
);
sourcepub fn envs<K, V, T>(&mut self, envs: T) -> &mut Self
pub fn envs<K, V, T>(&mut self, envs: T) -> &mut Self
Add multiple environment variables which will be available in library benchmarks
See also LibraryBenchmarkConfig::env
for more details.
Examples
use iai_callgrind::{LibraryBenchmarkConfig, main};
main!(
config =
LibraryBenchmarkConfig::default().envs([("MY_CUSTOM_VAR", "SOME_VALUE"), ("FOO", "BAR")]);
library_benchmark_groups = some_group
);
sourcepub fn pass_through_env<K>(&mut self, key: K) -> &mut Self
pub fn pass_through_env<K>(&mut self, key: K) -> &mut Self
Specify a pass-through environment variable
Usually, the environment variables before running a library benchmark are cleared but specifying pass-through variables makes this environment variable available to the benchmark as it actually appeared in the root environment.
Pass-through environment variables are ignored if they don’t exist in the root environment.
Examples
Here, we chose to pass-through the original value of the HOME
variable:
use iai_callgrind::{LibraryBenchmarkConfig, main};
main!(
config = LibraryBenchmarkConfig::default().pass_through_env("HOME");
library_benchmark_groups = some_group
);
sourcepub fn pass_through_envs<K, T>(&mut self, envs: T) -> &mut Self
pub fn pass_through_envs<K, T>(&mut self, envs: T) -> &mut Self
Specify multiple pass-through environment variables
See also LibraryBenchmarkConfig::pass_through_env
.
Examples
use iai_callgrind::{LibraryBenchmarkConfig, main};
main!(
config = LibraryBenchmarkConfig::default().pass_through_envs(["HOME", "USER"]);
library_benchmark_groups = some_group
);
sourcepub fn flamegraph<T>(&mut self, config: T) -> &mut Selfwhere
T: Into<InternalFlamegraphConfig>,
pub fn flamegraph<T>(&mut self, config: T) -> &mut Selfwhere
T: Into<InternalFlamegraphConfig>,
Option to produce flamegraphs from callgrind output using the crate::FlamegraphConfig
Examples
use iai_callgrind::{LibraryBenchmarkConfig, main, FlamegraphConfig};
main!(
config = LibraryBenchmarkConfig::default().flamegraph(FlamegraphConfig::default());
library_benchmark_groups = some_group
);
sourcepub fn regression<T>(&mut self, config: T) -> &mut Selfwhere
T: Into<InternalRegressionConfig>,
pub fn regression<T>(&mut self, config: T) -> &mut Selfwhere
T: Into<InternalRegressionConfig>,
Enable performance regression checks with a crate::RegressionConfig
Examples
use iai_callgrind::{LibraryBenchmarkConfig, main, RegressionConfig};
main!(
config = LibraryBenchmarkConfig::default().regression(RegressionConfig::default());
library_benchmark_groups = some_group
);
sourcepub fn tool<T>(&mut self, tool: T) -> &mut Selfwhere
T: Into<InternalTool>,
pub fn tool<T>(&mut self, tool: T) -> &mut Selfwhere
T: Into<InternalTool>,
Add a configuration to run a valgrind crate::Tool
in addition to callgrind
Examples
use iai_callgrind::{LibraryBenchmarkConfig, main, Tool, ValgrindTool};
main!(
config = LibraryBenchmarkConfig::default()
.tool(Tool::new(ValgrindTool::DHAT));
library_benchmark_groups = some_group
);
sourcepub fn tools<I, T>(&mut self, tools: T) -> &mut Self
pub fn tools<I, T>(&mut self, tools: T) -> &mut Self
Add multiple configurations to run valgrind crate::Tool
s in addition to callgrind
Examples
use iai_callgrind::{LibraryBenchmarkConfig, main, Tool, ValgrindTool};
main!(
config = LibraryBenchmarkConfig::default()
.tools(
[
Tool::new(ValgrindTool::DHAT),
Tool::new(ValgrindTool::Massif)
]
);
library_benchmark_groups = some_group
);
sourcepub fn tool_override<T>(&mut self, tool: T) -> &mut Selfwhere
T: Into<InternalTool>,
pub fn tool_override<T>(&mut self, tool: T) -> &mut Selfwhere
T: Into<InternalTool>,
Override previously defined configurations of valgrind crate::Tool
s
Usually, if specifying crate::Tool
configurations with LibraryBenchmarkConfig::tool
these tools are appended to the configuration of a LibraryBenchmarkConfig
of
higher-levels. Specifying a crate::Tool
with this method overrides previously defined
configurations.
Note that crate::Tool
s specified with LibraryBenchmarkConfig::tool
will be ignored,
if in the very same LibraryBenchmarkConfig
, crate::Tool
s are specified by this method
(or LibraryBenchmarkConfig::tools_override
).
Examples
The following will run DHAT
and Massif
(and the default callgrind) for all benchmarks in
main!
besides for some_func
which will just run Memcheck
(and callgrind).
use iai_callgrind::{
main, library_benchmark, library_benchmark_group, LibraryBenchmarkConfig, Tool, ValgrindTool
};
#[library_benchmark(config = LibraryBenchmarkConfig::default()
.tool_override(
Tool::new(ValgrindTool::Memcheck)
)
)]
fn some_func() {}
library_benchmark_group!(
name = some_group;
benchmarks = some_func
);
main!(
config = LibraryBenchmarkConfig::default()
.tools(
[
Tool::new(ValgrindTool::DHAT),
Tool::new(ValgrindTool::Massif)
]
);
library_benchmark_groups = some_group
);
sourcepub fn tools_override<I, T>(&mut self, tools: T) -> &mut Self
pub fn tools_override<I, T>(&mut self, tools: T) -> &mut Self
Override previously defined configurations of valgrind crate::Tool
s
See also LibraryBenchmarkConfig::tool_override
.
Examples
The following will run DHAT
(and the default callgrind) for all benchmarks in
main!
besides for some_func
which will run Massif
and Memcheck
(and callgrind).
use iai_callgrind::{
main, library_benchmark, library_benchmark_group, LibraryBenchmarkConfig, Tool, ValgrindTool
};
#[library_benchmark(config = LibraryBenchmarkConfig::default()
.tools_override([
Tool::new(ValgrindTool::Massif),
Tool::new(ValgrindTool::Memcheck)
])
)]
fn some_func() {}
library_benchmark_group!(
name = some_group;
benchmarks = some_func
);
main!(
config = LibraryBenchmarkConfig::default()
.tool(
Tool::new(ValgrindTool::DHAT),
);
library_benchmark_groups = some_group
);