Notebookcheck Logo

AMD A6-9225 vs AMD E2-9000 vs AMD A9-9410

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 A9-9410

► remove from comparison AMD A9-9410

The AMD A9-9410 is an entry-level chip from the Stoney-Ridge APU series for notebooks (7th APU generation), which was announced mid 2016. At its launch, the A9-9410 is the fastest 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.9-3.5 GHz. It also includes a Radeon R5 GPU with 192 shaders at 800 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

Thanks to the high maximum clock of up to 3.5 GHz, the single-core performance should be pretty good. The multi-core performance on the other hand is much lower compared to the Bristol Ridge models. Compared to older Carrizo-L/Beema quad-cores, the APU should still perform pretty well. The level of performance should be similar to a Core-m3 and therefore also be sufficient for more demanding applications.

The TDP can be configured between 10-25 Watts, so there can be big performance differences under sustained workloads.

Graphics Card

The integrated Radeon R5 (Stoney Ridge) GPU has 192 active shader units (3 compute cores) clocked at up to 800 MHz. More details about the GPU are available in the linked articles above. 

Power Consumption

AMD specifies the TDP of the A9-9410 with 15 Watts, but it can be configured between 10-25 Watts. This means the CPU is a good choice for thin and light notebooks, but also 15-inch devices with better cooling capabilities.

