Notebookcheck Logo

Intel HD Graphics P630 vs Intel UHD Graphics P630 vs Intel Iris Plus Graphics 650

Intel HD Graphics P630

► remove from comparison Intel HD Graphics P630

The Intel HD Graphics P630 (GT2) is an integrated graphics unit, which can be found in various Xeon workstation processors of the Kaby Lake generation. The "GT2" version of the Skylake GPU offers 24 Execution Units (EUs) clocked at up to 1050 MHz (depending on the CPU model). Due to its lack of dedicated graphics memory or eDRAM cache, the P630 has to access the main memory (2x 64bit DDR3L-1600 / DDR4-2133). It uses the same silicon as the consumer HD Graphics 630 in Kaby-Lake-H processors but features optimized drivers for workstaion and CAD software. According to Intel it is certified for 15 applications (see list).

Performance

According to Intel, the performance of the P630 is identical to the Intel HD Graphis P530 (Skylake predecessor) processor graphics card and 1.94x faster than the old Intel HD Graphics P4000. Compared to consumer cards, the gaming performance should be on a similar level to the dedicated GeForce 920M and will handle old games (as of 2015) in low or medium settings.

Features

The revised video engine in the Kaby Lake chips now supports H.265/HEVC Main10 profile at 10-bit color depth and also the VP9 codec in hardware. Furthermore, HDCP 2.2 is also supported in all chips, which allows Netflix 4K videos, for instance.

Power Consumption

The HD Graphics P630 can be found in mobile quad-core Xeon processors with 45 W TDP and also desktop processors of the Xeon range with higher TDPs.

Sourcehttp://www.intel.com/content/dam/www/public/us/en/documents/guides/hd-graphics-performance-guide.pdf

Intel UHD Graphics P630

► remove from comparison Intel UHD Graphics P630

The Intel UHD Graphics P630 (GT2) is a professional integrated graphics card, which can be found in various Xeon desktop and notebook processors of the Coffee-Lake generation. The "GT2" version of the GPU offers 24 Execution Units (EUs) and the clocks depend on the CPU model. Due to its lack of dedicated graphics memory or eDRAM cache, the UHD P630 has to access the main memory (2x 64-bit DDR3L-1600 / DDR4-2133). Compared to the older HD Graphics P630 (Kaby-Lake), the newer UHD GPU is identical but can be clocked slightly higher. Compared to the regular UHD 630, the P630 supports ECC main memory and is intended for professional applications.

Performance

The exact performance of the UHD Graphics P630 depends on various factors like TDP, L3 Cache, memory (DDR3/DDR4) and maximum clock rate of the specific model. However, it should be fairly similar to the HD Graphics 530 and HD Graphics 630 and therefore only suited for low demanding games like Overwatch or Farming Simulator 2017 (low details).

Features

The features of the UHD P630 are the same as for the HD 630 and therefore H.265/HEVC Main10 profile at 10-bit color depth are supported in hardware. Furthermore, HDCP 2.2 is also supported in all chips, which allows Netflix 4K videos, for instance. HDMI 2.0 however is still only supported with an external converter chip (LSPCon).

Power Consumption

The UHD Graphics P630 can be found in several notebook and desktop processors of different TDP classes.

Intel Iris Plus Graphics 650

► remove from comparison Intel Iris Plus Graphics 650

The Intel Iris Plus Graphics 650 (GT3e) is a processor graphics card for Kaby Lake models announced in January 2017. As the successor to the Intel Iris Graphics 550 (Skylake), the Iris Plus Graphics 650 is used for 28-Watt models and is equipped with 64 MB eDRAM cache. There should not be any big changes compared to the Iris Graphics 550.

The so called GT3e version of the Kaby Lake GPU probably still has 48 Execution Units (EUs), which can reach up to 1100 MHz depending on the model. Besides eDRAM cache, the Iris 650 can also access the system memory (2x 64 Bit DDR3L-1600/DDR4-2400) via processor interface.

Compared to the Iris Plus 640 from the 15-Watt models, the Iris 650 only has a slightly higher maximum clock as well as almost twice the TDP, which allows a better utilization of the Turbo Boost potential.

Performance

The exact performance of the Iris Plus Graphics 650 depends on the CPU model, because maximum clock as well as the size of the L3 cache can differ a bit. The system memory (DDR3/DDR4) will influence the performance as well.

The fastest chips are high-clocked Core i7 models like the Core i7-7567U. Depending on the game, the Iris Plus 650 will probably be on par with a dedicated GeForce 930M and can handle smooth gameplay in modern titles in low up to medium settings.

