You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -128,6 +128,20 @@ A **Run** is a single end-to-end execution of the benchmark for one system. Each
128
128
129
129
The **E2E benchmark duration** (phase 2, load test stage) is the primary ranking metric. After the load test, each query's p99 latency is compared against the baseline: >20% increase = FAIL, 10–20% = WARN, ≥3 WARNs = FAIL.
130
130
131
+
### Run Metadata
132
+
133
+
SpiceBench supports two run-level metadata knobs to keep cross-system comparisons consistent:
|`table_format`|`parquet`| Declares the dataset table format used for creation/registration. | Passed through data-generation/ETL dataset params and consumed by adapters (for example, Databricks UC table creation). |
138
+
|`executor_instance_type`|`unknown` (CLI) / `github-hosted-ubuntu-latest` (workflow) | Identifies the benchmark executor hardware class for apples-to-apples comparisons. | Sent in adapter `setup` metadata and attached as an OpenTelemetry metric attribute for dashboard filtering. |
0 commit comments