ModelAMD A6-9225AMD E2-9000AMD A9-9410
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 MHz2900 - 3500 MHz
L1 Cache160 KB
L2 Cache1 MB1 MB1 MB
Cores / Threads2 / 22 / 22 / 2
TDP10-15 Watt10 Watt10-25 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 R5 (Stoney Ridge) ( - 800 MHz)
Architecturex86x86x86
Announced
ManufacturerAMD Bristol Ridge A6-9225AMD Bristol Ridge E2-9000AMD Bristol Ridge A9-9410

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
130 Points (1%)
0102030405060708090100110120130Tooltip
Cinebench R15 - Cinebench R15 CPU Single 64 Bit
73 Points (25%)
47 Points (16%)
63 Points (22%)
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.6 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%)
2694 Points (24%)
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
4193 Points (6%)
2897 Points (4%)
4619 Points (6%)
wPrime 2.10 - wPrime 2.0 1024m *
852 s (10%)
1242 s (15%)
751 s (9%)
wPrime 2.10 - wPrime 2.0 32m *
26.3 s (5%)
36.2 s (7%)
24 s (5%)
WinRAR - WinRAR 4.0
852 Points (5%)
744 Points (4%)
879 Points (5%)
X264 HD Benchmark 4.0 - x264 Pass 2
9.1 fps (4%)
6.3 fps (3%)
10.1 fps (5%)
X264 HD Benchmark 4.0 - x264 Pass 1
48.9 fps (13%)
35.7 fps (10%)
53.5 fps (15%)
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%)
2455 Points (5%)
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
20.2 s (4%)
26.9 s (6%)
17.8 s (4%)
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
45.5 s (2%)
59.8 s (3%)
39.8 s (2%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
968 s (4%)
1304 s (6%)
878 s (4%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
100%
1 E2-9000 +
3146 Points (3%)
151%
1 A9-9410 +
4764 Points (5%)
3DMark 11 - 3DM11 Performance Physics
1568 Points (5%)
1199 Points (4%)
1470 Points (5%)
3DMark - 3DMark Ice Storm Physics
16446 Points (11%)
11949 Points (8%)
17953 Points (12%)
3DMark - 3DMark Ice Storm Extreme Physics
15678 Points (13%)
10209 Points (8%)
17279 Points (14%)
3DMark - 3DMark Ice Storm Unlimited Physics
16322 Points (14%)
11528 Points (10%)
17768 Points (15%)
3DMark - 3DMark Cloud Gate Physics
1304 Points (3%)
914 Points (2%)
1318 Points (3%)
3DMark - 3DMark Fire Strike Standard Physics
1821 Points (4%)
1255 Points (3%)
2054 Points (5%)
3DMark - 3DMark Time Spy CPU
100%
1 A6-9225 +
664 Points (4%)
110%
1 A9-9410 +
732 Points (4%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Single-Core
100%
1 A6-9225 +
1980 Points (23%)
1591 Points (18%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Multi-Core
100%
1 A6-9225 +
3190 Points (4%)
2461 Points (3%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Single-Core
1920 Points (30%)
1543 Points (24%)
2133 Points (33%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Multi-Core
3035 Points (7%)
2371 Points (6%)
3182 Points (8%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
3103 Points (6%)
2323 Points (4%)
3299 Points (6%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
1855 Points (36%)
1430 Points (28%)
2134 Points (42%)
Geekbench 3 - Geekbench 3 64 Bit Multi-Core
3323 Points (5%)
2439 Points (4%)
3516 Points (6%)
Geekbench 3 - Geekbench 3 64 Bit Single-Core
1974 Points (32%)
1526 Points (25%)
2255 Points (37%)
Geekbench 2 - 32 Bit - Geekbench Stream
3899 Points (31%)
2993 Points (24%)
3482 Points (28%)
Geekbench 2 - 32 Bit - Geekbench Memory
2849 Points (26%)
2893 Points (26%)
3458 Points (31%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
4490 Points (9%)
2847 Points (6%)
4828 Points (9%)
Geekbench 2 - 32 Bit - Geekbench Integer
4014 Points (8%)
2914 Points (6%)
4375 Points (9%)
Geekbench 2 - 32 Bit - Geekbench Total Score
3936 Points (10%)
2894 Points (8%)
4260 Points (11%)
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
2657 ms (3%)
3175 ms (4%)
2081 ms (2%)
Sunspider - Sunspider 1.0 Total Score *
203.6 ms (2%)
258.9 ms (3%)
147.7 ms (2%)
Octane V2 - Octane V2 Total Score
11962 Points (12%)
10575 Points (11%)
17423 Points (18%)
WebXPRT 3 - WebXPRT 3 Score
100%
1 A6-9225 +
81 Points (21%)

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

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

Average Benchmarks AMD A9-9410 → 107% n=38

- 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. 02:57:09

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

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

#2 checking url part for id 8181 +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 +0.001s ... 0.001s

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

#6 linkCache_getLink no uid found +0.005s ... 0.015s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#31 composed specs +0s ... 0.018s

#32 did output specs +0s ... 0.018s

#33 getting avg benchmarks for device 11281 +0.001s ... 0.019s

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

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

#36 got single benchmarks 11281 +0.008s ... 0.028s

#37 getting avg benchmarks for device 9294 +0.001s ... 0.028s

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

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

#40 got single benchmarks 9294 +0.009s ... 0.037s

#41 getting avg benchmarks for device 8181 +0.001s ... 0.038s

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

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

#44 got single benchmarks 8181 +0.009s ... 0.047s

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

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

#47 linkCache_getLink no uid found +0.001s ... 0.048s

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

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

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

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

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

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

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

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

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

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

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

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

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

#61 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.068s

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

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

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

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

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

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

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

#69 linkCache_getLink no uid found +0.001s ... 0.072s

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

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

#72 linkCache_getLink no uid found +0s ... 0.073s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#87 linkCache_getLink no uid found +0s ... 0.078s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#104 linkCache_getLink no uid found +0s ... 0.085s

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

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

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

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

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

#110 linkCache_getLink no uid found +0s ... 0.087s

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

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

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

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

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

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

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

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

#119 linkCache_getLink no uid found +0.001s ... 0.091s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#146 linkCache_getLink no uid found +0s ... 0.101s

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

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

#149 linkCache_getLink no uid found +0.001s ... 0.102s

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

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

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

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

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

#155 linkCache_getLink no uid found +0s ... 0.104s

#156 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.104s

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

#158 linkCache_getLink no uid found +0s ... 0.105s

#159 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.105s

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

#161 linkCache_getLink no uid found +0s ... 0.106s

#162 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.106s

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

#164 linkCache_getLink no uid found +0.001s ... 0.107s

#165 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.107s

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

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

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

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

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

#171 min, max, avg, median took s +0.001s ... 0.11s

#172 return log +0s ... 0.11s

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)