Expand description
Running benchmarking jobs
The core evobench functionality (i.e. excl. more general
library files, and excl. the main driver program at
src/bin/evobench.rs)
Modules§
- bench_
tmp_ dir - benchmarking_
job - command_
log_ file - Log files holding benchmarking command output–not the structured timing data, but stdout and stderr of the benchmarking target of the target application, plus a header with the serialized parameters.
- config
- custom_
parameter - dataset_
dir_ env_ var - env_
vars - global_
app_ state_ dir - insert_
jobs - key
- The key for a benchmarking run–all parameters modifying the output
- migrate
- Database migration. Structs with incompatible changes should be copied here and an upgrade function provided.
- open_
run_ queues - Does not belong in run_queues.rs? But must be accessible for utils other than evobench.rs, too, thus this module.
- output_
directory - polling_
pool - Handle polling the upstream project repository for changes, and also check commit ids for insertions for validity
- run_
context - run_job
- Running a benchmarking job
- run_
queue - run_
queues - stop_
start_ status - sub_
command - versioned_
dataset_ dir - working_
directory - An abstraction for an existing directory, and one that should be usable (i.e. is worth trying to use).
- working_
directory_ pool - A pool of
WorkingDirectory. Error concept: if there are errors, the WorkingDirectory is renamed but stays in the pool directory. (Only directories with names that are parseable as u64 are treated as usable entries.)