Notebookcheck Logo

AMD A6-9225 vs AMD E2-9000 vs AMD A6-9220

AMD A6-9225

► remove from comparison AMD A6-9225

The AMD A6-9225 is an entry-level chip from the Stoney-Ridge APU series for notebooks (7th APU generation), which was announced mid 2018. Compared to the one year older A4-9220, the A4-9225 has a 200 MHz higher CPU Boost clock but a slower iGPU. It integrates two CPU cores (one Excavator module with 2 integer and one FP unit) clocked at 2.6 GHz to 3.1 GHz. It also includes a Radeon R4 GPU, probably with 192 shaders at up to 686 MHz, as well as a single-channel DDR4-2133 memory controller, H.265 video decoder and chipset with all I/O ports.

Architecture

Stoney Ridge is the successor to the Carrizo architecture and the design is almost identical. Thanks to optimized manufacturing processes and more aggressive Boost behavior, however, the clocks are a bit higher at the same power consumption. The memory controller now also supports DDR4-RAM, in this case up to 2133 MHz. Stoney Ridge is the designation for the smaller dual-core and single-core chip, while Bristol Ridge is the bigger quad-core chip with dual-channel memory controller. More technical details are available in the following articles:

Performance

Because of the significantly lower clock range, the A6-9225 should be noticeably slower than the A9-9410. Therefore, it is in the absolute low end of 2018 mobile CPUs and only suited for basic tasks.

Graphics

The integrated Radeon R4 (Stoney Ridge) GPU is probably similar to the R5 with 192 active shader units (3 compute cores), but a reduced clock of just 686 MHz instead of 800 MHz. More details about the GPU are available in the linked articles above.

Power Consumption

AMD specifies the TDP of the A6-9225 with 15 Watts, but it can be configured between 10-15 Watts. This means the APU is a good choice for thin and light notebooks.

AMD E2-9000

► remove from comparison AMD E2-9000

The AMD E2-9000 is the least powerful chip from the Stoney-Ridge APU series for notebooks (7th APU generation) at the time of announcement in 2017. The SoC integrates two CPU cores (one Excavator module with 2 integer and on FP unit) clocked between 1.8-2.2 GHz. It also includes a Radeon R2 GPU clocked at 600 MHz as well as a single-channel DDR4-1866 memory controller, H.265 video engine and chipset with all I/O ports. Compared to the older E2-9010, the E2-9000 offers a lower base speed (1.8 versus 2 GHz).

Architecture

Stoney Ridge is the successor of the Carrizo architecture and the design is almost identical. Thanks to optimized manufacturing processes and more aggressive Boost behavior, however, the clocks are a bit higher at the same power consumption. The memory controller now also supports DDR4-RAM, in this case up to 1866 MHz. Stoney Ridge is the designation for the smaller dual-core and single-core chip, while Bristol Ridge is the bigger quad-core chip with dual-channel memory controller. More technical details are available in the following articles:

Power Consumption

AMD specifies the TDP of the E2-9000 with 10 Watts (compared to the 9010 at 15W). This means the APU is intended for thin and light notebooks.

AMD A6-9220

► remove from comparison AMD A6-9220

The AMD A6-9220 is an entry-level chip from the Stoney-Ridge APU series for notebooks (7th APU generation), which was announced mid 2016. The 9210 is a mid-range Stoney Ridge processor (dual-core version of Bristol Ridge) and integrates two CPU cores (one Excavator module with 2 integer and on FP unit) clocked between 2.5 - 2.9 GHz. It also includes a Radeon R4 GPU, probably with 192 shaders at 655 MHz, as well as a single-channel DDR4-2133 memory controller, H.265 video engine and chipset with all I/O ports.

Architecture

