benchmark

Description

The benchmark database provides an persistent way to store benchmark runs information and view the results over time. Each benchmark_db object holds the connection to one opened database and proves commands to query the database contents, or make changes to the database.

Interfaces Implemented

conf_object, log_object, benchmark_database

Notifiers

cell-change: Notifier that is triggered after the object's cell was changed.
object-delete: Notifier that is triggered just before Simics object is deleted.
queue-change: Notifier that is triggered after the object's clock was changed. New clock can be obtained with the SIM_object_clock function.

Commands for this class

add-benchmark – add benchmark name to the database
add-benchmark-to-suite – add benchmark(s) to a suite in the database
add-host – add host name to the database
add-host-group – add host-group to the database
add-host-to-group – add host-group to the database
add-metric – add new probe as metric in the database
add-run-annotation – add a user annotation to a specific run
add-session-annotation – add a user annotation to a specific session
add-suite – add suite name to the database
delete – remove this database object/connection
export-json – export a benchmark run from the database as json
garbage-collect – try to optimize the database in size
import-json – import one or several benchmark runs into the database
info – print information about the object
list-benchmarks – list benchmark names in the database
list-host-groups – list defined host-groups and associated hosts in the database
list-hosts – list host names in the database
list-metrics – list the different metrics stored in the database
list-run-annotations – list all run-annotation added
list-runs – list benchmark runs in the database
list-session-annotations – list all session-annotations added
list-session-scores – list session's performance scores
list-sessions – list benchmark sessions in the database
list-suites – list benchmark suites in the database
remove-benchmark – remove benchmark name from the database (and runs)
remove-benchmark-from-suite – remove benchmark(s) from a suite in the database
remove-host – remove host name from the database (and runs)
remove-host-from-group – remove a host from host-group in the database
remove-host-group – remove a host-group from the database
remove-metric – remove a probe as metric in the database
remove-run – remove a run from the database
remove-run-annotation – remove a user annotation from a specific run
remove-session – remove session(s) from the database
remove-session-annotation – remove a user annotation from a specific session
remove-suite – remove suite name from the database
set-journal-mode – set journal-mode on sqlite3 DB
set-suite-baseline – set baseline for a suite
status – print status of the object

Attributes

create: Required attribute; read/write access; type: b
signals if a new database should be created
read_only: Optional attribute; read/write access; type: b
indicates if the database is read-only
verbose: Optional attribute; read/write access; type: b
set log_level=4 early
database: Required attribute; read/write access; type: s
sqlite3-file to be used as database
create_flags: Optional attribute; read/write access; type: i
Flags indicating the default metrics in the database.

Provided By

benchmark-database