Notebookcheck Logo

Mediatek MT8173 vs Mediatek MT8183 vs Mediatek MT8173C

Mediatek MT8173

► remove from comparison  MT8173

The Mediatek MT8173 is an upper mainstream ARM SoC (System on a chip) that was introduced in March 2015 and is primarily used for Android based tablets. It is manufactured in a 28 nm process and has a total of four CPU cores with two Cortex-A72 and two Cortex-A53 cores in a big.LITTLE configuration. The graphics unit is based on the IMG Series 6XT (Rogue) and has the designation PowerVR GX6250. Among others, the GPU includes a video decoder with 4K and H.265 support.

Processor

The biggest highlight of the SoC are the new Cortex-A72 cores, which can be seen as the successors to the Cortex-A57 design. ARM promises much more performance in combination with reduced power consumption, which results in an excellent per-thread performance with the very high maximum clock of 2.4 GHz. The architecture is based on ARMv8-ISA and therefore supports 64-bit.

The two slower, but therefore very frugal Cortex-A53 cores (clocks unknown, probably around 1.5 GHz) are supposed to reduce the power consumption and are always active with light workloads. The big.LITTLE configuration also allows the simultaneous use of all four cores (or any combination of cores from both clusters), so the MT8173 can be called a real quad-core.

Graphics

The graphics unit is based on Series 6XT (Rogue) from IMG and has the designation PowerVR GX6250. The 2-cluster chip has a unified-shader architecture with a total of 64 FP32 ALUs as well as 4 TMUs. Thanks to the comparatively high maximum clock of 700 MHz, the performance is roughly on par with the PowerVR G6430 in the iPhone 5s. High-resolution screens and complex Android games from 2015 are usually no problem for the GPU.

Features

Besides CPU and GPU, the chip is also equipped with an LPDDR3 memory controller (2x 32-bit, probably up to 933 MHz, 14.9 GB/s), but no wireless modem. The maximum display resolution is 2560 x 1600 pixels. Another highlight is the integrated video engine, which even supports 4K material and the modern H.265 codec.

Power Consumption

The MT8173 is manufactured in an 28 nm process and should have a average up to high power consumption. It can still be used in tablets without limitations.

Mediatek MT8183

► remove from comparison  MT8183

The Mediatek MT8183 is a mainstream ARM SoC (System on a Chip) that was introduced in Late 2019 and is primarily used for Android based tablets. It is manufactured in a 12 nm process (unverified) and has a total of eight CPU cores with four powerful Cortex-A73 and four small Cortex-A53 cores in a big.LITTLE configuration. The integrated graphics card is a ARM Mali-G72 with three clusters (MP3).

Features

Besides CPU and GPU, the chip is also equipped with an LPDDR3/LPDDR4x memory controller, a Wi-Fi 5 (a/b/g/n/ac) modem (but no cellular modem). Furthermore, Mediatek states that it integrated an AI accelerator with a performance of 0.5 TOPS.

The maximum display resolution is only 2,400 x 1,080 pixels.

Mediatek MT8173C

► remove from comparison  MT8173C

The Mediatek MT8173C is an upper mainstream ARM SoC (System on a chip) that was introduced in March 2015 and is primarily used for Android based tablets and Chromebooks. It is manufactured in a 28 nm process and has a total of four CPU cores with two Cortex-A72 and two Cortex-A53 cores in a big.LITTLE configuration. The graphics unit is based on the IMG Series 6XT (Rogue) and has the designation PowerVR GX6250. Among others, the GPU includes a video decoder with 4K and H.265 support.

Processor

The biggest highlight of the SoC are the new Cortex-A72 cores, which can be seen as the successors to the Cortex-A57 design. ARM promises much more performance in combination with reduced power consumption, which results in an excellent per-thread performance with the very high maximum clock of 2.4 GHz. The architecture is based on ARMv8-ISA and therefore supports 64-bit.

The two slower, but therefore very frugal Cortex-A53 cores (clocks unknown, probably around 1.5 GHz) are supposed to reduce the power consumption and are always active with light workloads. The big.LITTLE configuration also allows the simultaneous use of all four cores (or any combination of cores from both clusters), so the MT8173C can be called a real quad-core.

Graphics