Stoney Ridge is the successor of the Carrizo architecture and the design is almost identical. Thanks to optimized manufacturing processes and more aggressive Boost behavior, however, the clocks are a bit higher at the same power consumption. The memory controller now also supports DDR4-RAM, in this case up to 2133 MHz. Stoney Ridge is the designation for the smaller dual-core and single-core chip, while Bristol Ridge is the bigger quad-core chip with dual-channel memory controller. More technical details are available in the following articles:

Performance

Because of the significantly lower clock range, the A6-9220 should be noticeably slower than the A9-9410. In the Cinebench R15 Multi benchmark e.g. it was around 15% slower in our benchmarks (see below). The single core benchmarks were quite similar overall.

Graphics Card

The integrated Radeon R4 (Stoney Ridge) GPU is probably similar to the R5 with 192 active shader units (3 compute cores), but a reduced clock of just 655 instead of 800 MHz. More details about the GPU are available in the linked articles above. 

Power Consumption

AMD specifies the TDP of the A6-9220 with 15 Watts, but it can be configured between 10-15 Watts. This means the APU is a good choice for thin and light notebooks.

ModelAMD A6-9225AMD E2-9000AMD A6-9220
SeriesAMD Bristol RidgeAMD Bristol RidgeAMD Bristol Ridge
CodenameStoney RidgeStoney RidgeStoney Ridge
Series: Bristol Ridge Stoney Ridge
AMD A9-94253.1 - 3.7 GHz2 / 2
AMD A9-9420e0 - 2.5 GHz2 / 2
AMD A9-94203 - 3.6 GHz2 / 2
AMD A9-94102.9 - 3.5 GHz2 / 2
» AMD A6-92252.6 - 3.1 GHz2 / 2
AMD A6-92202.5 - 2.9 GHz2 / 2
AMD A6-9220C1.8 - 2.7 GHz2 / 2
AMD A6-92102.4 - 2.8 GHz2 / 2
AMD A4-91202.2 - 2.5 GHz2 / 2
AMD A4-9120C1.6 - 2.4 GHz2 / 2
AMD E2-90102 - 2.2 GHz2 / 2
AMD E2-90001.8 - 2.2 GHz2 / 2
AMD A6-9220e1.6 - 2.4 GHz2 / 2
AMD A9-94253.1 - 3.7 GHz2 / 2
AMD A9-9420e0 - 2.5 GHz2 / 2
AMD A9-94203 - 3.6 GHz2 / 2
AMD A9-94102.9 - 3.5 GHz2 / 2
AMD A6-92252.6 - 3.1 GHz2 / 2
AMD A6-92202.5 - 2.9 GHz2 / 2
AMD A6-9220C1.8 - 2.7 GHz2 / 2
AMD A6-92102.4 - 2.8 GHz2 / 2
AMD A4-91202.2 - 2.5 GHz2 / 2
AMD A4-9120C1.6 - 2.4 GHz2 / 2
AMD E2-90102 - 2.2 GHz2 / 2
» AMD E2-90001.8 - 2.2 GHz2 / 2
AMD A6-9220e1.6 - 2.4 GHz2 / 2
AMD A9-94253.1 - 3.7 GHz2 / 2
AMD A9-9420e0 - 2.5 GHz2 / 2
AMD A9-94203 - 3.6 GHz2 / 2
AMD A9-94102.9 - 3.5 GHz2 / 2
AMD A6-92252.6 - 3.1 GHz2 / 2
» AMD A6-92202.5 - 2.9 GHz2 / 2
AMD A6-9220C1.8 - 2.7 GHz2 / 2
AMD A6-92102.4 - 2.8 GHz2 / 2
AMD A4-91202.2 - 2.5 GHz2 / 2
AMD A4-9120C1.6 - 2.4 GHz2 / 2
AMD E2-90102 - 2.2 GHz2 / 2
AMD E2-90001.8 - 2.2 GHz2 / 2
AMD A6-9220e1.6 - 2.4 GHz2 / 2
Clock2600 - 3100 MHz1800 - 2200 MHz2500 - 2900 MHz
L1 Cache160 KB160 KB
L2 Cache1 MB1 MB1 MB
Cores / Threads2 / 22 / 22 / 2
TDP10-15 Watt10 Watt10-15 Watt
Transistors1200 Million1200 Million1200 Million
Technology28 nm28 nm28 nm
Die Size124.5 mm2124.5 mm2124.5 mm2
max. Temp.90 °C90 °C90 °C
SocketBGABGABGA
FeaturesSingle-Channel DDR4-2133, Virtualization,Single-Channel DDR4-1866, Virtualization,Single-Channel DDR4-2133, Virtualization,
iGPUAMD Radeon R4 (Stoney Ridge) ( - 686 MHz)AMD Radeon R2 (Stoney Ridge) ( - 600 MHz)AMD Radeon R4 (Stoney Ridge) ( - 655 MHz)
Architecturex86x86x86
Announced
ManufacturerAMD Bristol Ridge A6-9225AMD Bristol Ridge E2-9000AMD Bristol Ridge A6-9220

