Notebookcheck Logo

AMD A12-9700P vs AMD A12-9720P vs AMD FX-9800P

AMD A12-9700P

► remove from comparison AMD A12-9700P

The AMD A12-9700P is a mainstream SoC from the Bristol-Ridge APU series for notebooks (7th APU generation), which was announced mid 2016. The ULV chip with a TDP of 15 Watts (can be configured to 12 Watts) has four CPU cores (two Excavator modules), a Radeon R7 GPU as well as a dual-channel DDR4-1866 memory controller. Carrizo is a full-fledged SoC and is also equipped with an integrated chipset, which provides all I/0 ports.

Architecture

Bristol 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. More technical details are available in the following articles:

Performance

The performance of the A12-9700P is between the two 15-Watt processors A10-9600P and FX-9800P, and therefore roughly on par with a 15-Watt Core i3 from the Skylake or Kaby Lake series, respectively. Compared to the Intel model, the AMD chip has a small advantage in multi-thread scenarios, but is beaten when you only stress one or two cores. Due to the TDP limitation, the performance of the A12-9700P will drop significantly under sustained workloads.

This means there is sufficient performance for typical office and web applications as well as light multitasking.

Graphics Card

The integrated Radeon R7 (Bristol Ridge) GPU has 512 active shader units (8 compute cores) clocked at up to 758 MHz. Thanks to the better utilization of the clock range as well as faster DDR4-RAm, the GPU can slightly beat its predecessors Radeon R7 (Carrizo) and competes with a dedicated GeForce 920MX in the best-case scenario (dual-channel memory, low CPU requirements). Many games from 2015/2016 can be played smoothly at low settings. 

Power Consumption

AMD specifies the TDP of the A12-9700P with 15 Watts, which is comparable to Intel's ULV models. This means the CPU is a good choice for thin notebooks starting with a 12-inch screen.

AMD A12-9720P

► remove from comparison AMD A12-9720P

The AMD A12-9720P is a mainstream SoC from the Bristol Ridge APU series for notebooks (7th APU generation), which was introduced in 2017. The ULV chip with a TDP of 15 Watts (can be configured to 12 Watts, not verified) has four CPU cores (two Excavator modules) clocked at 2.7 - 3.8 GHz (4.05 GHz for single core were briefly achievable in our test sample), a Radeon R7 iGPU as well as a dual-channel DDR4-1866 memory controller. Carrizo is a full-fledged SoC and is also equipped with an integrated chipset, which provides all I/0 ports.

Architecture

Bristol 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. More technical details are available in the following articles:

Performance

The performance of the A12-9720P should be slightly faster than the A12-9700P (the latter is notable for its slightly slower clock rates). Compared to Intel CPUs, the CPU is most comparable to Skylake Core i3 CPUs. Our first test sample however performed a bit worse than an average A12-9700P and on par with a i3-5010U (multi-core) and i3-4010U (single-core). Due to the TDP limitation, the performance of the A12-9720P will drop significantly under sustained workloads.

This means there is sufficient performance for typical office and web applications as well as light multitasking.

Graphics

The integrated Radeon R7 (Bristol Ridge) GPU has 512 active shader units (8 compute cores) clocked at up to 758 MHz. Thanks to the better utilization of the clock range as well as faster DDR4-RAM, the GPU can slightly beat its predecessors Radeon R7 (Carrizo) and competes with a dedicated GeForce 920MX in the best-case scenario (dual-channel memory, low CPU requirements). Many games from 2015/2016 can be played smoothly at low settings.

Power Consumption

AMD specifies the TDP of the A12-9720P with 15 Watts, which is comparable to Intel's ULV models. This means the CPU is a good choice for thin notebooks starting with a 12-inch screen.

AMD FX-9800P

► remove from comparison AMD FX-9800P

The AMD FX-9800P is a mobile mainstream SoC from the Bristol-Ridge APU series for notebooks (7th APU generation), which was announced mid 2016. The FX-9800P is the fastest Bristol Ridge APU with a 15-Watt TDP and the successor to the 15-Watt FX-8800P from the Carrizo generation. The ULV chip has four CPU cores (two Excavator modules = 4 integer and 2 FP units), a Radeon R7 GPU as well as a dual-channel DDR4-1866 memory controller. Carrizo is a full-fledged SoC and is also equipped with an integrated chipset, which provides all I/0 ports.

Architecture

Bristol 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. More technical details are available in the following articles:

Performance

Thanks to higher clocks, the FX9800P is slightly ahead of the old 15-Watt top model FX-8800P and competes with a Intel Core i3-6100U (Skylake, 15 Watts). Compared to the Intel model, the AMD chip has a small advantage in multi-thread scenarios, but is beaten when you only stress one or two cores.

This means there is sufficient performance for typical office and web applications as well as light multitasking.

Graphics Card

The integrated Radeon R7 (Bristol Ridge) GPU has 512 active shader units (8 compute cores) clocked at up to 758 MHz. Thanks to the better utilization of the clock range as well as faster DDR4-RAm, the GPU can slightly beat its predecessors Radeon R7 (Carrizo) and competes with a dedicated GeForce 920MX in the best-case scenario (dual-channel memory, low CPU requirements). Many games from 2015/2016 can be played smoothly at low settings. 

