Notebookcheck Logo

AMD A6-9220e vs AMD E2-9010 vs AMD A6-9225

AMD A6-9220e

► remove from comparison AMD A6-9220e

The AMD A6-9220e is an entry-level chip from the Stoney-Ridge APU series for notebooks (7th APU generation), which was announced mid 2017. The 9220e is an entry-level 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 1.6 - 2.4 GHz. It also includes a Radeon R4 GPU, probably with 192 shaders at 600 MHz, as well as a single-channel DDR4-2133 memory controller, H.265 video engine and chipset with all I/O ports. Compared to the similar named A6-9220 the 9220e is significantly slower clocked (2.5 - 2.9 GHz) including the GPU (600 versus 655 MHz) and can be passively cooled thanks to the TDP of 6W.

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 speed, the A6-9220e is noticeably slower than the A6-9220. In the Cinebench R15 Multi benchmark the 9220 reaches 38% higher scores, in the single thread test its more than twice as fast (219% versus the 9220 in the HP 255 G6). Compared to Intel CPUs, the A6-9220e is on par with the old Celeron N2820 in Cinebench (single and multi core). Therefore, the CPU is placed in the lowest segment (performance wise) and only suited for light tasks and light multitasking.

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-9220e with 6 Watts and therefore significantly below the 15 W of the A6-9220. This means the APU can be passively cooled and is a good choice for thin and light notebooks.

AMD E2-9010

► remove from comparison AMD E2-9010

The AMD E2-9010 is the least powerful chip from the Stoney-Ridge APU series for notebooks (7th APU generation) at the time of announcement in mid 2016. The SoC integrates two CPU cores (one Excavator module with 2 integer and on FP unit) clocked between 2.0-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.

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-9010 with 15 Watts, but it can be configured between 10-15 Watts. This means the APU is intended for thin and light notebooks.

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.

ModelAMD A6-9220eAMD E2-9010AMD A6-9225
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
Clock1600 - 2400 MHz2000 - 2200 MHz2600 - 3100 MHz
L1 Cache160 KB160 KB
L2 Cache1 MB1 MB1 MB
Cores / Threads2 / 22 / 22 / 2
TDP6 Watt10-15 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-2133, Virtualization,Single-Channel DDR4-2133, Virtualization,
iGPUAMD Radeon R4 (Stoney Ridge) ( - 600 MHz)AMD Radeon R2 (Stoney Ridge) ( - 600 MHz)AMD Radeon R4 (Stoney Ridge) ( - 686 MHz)
Architecturex86x86x86
Announced
ManufacturerAMD Bristol Ridge E2-9010AMD Bristol Ridge A6-9225

Benchmarks

