PCBenchmark/Results/Intel Core Ultra 7 265K + NVIDIA RTX A400 browser benchmark
PC SCORE64OUT OF 100
SYSTEM GRADEC
Excellent quality run 28 September 2026 · 21:26 EEST

Intel Core Ultra 7 265K+NVIDIA RTX A400

Solid performance with room to inspect individual workload results.

SUITEFULL SYSTEM MODEQUICK GPU APIWebGPU ENGINE1.2.1 SCORE SCALEPROVISIONAL R4 DURATION00:20
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.

CPU100

Processor throughput

Single thread
869.57 Mops/s
Multi thread
14,619.31 Mops/s
Compression proxy
1,179.5 MB/s
GPU13

Graphics throughput

Estimated shader work
1,533.3 G shader ops/s
Render throughput
60.3 FPS
Frame time p95
16.80 ms
MEMORY100

System memory

Effective bandwidth
87.39 GB/s
Latency proxy
8.3 ns
Browser RAM class
32 GB class
VRAMPASS

GPU-memory diagnostic

Transfer bandwidth
4.19 GB/s
Tested allocation
128 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 Core Ultra 7 265K comparison ladder

ESTIMATE

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

  1. Intel Core Ultra 9 285KArrow Lake · 24 cores / 24 threads · 2024
    +7.6%higher estimate
  2. Intel Core Ultra 7 265KArrow Lake · 20 cores / 20 threads · 2024
    BASECATALOG REFERENCE
  3. Intel Core Ultra 5 245KArrow Lake · 14 cores / 14 threads · 2024
    −13.6%lower estimate
GPU POSITION

NVIDIA RTX A400 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 RTX A2000 EmbeddedAmpere-MW(Ax000) · 4 GB VRAM · 2022
    +122.5%higher estimate
  2. NVIDIA RTX A500 EmbeddedAmpere-MW(Ax000) · 4 GB VRAM · 2022
    +101.8%higher estimate
  3. NVIDIA RTX A1000 EmbeddedAmpere-MW(Ax000) · 4 GB VRAM · 2022
    +72.3%higher estimate
  4. NVIDIA RTX A400Workstation Ampere(Ax000) · 4 GB VRAM · 2024
    BASECATALOG REFERENCE
  5. NVIDIA P106-090Mining GPUs · 3 GB VRAM · 2017
    −13.3%lower estimate
  6. NVIDIA GeForce MX450 30.5W 8GbpsGeForce MX(4xx) · 2 GB VRAM · 2020
    −15.5%lower estimate
  7. NVIDIA GeForce GTX 1630GeForce 16 · 4 GB VRAM · 2022
    −32.5%lower estimate
03 / STABILITY100.0%

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 WINDOW20 SEC DROPPED FRAMES0.00%
04 / ENVIRONMENTRUN CONTEXT

What the browser disclosed

Selected suite
Full system
Platform family
Windows
Logical processors
20
Browser RAM class
32 GB · rounded/capped
Graphics API
WebGPU
Run quality
Excellent · 92/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": "quick",
    "duration_ms": 19944,
    "system": {
        "cpu_name": "Intel Core Ultra 7 265K",
        "gpu_name": "NVIDIA RTX A400",
        "logical_cores": 20,
        "memory_gb": 32,
        "platform": "windows",
        "gpu_api": "webgpu",
        "processor_id": 31,
        "graphics_card_id": 2783
    },
    "metrics": {
        "stability": {
            "duration_seconds": 20,
            "completed": true,
            "dropped_frames_percent": 0
        },
        "cpu": {
            "single_core_ops_per_second": 869574621.583,
            "multi_core_ops_per_second": 14619309588.419,
            "compression_mb_per_second": 1179.475
        },
        "memory": {
            "bandwidth_gbps": 87.387,
            "latency_ns": 8.332
        },
        "gpu": {
            "frames_per_second": 60.313,
            "compute_gflops": 1533.289,
            "frame_time_p95_ms": 16.8
        },
        "vram": {
            "tested_mb": 128,
            "bandwidth_gbps": 4.191,
            "errors": 0
        }
    },
    "raw_points": {
        "cpu": 52.32436686,
        "gpu": 1.27774083
    },
    "original_scores": {
        "cpu": 100,
        "gpu": 13,
        "memory": 100,
        "vram": 0,
        "overall": 64,
        "grade": "C"
    },
    "current_scores": {
        "cpu": 100,
        "gpu": 13,
        "memory": 100,
        "vram": 0,
        "overall": 64,
        "grade": "C",
        "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 Quick mode again.

Run it again