Power Consumption

AMD specifies the TDP of the FX-9800P with 12-15 Watts, which is comparable to Intel's ULV models. This means the APU is a good choice for thin notebooks starting with a 12-inch screen.

ModelAMD A12-9700PAMD A12-9720PAMD FX-9800P
SeriesAMD Bristol RidgeAMD Bristol RidgeAMD Bristol Ridge
CodenameBristol RidgeBristol RidgeBristol Ridge
Series: Bristol Ridge Bristol Ridge
AMD FX-9830P3 - 3.7 GHz4 / 4
AMD PRO A12-9830B3 - 3.7 GHz4 / 4
AMD FX-9800P2.7 - 3.6 GHz4 / 4
AMD PRO A12-9800B2.7 - 3.6 GHz4 / 4
AMD A12-9720P2.7 - 3.6 GHz4 / 4
» AMD A12-9700P2.5 - 3.4 GHz4 / 4
AMD A10-9620P2.5 - 3.4 GHz4 / 4
AMD A10-9600P2.4 - 3.3 GHz4 / 4
AMD PRO A8-9600B2.4 - 3.3 GHz4 / 4
AMD FX-9830P3 - 3.7 GHz4 / 4
AMD PRO A12-9830B3 - 3.7 GHz4 / 4
AMD FX-9800P2.7 - 3.6 GHz4 / 4
AMD PRO A12-9800B2.7 - 3.6 GHz4 / 4
» AMD A12-9720P2.7 - 3.6 GHz4 / 4
AMD A12-9700P2.5 - 3.4 GHz4 / 4
AMD A10-9620P2.5 - 3.4 GHz4 / 4
AMD A10-9600P2.4 - 3.3 GHz4 / 4
AMD PRO A8-9600B2.4 - 3.3 GHz4 / 4
AMD FX-9830P3 - 3.7 GHz4 / 4
AMD PRO A12-9830B3 - 3.7 GHz4 / 4
» AMD FX-9800P2.7 - 3.6 GHz4 / 4
AMD PRO A12-9800B2.7 - 3.6 GHz4 / 4
AMD A12-9720P2.7 - 3.6 GHz4 / 4
AMD A12-9700P2.5 - 3.4 GHz4 / 4
AMD A10-9620P2.5 - 3.4 GHz4 / 4
AMD A10-9600P2.4 - 3.3 GHz4 / 4
AMD PRO A8-9600B2.4 - 3.3 GHz4 / 4
Clock2500 - 3400 MHz2700 - 3600 MHz2700 - 3600 MHz
L2 Cache2 MB2 MB2 MB
Cores / Threads4 / 44 / 44 / 4
TDP15 Watt15 Watt15 Watt
Transistors3100 Million3100 Million3100 Million
Technology28 nm28 nm28 nm
Die Size250 mm2250 mm2250 mm2
max. Temp.90 °C90 °C90 °C
SocketFP4FP4
FeaturesDual-Channel DDR3/DDR4-1866 Memory Controller, PCIe 3.0 x8Dual-Channel DDR3/DDR4-1866 Memory Controller, PCIe 3.0 x8Dual-Channel DDR3/DDR4-1866 Memory Controller, PCIe 3.0 x8
iGPUAMD Radeon R7 (Bristol Ridge) ( - 758 MHz)AMD Radeon R7 (Bristol Ridge) ( - 758 MHz)AMD Radeon R7 (Bristol Ridge) ( - 758 MHz)
Architecturex86x86x86
Announced
ManufacturerAMD Bristol Ridge A12-9700PAMD Bristol Ridge FX-9800P

Benchmarks

