Benchmark evidence and methodology
MyAIHardware maintains a curated reference catalog. Most entries do not include a public run artifact. They are not measurements made by an independent MyAIHardware lab, and a source link may identify a model or vendor rather than prove the reported speed.
What the current catalog supports
These counts are calculated from the same 565 records exported by the public API. Labels describe the evidence we can currently substantiate. Records without public supporting captures are classified as curated aggregates, including owner reports whose logs are still unpublished.
- Lab Verified: 0
- Community Verified: 0
- Vendor Claim: 0
- Curated Aggregate: 565
We removed retroactively assigned repeat counts, error bars, runtime versions and verification badges where they had no attached run evidence. A run count of zero means unknown, not a failed measurement. We have not recreated missing experiments or replaced unknown dates with today's date.
Owner-reported captures
These files preserve the owner's declared hardware and recorded outputs. They are useful examples, not independent certification or proof that other machines reproduce the results. The RX 7900 XTX capture also records a model that failed to generate tokens.
Comparisons and buying advice
A comparative speed group must share the model workload, quantization, context, batch and stated runtime version. Rankings use batch one; concurrent aggregate throughput is a separate quantity. Missing settings or a missing proxy workload are excluded from comparative speed scoring. Matching metadata alone does not establish a controlled experiment.
GPU memory comes from the hardware catalog where available. Multi-GPU and unified-memory systems need explicit configuration details. Capacity estimates reserve space for buffers, but cannot establish the KV-cache requirement for every model and context.
Catalog MSRP and earlier build allowances are undated references. They are not retailer quotes, stock checks or price history. No 30-day low is shown without actual observations in that window. Affiliate links can earn us a commission; verify price and terms at the retailer.
Reproducing a result
Reproduction requires the exact model artifact and hash, runtime commit, command, prompt and tokenizer, hardware configuration, context, batch, warmup policy and raw per-run outputs. Our older catalog does not consistently provide these. The protocol page specifies what a future submission needs; it does not claim the entire catalog followed that protocol.
Read the benchmark protocol and calculation definitions