Features

The reworked video engine now fully supports hardware decoding of H.265/HEVC videos. Contrary to Skylake, however, Kaby Lake can now also decode H.265/HEVC Main 10 with a 10-bit color depth as well as Google's VP9 codec. The video output is possible via DP 1.2/eDP 1.3 (up to 3840 x 2160 @60 Hz), whereas HDMI is also supported in the older 1.4a standard. An HDMI 2.0 output can be added via converter from DisplayPort. The GPU can drive up to three displays simultaneously.

Power Consumption

The Iris Plus Graphics 650 is used for 28-Watt processor and therefore medium-sized notebooks.

Intel HD Graphics P630Intel UHD Graphics P630Intel Iris Plus Graphics 650
Gen. 9.5 Series
Iris Plus Graphics 655 48 @ 0.3 - 1.2 GHz
Iris Plus Graphics 650 48 @ 0.3 - 1.1 GHz64/128 Bit
Iris Plus Graphics 645 48 @ 0.3 - 1.15 GHz
Iris Plus Graphics 640 48 @ 0.3 - 1.05 GHz64/128 Bit
UHD Graphics 630 24 @ 0.3 - 1.15 GHz64/128 Bit
UHD Graphics P630 24 @ 0.3 - 1.2 GHz64/128 Bit
HD Graphics 630 24 @ 0.3 - 1.15 GHz64/128 Bit
HD Graphics P630 24 64/128 Bit
UHD Graphics 620 24 @ 0.3 - 1.15 GHz
HD Graphics 620 24 @ 0.3 - 1.05 GHz64/128 Bit
UHD Graphics 617 24 @ 0.3 - 1.15 GHz64/128 Bit
UHD Graphics 615 24 @ 0.3 - 1 GHz64/128 Bit
HD Graphics 615 24 @ 0.3 - 1.05 GHz64/128 Bit
Iris Plus Graphics 655 48 @ 0.3 - 1.2 GHz
Iris Plus Graphics 650 48 @ 0.3 - 1.1 GHz64/128 Bit
Iris Plus Graphics 645 48 @ 0.3 - 1.15 GHz
Iris Plus Graphics 640 48 @ 0.3 - 1.05 GHz64/128 Bit
UHD Graphics 630 24 @ 0.3 - 1.15 GHz64/128 Bit
UHD Graphics P630 24 @ 0.3 - 1.2 GHz64/128 Bit
HD Graphics 630 24 @ 0.3 - 1.15 GHz64/128 Bit
HD Graphics P630 24 64/128 Bit
UHD Graphics 620 24 @ 0.3 - 1.15 GHz
HD Graphics 620 24 @ 0.3 - 1.05 GHz64/128 Bit
UHD Graphics 617 24 @ 0.3 - 1.15 GHz64/128 Bit
UHD Graphics 615 24 @ 0.3 - 1 GHz64/128 Bit
HD Graphics 615 24 @ 0.3 - 1.05 GHz64/128 Bit
Iris Plus Graphics 655 48 @ 0.3 - 1.2 GHz
Iris Plus Graphics 650 48 @ 0.3 - 1.1 GHz64/128 Bit
Iris Plus Graphics 645 48 @ 0.3 - 1.15 GHz
Iris Plus Graphics 640 48 @ 0.3 - 1.05 GHz64/128 Bit
UHD Graphics 630 24 @ 0.3 - 1.15 GHz64/128 Bit
UHD Graphics P630 24 @ 0.3 - 1.2 GHz64/128 Bit
HD Graphics 630 24 @ 0.3 - 1.15 GHz64/128 Bit
HD Graphics P630 24 64/128 Bit
UHD Graphics 620 24 @ 0.3 - 1.15 GHz
HD Graphics 620 24 @ 0.3 - 1.05 GHz64/128 Bit
UHD Graphics 617 24 @ 0.3 - 1.15 GHz64/128 Bit
UHD Graphics 615 24 @ 0.3 - 1 GHz64/128 Bit
HD Graphics 615 24 @ 0.3 - 1.05 GHz64/128 Bit
CodenameKaby-Lake-H-GT2Coffee-Lake-GT2Kaby Lake GT3e
ArchitectureGen. 9.5 Kaby LakeGen. 9.5Gen. 9.5 Kaby Lake
Pipelines24 - unified24 - unified48 - unified
Memory Bus Width64/128 Bit64/128 Bit64/128 Bit
Shared Memoryyesyesyes
APIDirectX 12_1, OpenGL 4.4DirectX 12_1, OpenGL 4.4DirectX 12_1, OpenGL 4.4
technology14 nm14 nm14 nm
FeaturesQuickSyncQuickSyncQuickSync
Date of Announcement05.08.2015 01.10.2017 03.01.2017
Core Speed300 - 1200 (Boost) MHz300 - 1100 (Boost) MHz
Memory TypeDDR4
CPU in HD Graphics P630GPU Base SpeedGPU Boost / Turbo
Intel Xeon E3-1535M v64 x 3100 MHz, 45 W300 MHz1150 MHz
Intel Xeon E3-1505M v64 x 3000 MHz, 45 W300 MHz1150 MHz
min. - max.300 MHz1150 MHz
CPU in UHD Graphics P630GPU Base SpeedGPU Boost / Turbo
Intel Xeon W-10885M8 x 2400 MHz, 45 W350 MHz1200 MHz
Intel Xeon E-2276M6 x 2800 MHz, 45 W350 MHz1200 MHz
Intel Xeon E-2176G6 x 3700 MHz, 80 W350 MHz1200 MHz
Intel Xeon W-10855M6 x 2800 MHz, 45 W350 MHz? MHz
min. - max.300 - 350 MHz? - 1200 MHz
CPU in Iris Plus Graphics 650GPU Base SpeedGPU Boost / Turbo
Intel Core i7-7567U2 x 3500 MHz, 28 W300 MHz1100 MHz
Intel Core i5-7287U2 x 3300 MHz, 28 W300 MHz1100 MHz
Intel Core i5-7267U2 x 3100 MHz, 28 W300 MHz1050 MHz
Intel Core i3-7167U2 x 2800 MHz, 28 W300 MHz1000 MHz
min. - max.300 - 350 MHz1000 - 1200 MHz