The graphics unit is based on Series 6XT (Rogue) from IMG and has the designation PowerVR GX6250. The 2-cluster chip has a unified-shader architecture with a total of 64 FP32 ALUs as well as 4 TMUs. Thanks to the comparatively high maximum clock of 700 MHz, the performance is roughly on par with the PowerVR G6430 in the iPhone 5s. High-resolution screens and complex Android games from 2015 are usually no problem for the GPU.

Features

Besides CPU and GPU, the chip is also equipped with an LPDDR3 memory controller (2x 32-bit, probably up to 933 MHz, 14.9 GB/s), but no wireless modem. The maximum display resolution is 2560 x 1600 pixels. Another highlight is the integrated video engine, which even supports 4K material and the modern H.265 codec.

Power Consumption

The MT8173 is manufactured in an 28 nm process and should have a average up to high power consumption. It can still be used in tablets and laptops without limitations.

ModelMediatek MT8173Mediatek MT8183Mediatek MT8173C
Series Mediatek Mediatek MT8 Mediatek
CodenameCortex-A72/-A53Cortex-A73/-A53Cortex-A72/-A53
Series: Mediatek Cortex-A72/-A53
Mediatek MT81762.1 GHz6 / 6 Cortex-A72/-A53
» Mediatek MT81732.4 GHz4 / 4 Cortex-A72/-A53
Mediatek MT8173C2.1 GHz4 / 4 Cortex-A72/-A53
Mediatek MT81762.1 GHz6 / 6 Cortex-A72/-A53
Mediatek MT81732.4 GHz4 / 4 Cortex-A72/-A53
» Mediatek MT8173C2.1 GHz4 / 4 Cortex-A72/-A53
Clock2400 MHz2000 MHz2100 MHz
Cores / Threads4 / 48 / 84 / 4
Technology28 nm12 nm28 nm
Features20 MP Camera ISP, 4K Video Encoder, H.265, PowerVR GX6250 GPU32 MP Camera ISP, 1080p H.264 Video Encoder, H.265 Decoder20 MP Camera ISP, 4K Video Encoder, H.265, PowerVR GX6250 GPU
iGPUPowerVR GX6250 (? - 700 MHz)ARM Mali-G72 MP3PowerVR GX6250 (? - 700 MHz)
ArchitectureARMARMARM
Announced

Benchmarks

