benchmark
Benchmark scenario definitions.
Primary key: benchmark_id. See the version history of this table on dbdocs.io.
Columns
| Column | Type | Constraints | References | Description |
|---|---|---|---|---|
benchmark_id | VARCHAR(255) | PK | Unique identifier of a specific Benchmark. | |
category | VARCHAR(255) | Category of the resource. | ||
source | JSON | NOT NULL | How the benchmark score is produced. A discriminated object keyed by ''kind'': ''measured'' (directly observed), ''extrapolated'' (derived from this server''s own measurements; carries ''derived_from'' + ''note''), or ''compound'' (aggregated across component benchmarks; carries ''aggregation'', ''normalization'', and the ''components'' recipe). | |
name | VARCHAR(255) | NOT NULL | Human-friendly name. | |
description | VARCHAR(255) | Short description. | ||
note | VARCHAR(255) | Optional caveat/comment on how to interpret the metric, surfaced as a warning/info badge (e.g. limited scaling on high vCPU counts, or independence from vCPU count). Null when there is nothing to flag. | ||
framework | VARCHAR(255) | NOT NULL | The name of the benchmark framework/software/tool used. | |
config_fields | JSON | NOT NULL | A dictionary of descriptions on the framework-specific config options, e.g. {"bandwidth": "Memory amount to use for compression in MB."}. | |
measurement | VARCHAR(255) | The name of measurement recorded in the benchmark. | ||
unit | VARCHAR(255) | Optional unit of measurement for the benchmark score. | ||
higher_is_better | BOOL | NOT NULL | If higher benchmark score means better performance, or vica versa. | |
status | ENUM | NOT NULL | Status of the resource (active or inactive). See Status for the possible values. | |
observed_at | DATETIME | NOT NULL | Timestamp of the last observation. |
Enums
Status
Last known status of a resource, e.g. active or inactive.
| Value | Description |
|---|---|
ACTIVE | Active and available resource. |
INACTIVE | Unavailable. For Server/Database: temporary or unknown cause. |
PLANNED_FOR_RETIREMENT | Planned for retirement; only valid for Server and Database. |
RETIRED | Not orderable anymore, but prices may still exist (e.g. active multi-year contracts). Only valid for Server and Database. |