Data transparency

Bottleneck Calculator Data Methodology

This calculator is built around source-backed hardware specifications and clearly labeled internal estimates. It is designed to explain likely balance, not to claim exact FPS.

Technical visualization of CPU, GPU, memory, and display workload flow used to estimate PC bottlenecks.

Official specs

CPU cores, threads, clocks, cache, power, GPU memory, bandwidth, and board power come from official vendor product pages whenever possible.

Normalized indexes

Gaming, productivity, raster, ray tracing, and compute indexes are internal model inputs. They are not raw benchmark scores and not copied from competitor calculators.

Resolution-aware scoring

The model treats 1080p, 1440p, ultrawide, and 4K differently. A GPU limit at 4K is often expected and should not always be shown as a bad bottleneck.

Source status

Production sources

Reference only

  • OpenBenchmarking.org Useful for public workload comparisons and validation. Do not collapse mixed workloads into a single gaming score without labeling the model.
  • Steam Hardware and Software Survey Use for market popularity and hardware coverage priorities, not for direct performance scoring.
  • DBGPU MIT-licensed GPU spec library sourced from TechPowerUp. Good for cross-checking specs; review upstream data terms before bulk redistribution.

Needs license

What the result means

A CPU result means the selected processor is more likely to limit frame pacing or simulation throughput for the chosen workload. This is most common at 1080p or high-refresh esports targets.

A GPU result means graphics workload is more likely to dominate. At 4K this can be normal, so the model subtracts an expected GPU-bound allowance before showing a serious warning.

RAM and VRAM warnings are handled separately. If memory is below the profile recommendation, the result prioritizes that shortfall before suggesting a CPU or GPU upgrade.

The calculator should be used as planning guidance. For purchase decisions, compare multiple game benchmarks and confirm current local pricing.

What is measured directly

Vendor-published specifications are stored as structured fields so every visible result can point back to official CPU and GPU product data.

What is estimated

Normalized performance indexes are internal estimates used for ranking relative balance. They are not copied benchmark tables and should not be read as exact FPS.

How updates are handled

Hardware rows include source status and checked dates, making future spec corrections auditable instead of hidden inside a black-box formula.