Benchmarks

3DMark - 3DMark Time Spy Score
400 Points (2%)
623 Points (3%)
3DMark - 3DMark Time Spy Graphics
555 Points (3%)
3DMark - 3DMark Ice Storm Unlimited Graphics
161538 Points (19%)
3DMark - 3DMark Cloud Gate Score
8280 Points (9%)
min: 8403     avg: 9150     median: 9149.5 (10%)     max: 9896 Points
3DMark - 3DMark Cloud Gate Graphics
13153 Points (5%)
3DMark - 3DMark Fire Strike Standard Score
1040 Points (2%)
min: 1586     avg: 1655     median: 1655 (4%)     max: 1724 Points
3DMark - 3DMark Fire Strike Standard Graphics
1698 Points (3%)
3DMark 11 - 3DM11 Performance Score
2924 Points (6%)
3DMark 11 - 3DM11 Performance GPU
2762 Points (4%)
3DMark 06 3DMark 06 - Standard 1280x1024 + Intel Iris Plus Graphics 650
3DMark 06
15175 Points (22%)
Cinebench R10 Cinebench R10 Shading (32bit) + Intel Iris Plus Graphics 650
Cinebench R10 - Cinebench R10 Shading (32bit)
8773 Points (6%)
Cinebench R11.5 Cinebench R11.5 OpenGL 64 Bit + Intel Iris Plus Graphics 650
Cinebench R11.5 - Cinebench R11.5 OpenGL 64 Bit
45.2 fps (16%)
Cinebench R15
Cinebench R15 OpenGL 64 Bit + Intel Iris Plus Graphics 650
Cinebench R15 - Cinebench R15 OpenGL 64 Bit
min: 41.21     avg: 59.1     median: 59.1 (15%)     max: 77 fps
Cinebench R15 OpenGL Ref. Match 64 Bit + Intel Iris Plus Graphics 650
Cinebench R15 - Cinebench R15 OpenGL Ref. Match 64 Bit
99.3 % (99%)
LuxMark v2.0 64Bit - LuxMark v2.0 Room GPU
336 Samples/s (2%)
LuxMark v2.0 64Bit - LuxMark v2.0 Sala GPU
813 Samples/s (1%)
ComputeMark v2.1 - ComputeMark v2.1 Result
1730 Points (3%)
Power Consumption - Furmark Stress Test Power Consumption - external Monitor *
51.4 Watt (8%)
Power Consumption - The Witcher 3 Power Consumption - external Monitor *
51.4 Watt (7%)
Clock Speed - GPU Clock Witcher 3 ultra
998 MHz (50%)
Clock Speed - GPU Clock Speed Furmark
848 MHz (34%)

