Struct fuchsia_storage_benchmarks::Args
source · pub(crate) struct Args {
pub(crate) output_fuchsiaperf: Option<PathBuf>,
pub(crate) output_csv: bool,
pub(crate) filter: Vec<Regex>,
pub(crate) enable_tracing: bool,
pub(crate) load_blobs_for_tracing: bool,
}
Expand description
Fuchsia Filesystem Benchmarks
Fields§
§output_fuchsiaperf: Option<PathBuf>
path to write the fuchsiaperf formatted benchmark results to.
output_csv: bool
outputs a summary of the benchmark results in csv format.
filter: Vec<Regex>
regex to specify a subset of benchmarks to run. Multiple regex can be provided and
benchmarks matching any of them will be run. The benchmark names are formatted as
“
enable_tracing: bool
registers a trace provider and adds a trace duration with the benchmarks name around each benchmark.
load_blobs_for_tracing: bool
starts each filesystem to force the filesystem components and the benchmark component to be loaded into blobfs. Does not run any benchmarks.
When trying to collect a trace immediately after modifying a filesystem or a benchmark, the start of the trace will be polluted with downloading the new blobs, writing the blobs to blobfs, and then paging the blobs back in. Running the benchmark component with this flag once before running it again with tracing enabled will remove most of the component loading from the start of the trace.