Scores by kind of claim
Each kind of claim is scored on its own, out of 100: the share that held up, with the range it likely falls in. Fewer resolved claims give a wider range.
-
Factual claims
Statements about the present or the past, checked against the record: did they hold up?
72 67 78 -
Predictions
Statements about events outside the person's control, checked once they fell due: did they come true?
Insufficient record: 1 prediction resolved, 5 needed for a score.
-
Promises
Commitments to the person's or organisation's own future action, with something to deliver: was it delivered?
Insufficient record: 4 promises resolved, 5 needed for a score.
-
Guidance
A company's own figures for its results over a period, checked against what it then reported.
Insufficient record: 1 guidance claim resolved, 5 needed for a score.
All types combined: 72 (likely 67 to 78, high confidence), from 101 claims: 101 factual claims. It mixes kinds of claim in different proportions for different people, so compare people kind by kind.
Jensen Huang's claims
32 claims
“KEPLER 32 Concurrent Work Queues”
NVIDIA keynote slide (Jensen Huang, CEO) May 2012 GTC 2012 Jen-Hsun Huang Keynote (SlideShare)
With Hyper-Q, Kepler supports 32 concurrent work queues versus one on Fermi.
Resolved true The record shows it happened or was so.
The evidence is the person's or their organisation's own records.
Said for an organisation they lead or work for; it counts on both records.
What would count as true or false
True: NVIDIA's Kepler (GK110) documentation, such as the Kepler GK110 whitepaper or GTC 2012 materials, states that Hyper-Q provides 32 simultaneous hardware work queues, compared with a single work queue on Fermi. Mostly true: 32 queues is confirmed, but the Fermi comparison is slightly imprecise, or Hyper-Q applies only to GK110 or compute capability 3.5 rather than all Kepler parts. Mostly false: the queue count or the Fermi baseline is materially wrong while Hyper-Q did increase concurrency. False: Kepler's Hyper-Q did not provide 32 concurrent work queues.
Evidence
- Whitepaper (NVIDIA's Next Generation CUDA Compute Architecture: Kepler GK110/210, V1.1) NVIDIA Own record
“Hyper-Q increases the total number of connections (work queues) between the host and the CUDA Work Distributor (CWD) logic in the GPU by allowing 32 simultaneous, hardware-managed connections (compared to the single connection available with Fermi).”
- www.nvidia.com · content · damDatasheet: NVIDIA Kepler Next-Generation Cuda Compute ... NVIDIA · May 2012 Own record
“by allowing 32 simultaneous, hardware managed connections, compared to the single connection available with Fermi.”
- Microsoft PowerPoint - Inside Kepler.pptx [Read-Only] NVIDIA (GTC 2012 session S0642, 'Inside Kepler' by Lars Nyland and Stephen Jones) Own record
“Kepler allows 32-way concurrency”
- Microsoft PowerPoint - Inside Kepler.pptx [Read-Only] NVIDIA (GTC 2012 session S0642, 'Inside Kepler' by Lars Nyland and Stephen Jones) Own record
“But CUDA streams multiplex into a single queue”
Reasoning
NVIDIA's Kepler GK110/210 architecture whitepaper (E1) says Hyper-Q allows "32 simultaneous, hardware-managed connections (compared to the single connection available with Fermi)." NVIDIA's May 2012 Kepler compute architecture datasheet (E2) uses the same wording. The GTC 2012 'Inside Kepler' slides say Kepler allows 32-way concurrency [E3] and that CUDA streams multiplex into a single queue [E4]. That matches the True criterion, which asks for NVIDIA's own Kepler GK110 documentation, though all of these sources are NVIDIA's own.
Cite this claim
Jensen Huang, “With Hyper-Q, Kepler supports 32 concurrent work queues versus one on Fermi.” (said May 2012). Verdict: resolved true. Reliability API, claim c_d1757cbb8222, method 0.1.0+03d23c0e. https://epistacklabs.com/claims/c_d1757cbb8222
Claims without a verdict
Is a verdict here wrong, or do you speak for Jensen Huang? Reply on the claim's own page, with the form at its foot (how replies work). Verdicts are made automatically; how verdicts and scores are made.