Performance Rating - Geekbench 5.1, PCM Work, Sling Shot Physics, Antutu v8 CPU - MT8183
23 pt (39%)
3DMark - 3DMark Ice Storm Unlimited Physics
15117 Points (13%)
min: 15776     avg: 18163     median: 18829 (16%)     max: 19883 Points
13994 Points (12%)
3DMark - 3DMark Sling Shot Extreme (ES 3.1) Unlimited Physics
100%
1 MT8173 +
1386 Points (17%)
183%
1 MT8183 +
min: 2085     avg: 2531     median: 2542 (32%)     max: 2966 Points
3DMark - 3DMark Sling Shot (ES 3.0) Unlimited Physics
1399 Points (20%)
min: 2322     avg: 2590     median: 2543 (37%)     max: 2963 Points
1382 Points (20%)
Geekbench 2 - 32 Bit - Geekbench Stream
100%
1 MT8183 +
805 Points (6%)
Geekbench 2 - 32 Bit - Geekbench Memory
100%
1 MT8183 +
1718 Points (16%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
100%
1 MT8183 +
10758 Points (21%)
Geekbench 2 - 32 Bit - Geekbench Integer
100%
1 MT8183 +
5381 Points (11%)
Geekbench 2 - 32 Bit - Geekbench Total Score
100%
1 MT8183 +
6072 Points (16%)
Geekbench 3 - Geekbench 3 64 Bit Multi-Core
100%
1 MT8173 +
2909 Points (5%)
214%
1 MT8183 +
min: 5754     avg: 6212     median: 6212 (10%)     max: 6670 Points
Geekbench 3 - Geekbench 3 64 Bit Single-Core
100%
1 MT8173 +
1385 Points (28%)
106%
1 MT8183 +
min: 1410     avg: 1469     median: 1468.5 (30%)     max: 1527 Points
Geekbench 4.0 - Geekbench 4.0 64 Bit Single-Core
100%
1 MT8183 +
1395 Points (22%)
104%
1 MT8173C +
1451 Points (22%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Multi-Core
100%
1 MT8183 +
4968 Points (12%)
2570 Points (6%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Single-Core
100%
1 MT8173 +
1204 Points (14%)
119%
1 MT8183 +
min: 1397     avg: 1431     median: 1430.5 (17%)     max: 1464 Points
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Multi-Core
100%
1 MT8173 +
3305 Points (4%)
163%
1 MT8183 +
min: 5308     avg: 5377     median: 5376.5 (7%)     max: 5445 Points
Geekbench 5.0 - Geekbench 5.0 64 Bit Single-Core
0 Points (0%)
Geekbench 5.0 - Geekbench 5.0 64 Bit Multi-Core
0 Points (0%)
Geekbench 5.3 - Geekbench 5.1 - 5.4 64 Bit Single-Core
100%
1 MT8183 +
min: 260     avg: 292     median: 301.5 (15%)     max: 305 Points
Geekbench 5.3 - Geekbench 5.1 - 5.4 64 Bit Multi-Core
100%
1 MT8183 +
min: 909     avg: 1184     median: 1198.5 (4%)     max: 1430 Points
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
3976 ms (5%)
min: 3957     avg: 4403     median: 4337.5 (5%)     max: 4979 ms
min: 2976     avg: 3319     median: 3297 (4%)     max: 3684 ms
Sunspider - Sunspider 1.0 Total Score *
100%
1 MT8173C +
min: 578     avg: 669     median: 590 (6%)     max: 839 ms
Octane V2 - Octane V2 Total Score
8570 Points (9%)
min: 8665     avg: 9510     median: 9671.5 (10%)     max: 10030 Points
min: 10139     avg: 10516     median: 10319 (11%)     max: 11089 Points
WebXPRT 3 - WebXPRT 3 Score
100%
1 MT8183 +
min: 46     avg: 54.3     median: 55.5 (15%)     max: 60 Points
AnTuTu v6 - AnTuTu v6 Total Score
100%
1 MT8173 +
63777 Points (22%)
AnTuTu v7 - AnTuTu v7 MEM
100%
1 MT8173 +
6544 Points (20%)
0 Points (0%)
AnTuTu v7 - AnTuTu v7 UX
100%
1 MT8173 +
22256 Points (27%)
0 Points (0%)
AnTuTu v7 - AnTuTu v7 GPU
100%
1 MT8173 +
11012 Points (3%)
0 Points (0%)
AnTuTu v7 - AnTuTu v7 CPU
100%
1 MT8173 +
37905 Points (23%)
0 Points (0%)
AnTuTu v7 - AnTuTu v7 Total Score
100%
1 MT8173 +
77717 Points (14%)
0 Points (0%)
AnTuTu v8 - AnTuTu v8 UX
100%
1 MT8183 +
32912 Points (28%)
AnTuTu v8 - AnTuTu v8 MEM
100%
1 MT8183 +
32293 Points (26%)
AnTuTu v8 - AnTuTu v8 GPU
100%
1 MT8183 +
25424 Points (5%)
AnTuTu v8 - AnTuTu v8 CPU
100%
1 MT8183 +
67925 Points (25%)
AnTuTu v8 - AnTuTu v8 Total Score
100%
1 MT8183 +
158554 Points (15%)
PassMark PerformanceTest Mobile V1 - PerformanceTest Mobile CPU Tests
100%
1 MT8183 +
175006 Points (23%)
PCMark for Android - PCM f. Android Work 2.0 Battery Life
100%
1 MT8173 +
509 min (10%)
PCMark for Android - PCM f. Android Computer Vision
100%
1 MT8173 +
2620 Points (14%)
120%
1 MT8183 +
min: 2714     avg: 3143     median: 3143 (17%)     max: 3572 Points
PCMark for Android - PCM f. Android Storage
100%
1 MT8173 +
3656 Points (10%)
305%
1 MT8183 +
min: 6470     avg: 11152     median: 11152 (30%)     max: 15834 Points
PCMark for Android - PCM f. Android Work Score 2.0
100%
1 MT8173 +
3678 Points (24%)
PCMark for Android - PCM f. Android Work Score
100%
1 MT8173 +
4895 Points (24%)
152%
1 MT8183 +
min: 6284     avg: 7442     median: 7441.5 (37%)     max: 8599 Points
PCMark for Android - PCM f. Android Storage 2.0 score
100%
1 MT8183 +
min: 6087     avg: 13047     median: 13046.5 (36%)     max: 20006 Points
PCMark for Android - PCM f. Android Work Score 3.0
100%
1 MT8183 +
min: 5224     avg: 5628     median: 5346 (29%)     max: 6315 Points
Power Consumption - Geekbench 5.4 Power Consumption 150cd *
100%
1 MT8183 +
min: 3.4     avg: 3.4     median: 3.4 (15%)     max: 3.44 Watt
0123456Tooltip
Power Consumption - Idle Power Consumption 150cd *
100%
1 MT8183 +
min: 1.871     avg: 1.9     median: 1.9 (7%)     max: 1.889 Watt
00.10.30.40.60.70.811.11.31.41.51.71.822.12.22.42.52.7Tooltip

Average Benchmarks Mediatek MT8173 → 100% n=4

Average Benchmarks Mediatek MT8183 → 130% n=4

Average Benchmarks Mediatek MT8173C → 103% n=4

- 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

v1.17
log 27. 00:38:21

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

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

#2 checking url part for id 8520 +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 Wed, 22 Jun 2022 13:12:54 +0200 +0s ... 0s

#5 linkCache_getLink no uid found +0.006s ... 0.007s

#6 linkCache_getLink no uid found +0.003s ... 0.01s

#7 linkCache_getLink no uid found +0.003s ... 0.012s

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

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

#10 composed specs +0s ... 0.012s

#11 did output specs +0s ... 0.012s

#12 getting avg benchmarks for device 6666 +0s ... 0.013s

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

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

#15 got single benchmarks 6666 +0.007s ... 0.021s

#16 getting avg benchmarks for device 11547 +0.004s ... 0.025s

#17 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.026s

#18 got single benchmarks 11547 +0.012s ... 0.038s

#19 getting avg benchmarks for device 8520 +0s ... 0.038s

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

#21 got single benchmarks 8520 +0.009s ... 0.048s

#22 got avg benchmarks for devices +0s ... 0.048s

#23 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.05s

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

#25 linkCache_getLink using $NBC_LINKCACHE +0.004s ... 0.054s

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

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

#28 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.055s

#29 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.055s

#30 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.055s

#31 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.055s

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

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

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

#35 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

#36 linkCache_getLink no uid found +0s ... 0.057s

#37 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

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

#39 linkCache_getLink no uid found +0s ... 0.058s

#40 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

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

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

#43 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#44 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#45 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#46 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

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

#48 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

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

#50 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.061s

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

#52 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.061s

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

#54 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.061s

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

#56 No cached benchmark found, getting uncached values +0s ... 0.062s

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

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

#59 No cached benchmark found, getting uncached values +0s ... 0.062s

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

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

#62 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.062s

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

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

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

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

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

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

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

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

#71 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.063s

#72 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.064s

#73 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.064s

#74 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.064s

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

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

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

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

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

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

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

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

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

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

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

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

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

#88 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.066s

#89 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.067s

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

#91 No cached benchmark found, getting uncached values +0s ... 0.067s

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

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

#94 No cached benchmark found, getting uncached values +0s ... 0.068s

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

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

#97 No cached benchmark found, getting uncached values +0s ... 0.069s

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

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

#100 No cached benchmark found, getting uncached values +0s ... 0.07s

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

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

#103 No cached benchmark found, getting uncached values +0s ... 0.071s

#104 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.072s

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

#106 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.073s

#107 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.074s

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

#109 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.075s

#110 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.076s

#111 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

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

#113 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

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

#115 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

#116 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

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

#118 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

#119 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

#120 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

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

#122 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

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

#124 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

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

#126 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.078s

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

#128 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.078s

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

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

#131 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.078s

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

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

#134 linkCache_getLink using $NBC_LINKCACHE +0.015s ... 0.094s

#135 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.094s

#136 min, max, avg, median took s +0.007s ... 0.101s

#137 return log +0s ... 0.101s

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