Spare Cores Inspector Data

Data collected by sparecores-inspector under the data folder using the vendor/server directory structure, referring to the vendor by its vendor_id, and using the api_reference for the server.

Collected data

In general, consult the SpareCores Inspector repository for the technical details about the data collected, and the Spare Cores Navigator Benchmark Coverage page for a higher level overview.

Timing

Each inspected instance may have a timing/ directory (alongside task directories such as dmidecode/). Orchestration state for the timing task lives in timing/meta.json. Per GitHub Actions run, timestamps are stored under timing/<GITHUB_RUN_ID>/ so repeated starts of the same instance type keep separate histories.

Files are plain text with a single UTC timestamp per line, in ISO-8601 form (YYYY-MM-DDTHH:MM:SSZ). They are written to separate files (not meta.json) so the GitHub Actions start workflow and the remote inspect run can commit independently. The run id comes from the…