Average Benchmarks Intel HD Graphics P630 → NAN% n=

Average Benchmarks Intel Iris Plus Graphics 650 → NAN% n=

- Range of benchmark values for this graphics card
- Average benchmark values for this graphics card
* Smaller numbers mean a higher performance
1 This benchmark is not used for the average calculation

Game Benchmarks

The following benchmarks stem from our benchmarks of review laptops. The performance depends on the used graphics memory, clock rate, processor, system settings, drivers, and operating systems. So the results don't have to be representative for all laptops with this GPU. For detailed information on the benchmark results, click on the fps number.

Dirt 4

Dirt 4

2017
low 1280x720
Iris Plus Graphics 650:
64  fps
med. 1920x1080
Iris Plus Graphics 650:
21.3  fps
high 1920x1080
Iris Plus Graphics 650:
14.2  fps
low 1280x720
Iris Plus Graphics 650:
113  fps
med. 1920x1080
Iris Plus Graphics 650:
56.8  fps
high 1920x1080
Iris Plus Graphics 650:
38.9  fps
Prey

Prey

2017
low 1280x720
Iris Plus Graphics 650:
51.4  fps
med. 1920x1080
Iris Plus Graphics 650:
20.2  fps
low 1280x720
Iris Plus Graphics 650:
25.8  fps
med. 1920x1080
Iris Plus Graphics 650:
10.5  fps
low 1280x720
Iris Plus Graphics 650:
17.6  fps
For Honor

For Honor

2017
low 1280x720
Iris Plus Graphics 650:
39.7  fps
med. 1920x1080
Iris Plus Graphics 650:
15.2  fps
low 1280x720
Iris Plus Graphics 650:
15  fps
low 1280x720
Iris Plus Graphics 650:
32.4  fps
low 1280x720
Iris Plus Graphics 650:
54.1  fps
med. 1366x768
Iris Plus Graphics 650:
37.9  fps
high 1920x1080
Iris Plus Graphics 650:
36.8  fps
ultra 1920x1080
Iris Plus Graphics 650:
19.9  fps
low 1280x720
Iris Plus Graphics 650:
46.1  fps
med. 1366x768
Iris Plus Graphics 650:
29.5  fps
low 1024x768
Iris Plus Graphics 650:
42.2  fps
med. 1366x768
Iris Plus Graphics 650:
20.2  fps
low 1280x720
Iris Plus Graphics 650:
19.2  fps
med. 1366x768
Iris Plus Graphics 650:
14.6  fps
high 1920x1080
Iris Plus Graphics 650:
8.2  fps
Overwatch

Overwatch

2016
low 1280x720
Iris Plus Graphics 650:
79.2  fps
med. 1366x768
Iris Plus Graphics 650:
57.4  fps
high 1920x1080
Iris Plus Graphics 650:
25.6  fps
ultra 1920x1080
Iris Plus Graphics 650:
21.4  fps
low 1280x720
Iris Plus Graphics 650:
30  fps
low 1280x720
Iris Plus Graphics 650:
32  fps
med. 1920x1080
Iris Plus Graphics 650:
15  fps
low 1024x768
Iris Plus Graphics 650:
25.9  fps
med. 1366x768
Iris Plus Graphics 650:
18.3  fps
low 1024x768
Iris Plus Graphics 650:
54.2  fps
med. 1366x768
Iris Plus Graphics 650:
35.6  fps
high 1920x1080
Iris Plus Graphics 650:
20.8  fps
low 1280x720
Iris Plus Graphics 650:
95  fps
med. 1366x768
Iris Plus Graphics 650:
64  fps
high 1920x1080
Iris Plus Graphics 650:
29.7  fps
ultra 1920x1080
Iris Plus Graphics 650:
25  fps
low 1024x768
Iris Plus Graphics 650:
21.4  fps
GTA V

GTA V

2015
low 1024x768
Iris Plus Graphics 650:
56.5  fps
med. 1366x768
Iris Plus Graphics 650:
49.9  fps
high 1920x1080
Iris Plus Graphics 650:
11.6  fps
ultra 1920x1080
Iris Plus Graphics 650:
5  fps
low 1280x720
Iris Plus Graphics 650:
84  fps
med. 1366x768
Iris Plus Graphics 650:
54.4  fps
high 1366x768
Iris Plus Graphics 650:
46.5  fps
ultra 1920x1080
Iris Plus Graphics 650:
13.3  fps