Cinebench R20 - Cinebench R20 CPU (Single Core)
73 Points (9%)
249%
1 A6-9225 +
182 Points (23%)
Cinebench R20 - Cinebench R20 CPU (Multi Core)
110 Points (0%)
248%
1 A6-9225 +
273 Points (1%)
Cinebench R15 - Cinebench R15 CPU Multi 64 Bit
86 Points (1%)
0510152025303540455055606570758085Tooltip
91 Points (1%)
051015202530354045505560657075808590Tooltip
min: 96     avg: 108.5     median: 108.5 (1%)     max: 121 Points
Cinebench R15 - Cinebench R15 CPU Single 64 Bit
31 Points (11%)
53 Points (18%)
73 Points (25%)
Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
100%
1 E2-9010 +
1.1 Points (2%)
109%
1 A6-9225 +
min: 1.03     avg: 1.2     median: 1.2 (2%)     max: 1.44 Points
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
100%
1 E2-9010 +
0.6 Points (2%)
133%
1 A6-9225 +
0.9 Points (3%)
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
1056 Points (9%)
1871 Points (17%)
2532 Points (23%)
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
1741 Points (2%)
3268 Points (4%)
4193 Points (6%)
wPrime 2.10 - wPrime 2.0 1024m *
1517 s (18%)
1142 s (13%)
852 s (10%)
wPrime 2.10 - wPrime 2.0 32m *
35.2 s (7%)
37.1 s (7%)
26.3 s (5%)
WinRAR - WinRAR 4.0
519 Points (3%)
769 Points (4%)
852 Points (5%)
X264 HD Benchmark 4.0 - x264 Pass 2
2.7 fps (1%)
7.4 fps (3%)
9.1 fps (4%)
X264 HD Benchmark 4.0 - x264 Pass 1
14.7 fps (4%)
39.2 fps (11%)
48.9 fps (13%)
TrueCrypt - TrueCrypt Serpent
0 GB/s (2%)
0.1 GB/s (3%)
0.1 GB/s (4%)
TrueCrypt - TrueCrypt Twofish
0.1 GB/s (2%)
0.1 GB/s (3%)
0.2 GB/s (4%)
TrueCrypt - TrueCrypt AES
0.3 GB/s (1%)
0.7 GB/s (3%)
1 GB/s (4%)
3DMark 06 - CPU - 3DMark 06 - CPU
100%
1 A6-9225 +
2132 Points (5%)
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
66.4 s (14%)
27.9 s (6%)
20.2 s (4%)
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
113.1 s (5%)
61.5 s (3%)
45.5 s (2%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
2732 s (12%)
1296 s (6%)
968 s (4%)
3DMark 11 - 3DM11 Performance Physics
529 Points (2%)
1241 Points (4%)
1568 Points (5%)
3DMark - 3DMark Ice Storm Physics
4502 Points (3%)
365%
1 A6-9225 +
16446 Points (11%)
3DMark - 3DMark Ice Storm Extreme Physics
4404 Points (4%)
356%
1 A6-9225 +
15678 Points (13%)
3DMark - 3DMark Ice Storm Unlimited Physics
5273 Points (4%)
12726 Points (11%)
16322 Points (14%)
3DMark - 3DMark Cloud Gate Physics
444 Points (1%)
919 Points (2%)
1304 Points (3%)
3DMark - 3DMark Fire Strike Standard Physics
376 Points (1%)
1268 Points (3%)
1821 Points (4%)
3DMark - 3DMark Time Spy CPU
100%
1 A6-9225 +
664 Points (4%)
Geekbench 5.0 - Geekbench 5.0 64 Bit Single-Core
260 Points (13%)
Geekbench 5.0 - Geekbench 5.0 64 Bit Multi-Core
293 Points (1%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Single-Core
1260 Points (15%)
1610 Points (19%)
1980 Points (23%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Multi-Core
1571 Points (2%)
2402 Points (3%)
3190 Points (4%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Single-Core
1112 Points (17%)
1512 Points (23%)
1920 Points (30%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Multi-Core
1513 Points (4%)
2307 Points (6%)
3035 Points (7%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
1929 Points (3%)
2348 Points (4%)
3103 Points (6%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
1247 Points (24%)
1415 Points (28%)
1855 Points (36%)
Geekbench 3 - Geekbench 3 64 Bit Multi-Core
2003 Points (3%)
2484 Points (4%)
3323 Points (5%)
Geekbench 3 - Geekbench 3 64 Bit Single-Core
1329 Points (22%)
1516 Points (25%)
1974 Points (32%)
Geekbench 2 - 32 Bit - Geekbench Stream
3297 Points (27%)
3104 Points (25%)
3899 Points (31%)
Geekbench 2 - 32 Bit - Geekbench Memory
2796 Points (25%)
2675 Points (24%)
2849 Points (26%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
3496 Points (7%)
3377 Points (7%)
4490 Points (9%)
Geekbench 2 - 32 Bit - Geekbench Integer
3085 Points (6%)
2957 Points (6%)
4014 Points (8%)
Geekbench 2 - 32 Bit - Geekbench Total Score
3192 Points (8%)
3062 Points (8%)
3936 Points (10%)
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
4105 ms (5%)
3043 ms (4%)
2657 ms (3%)
Sunspider - Sunspider 1.0 Total Score *
357.7 ms (4%)
234.5 ms (3%)
203.6 ms (2%)
Octane V2 - Octane V2 Total Score
9070 Points (9%)
10419 Points (11%)
11962 Points (12%)
WebXPRT 3 - WebXPRT 3 Score
64 Points (17%)
127%
1 A6-9225 +
81 Points (21%)

Average Benchmarks AMD A6-9220e → 100% n=35

Average Benchmarks AMD E2-9010 → 152% n=35

Average Benchmarks AMD A6-9225 → 192% n=35

- 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 10. 00:49:06

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

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

#2 checking url part for id 11281 +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 Sat, 06 Aug 2022 13:13:32 +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.016s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#37 got single benchmarks 11876 +0.007s ... 0.023s

#38 getting avg benchmarks for device 8183 +0s ... 0.024s

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

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

#41 got single benchmarks 8183 +0.007s ... 0.031s

#42 getting avg benchmarks for device 11281 +0s ... 0.031s

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

#44 got single benchmarks 11281 +0.008s ... 0.039s

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

#46 linkCache_getLink no uid found +0.001s ... 0.04s

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

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

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

#50 linkCache_getLink no uid found +0.005s ... 0.045s

#51 linkCache_getLink no uid found +0.004s ... 0.049s

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

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

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

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

#56 linkCache_getLink no uid found +0s ... 0.051s

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

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

#59 linkCache_getLink no uid found +0s ... 0.052s

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

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

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

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

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

#65 linkCache_getLink no uid found +0s ... 0.054s

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

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

#68 linkCache_getLink no uid found +0s ... 0.055s

#69 linkCache_getLink no uid found +0s ... 0.055s

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

#71 linkCache_getLink no uid found +0s ... 0.056s

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

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

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

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

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

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

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

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

#80 linkCache_getLink no uid found +0s ... 0.059s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#162 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.088s

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

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

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

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

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

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

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

#170 min, max, avg, median took s +0s ... 0.091s

#171 return log +0s ... 0.091s

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)