Benchmarks

Cinebench R20 - Cinebench R20 CPU (Single Core)
100%
1 A6-9225 +
182 Points (23%)
Cinebench R20 - Cinebench R20 CPU (Multi Core)
100%
1 A6-9225 +
273 Points (1%)
Cinebench R15 - Cinebench R15 CPU Multi 64 Bit
min: 96     avg: 108.5     median: 108.5 (1%)     max: 121 Points
84 Points (1%)
05101520253035404550556065707580Tooltip
min: 109     avg: 111.5     median: 111.5 (1%)     max: 114 Points
0102030405060708090100110Tooltip
Cinebench R15 - Cinebench R15 CPU Single 64 Bit
73 Points (25%)
47 Points (16%)
min: 68     avg: 68.5     median: 68.5 (23%)     max: 69 Points
Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
min: 1.03     avg: 1.2     median: 1.2 (2%)     max: 1.44 Points
1 Points (2%)
1.4 Points (3%)
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
0.9 Points (3%)
0.6 Points (2%)
0.8 Points (3%)
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
2532 Points (23%)
1787 Points (16%)
2432 Points (22%)
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
4193 Points (6%)
2897 Points (4%)
3941 Points (5%)
wPrime 2.10 - wPrime 2.0 1024m *
852 s (10%)
1242 s (15%)
915 s (11%)
wPrime 2.10 - wPrime 2.0 32m *
26.3 s (5%)
36.2 s (7%)
27.7 s (6%)
WinRAR - WinRAR 4.0
852 Points (5%)
744 Points (4%)
770 Points (4%)
X264 HD Benchmark 4.0 - x264 Pass 2
9.1 fps (4%)
6.3 fps (3%)
8.7 fps (4%)
X264 HD Benchmark 4.0 - x264 Pass 1
48.9 fps (13%)
35.7 fps (10%)
46.5 fps (13%)
TrueCrypt - TrueCrypt Serpent
0.1 GB/s (4%)
0.1 GB/s (3%)
0.1 GB/s (4%)
TrueCrypt - TrueCrypt Twofish
0.2 GB/s (4%)
0.1 GB/s (3%)
0.2 GB/s (4%)
TrueCrypt - TrueCrypt AES
1 GB/s (4%)
0.7 GB/s (3%)
1 GB/s (4%)
3DMark 06 - CPU - 3DMark 06 - CPU
2132 Points (5%)
1556 Points (3%)
2253 Points (5%)
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
20.2 s (4%)
26.9 s (6%)
20.9 s (5%)
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
45.5 s (2%)
59.8 s (3%)
46.9 s (2%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
968 s (4%)
1304 s (6%)
1022 s (5%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
100%
1 E2-9000 +
3146 Points (3%)
135%
1 A6-9220 +
4236 Points (4%)
3DMark 11 - 3DM11 Performance Physics
1568 Points (5%)
1199 Points (4%)
min: 1467     avg: 1470     median: 1469.5 (5%)     max: 1472 Points
3DMark - 3DMark Ice Storm Physics
16446 Points (11%)
11949 Points (8%)
16010 Points (10%)
3DMark - 3DMark Ice Storm Extreme Physics
15678 Points (13%)
10209 Points (8%)
15125 Points (13%)
3DMark - 3DMark Ice Storm Unlimited Physics
16322 Points (14%)
11528 Points (10%)
15704 Points (13%)
3DMark - 3DMark Cloud Gate Physics
1304 Points (3%)
914 Points (2%)
1241 Points (3%)
3DMark - 3DMark Fire Strike Standard Physics
1821 Points (4%)
1255 Points (3%)
1721 Points (4%)
3DMark - 3DMark Time Spy CPU
100%
1 A6-9225 +
664 Points (4%)
634 Points (3%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Single-Core
1980 Points (23%)
1591 Points (18%)
1960 Points (23%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Multi-Core
3190 Points (4%)
2461 Points (3%)
2857 Points (4%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Single-Core
1920 Points (30%)
1543 Points (24%)
1885 Points (29%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Multi-Core
3035 Points (7%)
2371 Points (6%)
2805 Points (7%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
3103 Points (6%)
2323 Points (4%)
2921 Points (5%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
1855 Points (36%)
1430 Points (28%)
1798 Points (35%)
Geekbench 3 - Geekbench 3 64 Bit Multi-Core
3323 Points (5%)
2439 Points (4%)
3115 Points (5%)
Geekbench 3 - Geekbench 3 64 Bit Single-Core
1974 Points (32%)
1526 Points (25%)
1909 Points (31%)
Geekbench 2 - 32 Bit - Geekbench Stream
3899 Points (31%)
2993 Points (24%)
3245 Points (26%)
Geekbench 2 - 32 Bit - Geekbench Memory
2849 Points (26%)
2893 Points (26%)
2855 Points (26%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
4490 Points (9%)
2847 Points (6%)
3510 Points (7%)
Geekbench 2 - 32 Bit - Geekbench Integer
4014 Points (8%)
2914 Points (6%)
3822 Points (8%)
Geekbench 2 - 32 Bit - Geekbench Total Score
3936 Points (10%)
2894 Points (8%)
3461 Points (9%)
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
2657 ms (3%)
3175 ms (4%)
2416 ms (3%)
Sunspider - Sunspider 1.0 Total Score *
203.6 ms (2%)
258.9 ms (3%)
162.1 ms (2%)
Octane V2 - Octane V2 Total Score
11962 Points (12%)
10575 Points (11%)
14724 Points (15%)
WebXPRT 3 - WebXPRT 3 Score
100%
1 A6-9225 +
81 Points (21%)

Average Benchmarks AMD A6-9225 → 100% n=40

Average Benchmarks AMD E2-9000 → 79% n=40

Average Benchmarks AMD A6-9220 → 97% n=40

- 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 17. 03:48:57

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

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

#2 checking url part for id 9326 +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 Tue, 16 Aug 2022 13:13:41 +0200 +0s ... 0s

#5 linkCache_getLink no uid found +0.008s ... 0.009s

#6 linkCache_getLink no uid found +0.004s ... 0.013s

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

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

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

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

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

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

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

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

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

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

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

#18 linkCache_getLink no uid found +0.002s ... 0.015s

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

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

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

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

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

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

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

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

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

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

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

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

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

#32 composed specs +0s ... 0.015s

#33 did output specs +0s ... 0.015s

#34 getting avg benchmarks for device 11281 +0s ... 0.016s

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

#36 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.016s

#37 got single benchmarks 11281 +0.008s ... 0.024s

#38 getting avg benchmarks for device 9294 +0.001s ... 0.025s

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

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

#41 got single benchmarks 9294 +0.008s ... 0.033s

#42 getting avg benchmarks for device 9326 +0s ... 0.033s

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

#44 got single benchmarks 9326 +0.008s ... 0.042s

#45 got avg benchmarks for devices +0s ... 0.042s

#46 linkCache_getLink no uid found +0s ... 0.042s

#47 linkCache_getLink no uid found +0s ... 0.043s

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

#49 linkCache_getLink no uid found +0s ... 0.043s

#50 linkCache_getLink no uid found +0.015s ... 0.058s

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

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

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

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

#55 linkCache_getLink no uid found +0s ... 0.06s

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

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

#58 linkCache_getLink no uid found +0s ... 0.061s

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

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

#61 linkCache_getLink no uid found +0s ... 0.062s

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

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

#64 linkCache_getLink no uid found +0s ... 0.063s

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

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

#67 linkCache_getLink no uid found +0s ... 0.065s

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

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

#70 linkCache_getLink no uid found +0s ... 0.066s

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

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

#73 linkCache_getLink no uid found +0s ... 0.067s

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

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

#76 linkCache_getLink no uid found +0s ... 0.068s

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

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

#79 linkCache_getLink no uid found +0s ... 0.069s

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

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

#82 linkCache_getLink no uid found +0s ... 0.07s

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

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

#85 linkCache_getLink no uid found +0s ... 0.071s

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

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

#88 linkCache_getLink no uid found +0s ... 0.072s

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

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

#91 linkCache_getLink no uid found +0s ... 0.074s

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

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

#94 linkCache_getLink no uid found +0s ... 0.075s

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

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

#97 linkCache_getLink no uid found +0s ... 0.076s

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

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

#100 linkCache_getLink no uid found +0s ... 0.077s

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

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

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

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

#105 linkCache_getLink no uid found +0s ... 0.079s

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

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

#108 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.08s

#109 linkCache_getLink no uid found +0s ... 0.08s

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

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

#112 linkCache_getLink no uid found +0s ... 0.081s

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

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

#115 linkCache_getLink no uid found +0s ... 0.082s

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

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

#118 linkCache_getLink no uid found +0s ... 0.083s

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

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

#121 linkCache_getLink no uid found +0s ... 0.084s

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

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

#124 linkCache_getLink no uid found +0s ... 0.086s

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

#126 linkCache_getLink no uid found +0.001s ... 0.087s

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

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

#129 linkCache_getLink no uid found +0s ... 0.088s

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

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

#132 linkCache_getLink no uid found +0s ... 0.089s

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

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

#135 linkCache_getLink no uid found +0s ... 0.09s

#136 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.09s

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

#138 linkCache_getLink no uid found +0s ... 0.091s

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

#140 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.091s

#141 linkCache_getLink no uid found +0s ... 0.092s

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

#143 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.092s

#144 linkCache_getLink no uid found +0s ... 0.093s

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

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

#147 linkCache_getLink no uid found +0s ... 0.094s

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

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

#150 linkCache_getLink no uid found +0s ... 0.095s

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

#152 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.095s

#153 linkCache_getLink no uid found +0s ... 0.096s

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

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

#156 linkCache_getLink no uid found +0s ... 0.097s

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

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

#159 linkCache_getLink no uid found +0s ... 0.098s

#160 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.098s

#161 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.098s

#162 linkCache_getLink no uid found +0s ... 0.099s

#163 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.099s

#164 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.099s

#165 linkCache_getLink no uid found +0s ... 0.1s

#166 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.1s

#167 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.101s

#168 linkCache_getLink no uid found +0.001s ... 0.101s

#169 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.101s

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

#171 linkCache_getLink no uid found +0s ... 0.102s

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

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

#174 linkCache_getLink no uid found +0s ... 0.103s

#175 min, max, avg, median took s +0s ... 0.104s

#176 return log +0s ... 0.104s

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