INDEPENDENT HARDWARE INTELLIGENCE

Sources & data policy

Hardware Benchmark is designed around traceable data. The preferred source for a product specification is the manufacturer. Independent benchmark evidence is kept conceptually separate from specifications.

DataPreferred evidence
Model, launch, cores, clocks, memory, socket, powerManufacturer product/specification documentation
Gaming / creation performanceRepeatable independent benchmark evidence
Derived indicesDocumented calculation from cited evidence
Unknown / conflicting dataShown as pending rather than guessed

Source hierarchy

Hardware Benchmark uses a layered evidence model. Manufacturer documentation remains the primary authority for product specifications. Reputable independent references may be used for discovery and cross-checking where primary documentation is incomplete or difficult to locate, particularly for historical hardware. Independent benchmark evidence is assessed separately from specification data and is not automatically converted into Hardware Benchmark scores, rankings or winner claims.

Source tierRole
Manufacturer documentationPrimary specification authority and preferred verification source
Independent specification referencesSecondary discovery and cross-check evidence where primary documentation is incomplete or unavailable
Independent benchmark evidenceWorkload-specific performance evidence used only where methodology and products are sufficiently comparable
Conflicting or unsupported valuesFlagged for verification or left pending; never silently guessed

Where a secondary source contributes a value, provenance should identify the supporting evidence rather than presenting the field as manufacturer-verified.

Reference vs partner cards

Reference GPU specifications and board-partner card specifications are not interchangeable. Factory overclocks, connectors, dimensions and power limits can vary, so exact variants should become distinct records where those differences matter.

Corrections

The database is expanded by verification. Exact product identities may remain searchable while individual fields are incomplete, but unsupported values stay pending and are never presented as verified specifications.