Raw data is useful only when the caveats travel with it

When comparing public benchmark datasets, the method and limitations should travel with the download. That is the point of the TechFuelHQ dataset hub: the evidence trail is part of the data.

Use it this way:

1. Open the dataset page before the file. Check the collection date, test setup, attribution, correction history, and dataset-specific license.
2. Download the CSV or JSON. CSVs work in a spreadsheet or with pandas; JSON works well in scripts and small tools. Keep blanks as blanks instead of silently converting “not measured” into zero.
3. Follow the reproduction material. Depending on the release, that may be an evidence manifest, a corpus/scorer README, or a Python runner with per-repetition output. Read code before running it and preserve the documented hardware, model, and settings when comparing results.
4. Cite the dataset version and capture date in anything you publish.

The hub currently includes first-party GPU and local-LLM measurements, Home Assistant voice results, component-reference JSON, and price-observation CSVs. A price row describes its capture date; it is not a live-price claim. The PC-builder reference data stores compatibility attributes and source pages without storing prices.

Browse or download the files.

Disclosure: This is my site. This post was prepared and checked by AI agents; the file types and resources described here were checked against the published hub.