PCBenchmark/Results/Intel Xeon W-2133 + NVIDIA Quadro P2000 browser benchmark
PC SCORE30OUT OF 100
SYSTEM GRADEE
Excellent quality run 12 September 2026 · 12:13 EEST

Intel Xeon W-2133+NVIDIA Quadro P2000

A completed baseline run. Review quality and raw metrics before comparing it.

SUITEFULL SYSTEM MODESTRESS GPU APIWebGPU ENGINE1.2.1 SCORE SCALEPROVISIONAL R4 DURATION03:38
Run same suite
01 / WORKLOAD BREAKDOWN

Performance by workload.

CPU and GPU use the current adaptive scale for the same workload, mode and graphics backend. When a faster validated device becomes the reference, older comparable scores are projected onto the new scale without changing their raw measurements. VRAM remains a pass/fail diagnostic.

CPU37

Processor throughput

Single thread
387.93 Mops/s
Multi thread
2,767.24 Mops/s
Compression proxy
532.5 MB/s
GPU14

Graphics throughput

Estimated shader work
1,635.8 G shader ops/s
Render throughput
155.0 FPS
Frame time p95
6.20 ms
MEMORY52

System memory

Effective bandwidth
17.10 GB/s
Latency proxy
62.3 ns
Browser RAM class
32 GB class
VRAMPASS

GPU-memory diagnostic

Transfer bandwidth
2.35 GB/s
Tested allocation
512 MB
Validation errors
0 errors
02 / RELATIVE PERFORMANCE

What sits above and below this hardware.

Each ladder uses one consistent source. Validated PCBenchmark medians take priority when the matching workload cohort has enough approved runs; until then, the report shows a clearly marked catalog estimate.

CPU POSITION

Intel Xeon W-2133 comparison ladder

ESTIMATE

Specification-based estimateApproximate browser CPU capacity derived from official core, thread and clock specifications for Skylake desktop processors. It is not a measured benchmark.

  1. Intel Xeon Gold 5120Skylake · 14 cores / 28 threads · 2017
    +2.4%higher estimate
  2. Intel Xeon W-2133Skylake · 6 cores / 12 threads · 2017
    BASECATALOG REFERENCE
  3. Intel Xeon Gold 5118Skylake · 12 cores / 24 threads · 2017
    −2.0%lower estimate
GPU POSITION

NVIDIA Quadro P2000 comparison ladder

ESTIMATE

Theoretical FP32 estimatePercentages compare theoretical FP32 compute within the desktop GPU catalog; they are not measured PCBenchmark or gaming performance.

  1. NVIDIA GeForce GTX 1650 SUPERGeForce 16 · 4 GB VRAM · 2019
    +45.9%higher estimate
  2. NVIDIA GeForce GTX 1060 6 GBGeForce 10 · 6 GB VRAM · 2016
    +44.6%higher estimate
  3. NVIDIA P106-100Mining GPUs · 6 GB VRAM · 2017
    +44.6%higher estimate
  4. NVIDIA Quadro P2000Quadro Pascal(Px000) · 5 GB VRAM · 2017
    BASECATALOG REFERENCE
  5. NVIDIA GeForce GTX 1650GeForce 16 · 4 GB VRAM · 2019
    −1.7%lower estimate
  6. NVIDIA P106MMining GPUs · 4 GB VRAM · 2019
    −2.0%lower estimate
  7. NVIDIA P106-090Mining GPUs · 3 GB VRAM · 2017
    −22.4%lower estimate
03 / STABILITY98.3%

Sustained-load signal

This signal summarizes frame delivery during the timed graphics phase. It can reveal an inconsistent run, but it is not a temperature sensor.

COMPLETEDYES SAMPLE WINDOW218 SEC DROPPED FRAMES1.71%
04 / ENVIRONMENTRUN CONTEXT

What the browser disclosed

Selected suite
Full system
Platform family
Windows
Logical processors
12
Browser RAM class
32 GB · rounded/capped
Graphics API
WebGPU
Run quality
Excellent · 99/100
Score fingerprint
adaptive-v2.0 / 1.2.1
Current adaptive scale
Provisional revision 4 / 28 August 2026
i
BROWSER BENCHMARK, NOT HARDWARE ATTESTATION

Read this result in its proper context.

It measures this browser’s execution path under the conditions of this run. Cooling, power mode, drivers, background processes and browser updates can change the outcome. CPU/GPU names may be supplied manually or matched to the catalog from a browser hint. Compare only matching suite, mode, engine version and graphics backend. NOT RUN categories were not measured and are not zero-performance results.

Read methodology & limitations
05 / RAW RESULT DATAInspect JSON +
{
    "test_suite": "all",
    "test_mode": "stress",
    "duration_ms": 218457,
    "system": {
        "cpu_name": "Intel Xeon W-2133",
        "gpu_name": "NVIDIA Quadro P2000",
        "logical_cores": 12,
        "memory_gb": 32,
        "platform": "windows",
        "gpu_api": "webgpu",
        "processor_id": 3246,
        "graphics_card_id": 2199
    },
    "metrics": {
        "stability": {
            "duration_seconds": 218,
            "completed": true,
            "dropped_frames_percent": 1.706
        },
        "cpu": {
            "single_core_ops_per_second": 387925437.805,
            "multi_core_ops_per_second": 2767236990.829,
            "compression_mb_per_second": 532.502
        },
        "memory": {
            "bandwidth_gbps": 17.096,
            "latency_ns": 62.308
        },
        "gpu": {
            "frames_per_second": 154.957,
            "compute_gflops": 1635.819,
            "frame_time_p95_ms": 6.2
        },
        "vram": {
            "tested_mb": 512,
            "bandwidth_gbps": 2.345,
            "errors": 0
        }
    },
    "raw_points": {
        "cpu": 16.60561024,
        "gpu": 1.3631825
    },
    "original_scores": {
        "cpu": 37,
        "gpu": 14,
        "memory": 52,
        "vram": 0,
        "overall": 30,
        "grade": "E"
    },
    "current_scores": {
        "cpu": 37,
        "gpu": 14,
        "memory": 52,
        "vram": 0,
        "overall": 30,
        "grade": "E",
        "snapshot_revision": 4
    },
    "runner_version": "1.2.1",
    "workload_signature": "browser-1.2",
    "scoring_version": "adaptive-v2.0"
}
SAME SUITE, FRESH CONDITIONS

Think this system can do better?

Close heavy apps, connect power, keep the tab visible and run the same Full system suite and Stress mode again.

Run it again