PCBenchmark/Results/Intel Xeon E5-2683 v4 CPU browser benchmark
CPU CATEGORY SCORE26PARTIAL · OUT OF 100
RUN QUALITY62
Fair quality run 12 October 2026 · 09:43 EEST

Intel Xeon E5-2683 v4

CPU category score 26/100 from the processor-only suite. This partial result is not a full-system PC Score.

SUITECPU + MEMORY MODEQUICK GPU APINOT RUN ENGINE1.3.0 SCORE SCALEVALIDATED R5 DURATION00:10
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.

CPU26

Processor throughput

Single thread
308.68 Mops/s
Multi thread
3,449.30 Mops/s
Compression proxy
467.9 MB/s
GPUNOT RUN

Graphics throughput

This workload was not included in the CPU + Memory suite.

MEMORY49

System memory

Effective bandwidth
12.45 GB/s
Latency proxy
123.7 ns
Browser RAM class
32 GB class
VRAMNOT RUN

GPU-memory diagnostic

This workload was not included in the CPU + Memory suite.

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 E5-2683 v4 comparison ladder

ESTIMATE

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

  1. Intel Xeon E5-4660 v4Broadwell · 16 cores / 32 threads · 2016
    +1.9%higher estimate
  2. Intel Xeon E5-2683 v4Broadwell · 16 cores / 32 threads · 2016
    BASECATALOG REFERENCE
  3. Intel Pentium D1519Broadwell · 4 cores / 8 threads · 2016
    −59.5%lower estimate
03 / RUN QUALITY62.0%

Protocol quality signal

This signal summarizes protocol completion, visible-tab timing and selected-suite capability. It does not invent a graphics stability reading when no GPU workload ran.

COMPLETEDYES SAMPLE WINDOW10 SEC RUN QUALITY62/100

Why the run quality was reduced

  • The browser reported more threads than the selected CPU has; the selected CPU is probably wrong.
04 / ENVIRONMENTRUN CONTEXT

What the browser disclosed

Selected suite
CPU + Memory
Platform family
Windows
Logical processors
64
Browser RAM class
32 GB · rounded/capped
Graphics API
NOT RUN
Browser
Chrome 154 · Blink engine
Timer resolution
0.100 ms
Memory working set
256 MB
Run quality
Fair · 62/100
Score fingerprint
adaptive-v2.0 / 1.3.0
Current adaptive scale
Validated revision 5 / 6 October 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": "cpu",
    "test_mode": "quick",
    "duration_ms": 10276,
    "system": {
        "cpu_name": "Intel Xeon E5-2683 v4",
        "gpu_name": "NVIDIA Quadro M2000",
        "logical_cores": 64,
        "memory_gb": 32,
        "platform": "windows",
        "gpu_api": "not_tested",
        "browser_engine": "blink",
        "browser_name": "chrome",
        "browser_version": 154,
        "timer_resolution_ms": 0.1,
        "cross_origin_isolated": false,
        "on_battery": false,
        "processor_id": 2757,
        "graphics_card_id": 2103
    },
    "metrics": {
        "stability": {
            "duration_seconds": 10,
            "completed": true,
            "dropped_frames_percent": 0
        },
        "cpu": {
            "single_core_ops_per_second": 308681219.357,
            "multi_core_ops_per_second": 3449303201.871,
            "compression_mb_per_second": 467.896
        },
        "memory": {
            "bandwidth_gbps": 12.45,
            "latency_ns": 123.708,
            "working_set_mb": 256
        }
    },
    "raw_points": {
        "cpu": 16.12869555,
        "gpu": null,
        "memory": 0.68210519
    },
    "quality_flags": [
        "thread_mismatch"
    ],
    "original_scores": {
        "cpu": 26,
        "gpu": null,
        "memory": 49,
        "vram": null,
        "overall": null,
        "grade": null
    },
    "current_scores": {
        "cpu": 26,
        "gpu": null,
        "memory": 49,
        "vram": null,
        "overall": null,
        "performance_index": null,
        "leaderboard_outlier": false,
        "grade": null,
        "snapshot_revision": 5
    },
    "runner_version": "1.3.0",
    "workload_signature": "browser-1.3",
    "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 CPU + Memory suite and Quick mode again.

Run it again