For more games that might be playable and a list of all games and graphics cards visit our Gaming List

v1.18
log 05. 17:39:05

#0 checking url part for id 7657 +0s ... 0s

#1 checking url part for id 9906 +0s ... 0s

#2 checking url part for id 7655 +0s ... 0s

#3 not redirecting to Ajax server +0s ... 0s

#4 did not recreate cache, as it is less than 5 days old! Created at Sun, 02 Oct 2022 17:27:15 +0200 +0s ... 0s

#5 linkCache_getLink using $NBC_LINKCACHE +0.052s ... 0.053s

#6 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#7 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#8 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#9 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#10 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#11 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#12 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#13 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#14 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#15 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#16 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.056s

#17 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#18 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#19 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#20 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#21 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#22 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#23 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#24 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#25 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#26 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#27 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#28 composed specs +0s ... 0.056s

#29 did output specs +0s ... 0.056s

#30 start showIntegratedCPUs +0s ... 0.056s

#31 getting avg benchmarks for device 7657 +0.04s ... 0.096s

#32 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.097s

#33 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.097s

#34 got single benchmarks 7657 +0.004s ... 0.101s

#35 getting avg benchmarks for device 9906 +0s ... 0.101s

#36 got single benchmarks 9906 +0s ... 0.101s

#37 getting avg benchmarks for device 7655 +0s ... 0.101s

#38 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.102s

#39 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.102s

#40 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.102s

#41 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.103s

#42 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.103s

#43 got single benchmarks 7655 +0.005s ... 0.108s

#44 got avg benchmarks for devices +0s ... 0.108s

#45 linkCache_getLink no uid found +0s ... 0.108s

#46 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.108s

#47 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.109s

#48 linkCache_getLink no uid found +0s ... 0.109s

#49 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.109s

#50 linkCache_getLink no uid found +0s ... 0.109s

#51 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.11s

#52 linkCache_getLink no uid found +0s ... 0.11s

#53 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.11s

#54 linkCache_getLink no uid found +0s ... 0.11s

#55 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.111s

#56 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.111s

#57 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.111s

#58 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.112s

#59 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.112s

#60 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.112s

#61 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.113s

#62 linkCache_getLink no uid found +0s ... 0.113s

#63 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.113s

#64 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.113s

#65 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.114s

#66 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.114s

#67 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.114s

#68 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.114s

#69 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.115s

#70 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.115s

#71 min, max, avg, median took s +0.001s ... 0.116s

#72 before gaming benchmark output +0s ... 0.116s

#73 Got 51 rows for game benchmarks. +0.009s ... 0.124s

#74 composed SQL query for gamebenchmarks +0s ... 0.124s

#75 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.124s

#76 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.124s

#77 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.124s

#78 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.124s

#79 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#80 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#81 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#82 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#83 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#84 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#85 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#86 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#87 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#88 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#89 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#90 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#91 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#92 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#93 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#94 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#95 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#96 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#97 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#98 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#99 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#100 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.125s

#101 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.126s

#102 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.126s

#103 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.126s

#104 got data and put it in $dataArray +0.001s ... 0.126s

#105 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.127s

#106 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.127s

#107 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.127s

#108 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.127s

#109 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.128s

#110 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.128s

#111 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.128s

#112 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.128s

#113 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.129s

#114 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.129s

#115 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.129s

#116 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.13s

#117 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.13s

#118 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.131s

#119 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.131s

#120 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.132s

#121 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.132s

#122 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.133s

#123 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.133s

#124 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.133s

#125 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.133s

#126 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.134s

#127 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.134s

#128 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.135s

#129 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.135s

#130 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.135s

#131 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.135s

#132 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.135s

#133 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.135s

#134 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.135s

#135 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.136s

#136 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.137s

#137 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.137s

#138 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.137s

#139 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.137s

#140 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.138s

#141 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.138s

#142 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.138s

#143 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.139s

#144 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.139s

#145 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.139s

#146 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.139s

#147 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.139s

#148 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.14s

#149 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.14s

#150 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.14s

#151 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.14s

#152 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.141s

#153 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.141s

#154 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.141s

#155 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.141s

#156 benchmarks composed for output. +0s ... 0.141s

#157 calculated avg scores. +0s ... 0.141s

#158 return log +0.001s ... 0.141s

Please share our article, every link counts!
.170
> Notebook / Laptop Reviews and News > Benchmarks / Tech > Graphics Card Comparison - Head 2 Head
Redaktion, 2017-09- 8 (Update: 2017-09-11)