Cinebench R15 - Cinebench R15 CPU Multi 64 Bit
min: 222     avg: 225.5     median: 225.5 (2%)     max: 229 Points
min: 229     avg: 234.5     median: 234.5 (2%)     max: 240 Points
0153045607590105120135150165180195210225Tooltip
236 Points (2%)
Cinebench R15 - Cinebench R15 CPU Single 64 Bit
min: 78     avg: 79     median: 79 (27%)     max: 80 Points
min: 69     avg: 72.5     median: 72.5 (25%)     max: 76 Points
74 Points (25%)
Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
min: 1.92     avg: 2.3     median: 2.3 (4%)     max: 2.62 Points
min: 2.6     avg: 2.7     median: 2.7 (5%)     max: 2.7 Points
2.9 Points (5%)
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
min: 0.76     avg: 0.9     median: 0.9 (3%)     max: 0.94 Points
min: 0.93     avg: 0.9     median: 0.9 (3%)     max: 0.94 Points
0.9 Points (3%)
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
min: 2262     avg: 2429     median: 2429 (22%)     max: 2596 Points
min: 2640     avg: 2743     median: 2743 (24%)     max: 2846 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
min: 5148     avg: 6168     median: 6168 (8%)     max: 7188 Points
min: 7200     avg: 7361     median: 7361 (10%)     max: 7522 Points
wPrime 2.10 - wPrime 2.0 1024m *
415.5 s (5%)
wPrime 2.10 - wPrime 2.0 32m *
13 s (3%)
14.4 s (3%)
WinRAR - WinRAR 4.0
1462 Points (8%)
X264 HD Benchmark 4.0 - x264 Pass 2
16.7 fps (8%)
X264 HD Benchmark 4.0 - x264 Pass 1
84.6 fps (23%)
TrueCrypt - TrueCrypt Serpent
0.2 GB/s (8%)
0.2 GB/s (8%)
TrueCrypt - TrueCrypt Twofish
0.4 GB/s (7%)
0.4 GB/s (8%)
TrueCrypt - TrueCrypt AES
1.8 GB/s (7%)
1.8 GB/s (7%)
3DMark 06 - CPU - 3DMark 06 - CPU
min: 3344     avg: 3498     median: 3498 (7%)     max: 3652 Points
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
19.2 s (4%)
min: 17.77     avg: 19.6     median: 19.6 (4%)     max: 21.4 s
33 s (7%)
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
42.1 s (2%)
min: 39.77     avg: 44.1     median: 44.1 (2%)     max: 48.5 s
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
980 s (4%)
min: 864     avg: 902     median: 901.5 (4%)     max: 939 s
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
7608 Points (8%)
3DMark 11 - 3DM11 Performance Physics
min: 2524     avg: 2527     median: 2527 (9%)     max: 2530 Points
2761 Points (10%)
2393 Points (8%)
3DMark - 3DMark Ice Storm Physics
25886 Points (17%)
25648 Points (16%)
3DMark - 3DMark Ice Storm Extreme Physics
25743 Points (21%)
24747 Points (20%)
3DMark - 3DMark Ice Storm Unlimited Physics
27373 Points (23%)
min: 24457     avg: 27079     median: 27079 (23%)     max: 29701 Points
3DMark - 3DMark Cloud Gate Physics
min: 2283     avg: 2306     median: 2306 (6%)     max: 2329 Points
min: 2258     avg: 2330     median: 2329.5 (6%)     max: 2401 Points
3DMark - 3DMark Fire Strike Standard Physics
min: 2981     avg: 3125     median: 3124.5 (8%)     max: 3268 Points
min: 3179     avg: 3265     median: 3264.5 (8%)     max: 3350 Points
3DMark - 3DMark Time Spy CPU
1069 Points (6%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Single-Core
2158 Points (33%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Multi-Core
4899 Points (12%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
min: 5371     avg: 5464     median: 5464 (10%)     max: 5557 Points
Geekbench 3 - Geekbench 3 32 Bit Single-Core
min: 2062     avg: 2091     median: 2091 (41%)     max: 2120 Points
Geekbench 3 - Geekbench 3 64 Bit Multi-Core
5824 Points (9%)
5496 Points (9%)
Geekbench 3 - Geekbench 3 64 Bit Single-Core
2308 Points (38%)
2057 Points (34%)
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
2059 ms (2%)
2422 ms (3%)
Sunspider - Sunspider 1.0 Total Score *
164.9 ms (2%)
min: 146.6     avg: 192.1     median: 192.1 (2%)     max: 237.6 ms
Octane V2 - Octane V2 Total Score
19404 Points (20%)
min: 14783     avg: 16961     median: 16960.5 (18%)     max: 19138 Points
Power Consumption - Prime95 Power Consumption - external Monitor *
31.9 Watt (6%)
Power Consumption - Cinebench R15 Multi Power Consumption - external Monitor *
33.3 Watt (9%)

Average Benchmarks AMD A12-9700P → 100% n=6

Average Benchmarks AMD A12-9720P → 105% n=6

Average Benchmarks AMD FX-9800P → 104% n=6

- 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 18. 02:59:10

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

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

#2 checking url part for id 8158 +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.006s ... 0.007s

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

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

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

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

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

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

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

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

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

#15 linkCache_getLink no uid found +0.003s ... 0.014s

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

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

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

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

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

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

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

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

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

#25 composed specs +0s ... 0.014s

#26 did output specs +0s ... 0.014s

#27 getting avg benchmarks for device 8166 +0s ... 0.015s

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

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

#30 got single benchmarks 8166 +0.002s ... 0.017s

#31 getting avg benchmarks for device 9192 +0s ... 0.018s

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

#33 got single benchmarks 9192 +0.009s ... 0.027s

#34 getting avg benchmarks for device 8158 +0s ... 0.027s

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

#36 got single benchmarks 8158 +0.001s ... 0.029s

#37 got avg benchmarks for devices +0s ... 0.029s

#38 linkCache_getLink no uid found +0.006s ... 0.035s

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

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

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

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

#43 linkCache_getLink no uid found +0s ... 0.035s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#114 linkCache_getLink no uid found +0s ... 0.046s

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

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

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

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

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

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

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

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

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

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

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

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

#127 min, max, avg, median took s +0s ... 0.048s

#128 return log +0s ... 0.048s

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)