AMD A6-9225 vs Intel Core i5-8265U: What is the difference?
35points
AMD A6-9225
54points
Intel Core i5-8265U
vs
64 facts in comparison
AMD A6-9225
Intel Core i5-8265U
Why is AMD A6-9225 better than Intel Core i5-8265U?
- 0.25MB/core more L2 cache per core?
0.5MB/corevs0.25MB/core - Has FMA4?
Why is Intel Core i5-8265U better than AMD A6-9225?
- 23.08% faster CPU speed?
4 x 1.6GHzvs2 x 2.6GHz - 267MHz higher ram speed?
2400MHzvs2133MHz - 6 more CPU threads?
8vs2 - 10°C higher maximum operating temperature?
100°Cvs90°C - 14nm smaller semiconductor size?
14nmvs28nm - 4.59x higher PassMark result?
6130vs1336 - 0.8GHz higher turbo clock speed?
3.9GHzvs3.1GHz
- 96KB bigger L1 cache?
256KBvs160KB
Which are the most popular comparisons?
AMD A6-9225
vs
Intel Core i3-8130U
Intel Core i5-8265U
vs
AMD A9-9425
AMD A6-9225
vs
Intel Core i3-7020U
Intel Core i5-8265U
vs
AMD Ryzen 5 3500U
AMD A6-9225
vs
Intel Celeron N4020
Intel Core i5-8265U
vs
AMD Ryzen 3 5300U
AMD A6-9225
vs
Intel Core i5-10210U
Intel Core i5-8265U
vs
AMD Ryzen 5 2500U
AMD A6-9225
vs
Intel Core i3-1115G4
Intel Core i5-8265U
vs
Intel Pentium Silver N5030
AMD A6-9225
vs
AMD Ryzen 3 3200U
Intel Core i5-8265U
vs
Intel Core i5-1135G7
AMD A6-9225
vs
AMD Ryzen 5 2500U
Intel Core i5-8265U
vs
Intel Core i3-1115G4
AMD A6-9225
vs
Intel Core i5-8250U
Intel Core i5-8265U
vs
AMD Ryzen 7 2700U
AMD A6-9225
vs
Intel Core i5-6200U
Intel Core i5-8265U
vs
AMD Ryzen 5 5500U
Price comparison
User reviews
Overall Rating
AMD A6-9225
2 User reviews
AMD A6-9225
8.
0/10
2 User reviews
Intel Core i5-8265U
3 User reviews
Intel Core i5-8265U
9.0/10
3 User reviews
Features
Value for money
8.5/10
2 votes
8.3/10
3 votes
Gaming
6.5/10
2 votes
7.3/10
3 votes
Performance
8.0/10
2 votes
9.3/10
3 votes
Reliability
8.0/10
2 votes
9.3/10
3 votes
Energy efficiency
8.0/10
1 votes
8.3/10
3 votes
Performance
1.CPU speed
2 x 2.6GHz
4 x 1.6GHz
The CPU speed indicates how many processing cycles per second can be executed by a CPU, considering all of its cores (processing units). It is calculated by adding the clock rates of each core or, in the case of multi-core processors employing different microarchitectures, of each group of cores.
2.CPU threads
More threads result in faster performance and better multitasking.
3.turbo clock speed
3.1GHz
3.9GHz
When the CPU is running below its limitations, it can boost to a higher clock speed in order to give increased performance.
4.Has an unlocked multiplier
✖AMD A6-9225
✖Intel Core i5-8265U
Some processors come with an unlocked multiplier which makes them easy to overclock, allowing you to gain increased performance in games and other apps.
5.L2 cache
A larger L2 cache results in faster CPU and system-wide performance.
6.L3 cache
Unknown. Help us by suggesting a value. (AMD A6-9225)
A larger L3 cache results in faster CPU and system-wide performance.
7.L1 cache
A larger L1 cache results in faster CPU and system-wide performance.
8.L2 core
0.5MB/core
0.25MB/core
More data can be stored in the L2 cache for access by each core of the CPU.
9.L3 core
Unknown. Help us by suggesting a value. (AMD A6-9225)
1.5MB/core
More data can be stored in the L3 cache for access by each core of the CPU.
Memory
1.RAM speed
2133MHz
2400MHz
It can support faster memory, which will give quicker system performance.
2.maximum memory bandwidth
Unknown. Help us by suggesting a value. (AMD A6-9225)
37.5GB/s
This is the maximum rate that data can be read from or stored into memory.
3.DDR memory version
DDR (Double Data Rate) memory is the most common type of RAM. Newer versions of DDR memory support higher maximum speeds and are more energy-efficient.
4.
memory channels
More memory channels increases the speed of data transfer between the memory and the CPU.
5.maximum memory amount
The maximum amount of memory (RAM) supported.
6.bus transfer rate
Unknown. Help us by suggesting a value. (AMD A6-9225)
The bus is responsible for transferring data between different components of a computer or device.
7.Supports ECC memory
✖AMD A6-9225
✖Intel Core i5-8265U
Error-correcting code memory can detect and correct data corruption. It is used when is it essential to avoid corruption, such as scientific computing or when running a server.
8.eMMC version
Unknown. Help us by suggesting a value. (AMD A6-9225)
Unknown. Help us by suggesting a value. (Intel Core i5-8265U)
A higher version of eMMC allows faster memory interfaces, having a positive effect on the performance of a device.
For example, when transferring files from your computer to the internal storage over USB.
9.bus speed
Unknown. Help us by suggesting a value. (AMD A6-9225)
Unknown. Help us by suggesting a value. (Intel Core i5-8265U)
The bus is responsible for transferring data between different components of a computer or device.
Benchmarks
1.PassMark result
This benchmark measures the performance of the CPU using multiple threads.
2.PassMark result (single)
This benchmark measures the performance of the CPU using a single thread.
3.Geekbench 5 result (multi)
Geekbench 5 is a cross-platform benchmark that measures a processor’s multi-core performance. (Source: Primate Labs, 2022)
4.Cinebench R20 (multi) result
Unknown. Help us by suggesting a value. (Intel Core i5-8265U)
Cinebench R20 is a benchmark tool that measures a CPU’s multi-core performance by rendering a 3D scene.
5.Cinebench R20 (single) result
Unknown. Help us by suggesting a value. (Intel Core i5-8265U)
Cinebench R20 is a benchmark tool that measures a CPU’s single-core performance by rendering a 3D scene.
6.Geekbench 5 result (single)
Geekbench 5 is a cross-platform benchmark that measures a processor’s single-core performance. (Source: Primate Labs, 2022)
7.Blender (bmw27) result
Unknown. Help us by suggesting a value. (AMD A6-9225)
731.93seconds
The Blender (bmw27) benchmark measures the performance of a processor by rendering a 3D scene. More powerful processors can render the scene in less time.
8.Blender (classroom) result
Unknown. Help us by suggesting a value. (AMD A6-9225)
1694.63seconds
The Blender (classroom) benchmark measures the performance of a processor by rendering a 3D scene.
More powerful processors can render the scene in less time.
9.performance per watt
This means the CPU is more efficient, giving a greater amount of performance for each watt of power used.
Features
1.uses multithreading
✖AMD A6-9225
✔Intel Core i5-8265U
Multithreading technology (such as Intel’s Hyperthreading or AMD’s Simultaneous Multithreading) provides increased performance by splitting each of the processor’s physical cores into virtual cores, also known as threads. This way, each core can run two instruction streams at once.
2.Has AES
✔AMD A6-9225
✔Intel Core i5-8265U
AES is used to speed up encryption and decryption.
3.Has AVX
✔AMD A6-9225
✔Intel Core i5-8265U
AVX is used to help speed up calculations in multimedia, scientific and financial apps, as well as improving Linux RAID software performance.
4.SSE version
SSE is used to speed up multimedia tasks such as editing an image or adjusting audio volume. Each new version contains new instructions and improvements.
5.Has F16C
✔AMD A6-9225
✔Intel Core i5-8265U
F16C is used to speed up tasks such as adjusting the contrast of an image or adjusting volume.
6.bits executed at a time
Unknown. Help us by suggesting a value. (AMD A6-9225)
Unknown. Help us by suggesting a value. (Intel Core i5-8265U)
NEON provides acceleration for media processing, such as listening to MP3s.
7.Has MMX
✔AMD A6-9225
✔Intel Core i5-8265U
MMX is used to speed up tasks such as adjusting the contrast of an image or adjusting volume.
8.Has TrustZone
✖AMD A6-9225
✖Intel Core i5-8265U
A technology integrated into the processor to secure the device for use with features such as mobile payments and streaming video using digital rights management (DRM).
9.front-end width
Unknown. Help us by suggesting a value. (AMD A6-9225)
Unknown. Help us by suggesting a value. (Intel Core i5-8265U)
The CPU can decode more instructions per clock (IPC), meaning that the CPU performs better
Price comparison
Cancel
Which are the best CPUs?
AMD A6-9225 vs Intel Core i5-8250U
log 01. 02:32:39
#0 checking url part for id 11281 +0s … 0s
#1 checking url part for id 9206 +0s … 0s
#2 not redirecting to Ajax server +0s … 0s
#3 did not recreate cache, as it is less than 5 days old! Created at Fri, 30 Sep 2022 13:14:19 +0200 +0s … 0s
#4 linkCache_getLink no uid found +0.006s … 0.007s
#5 linkCache_getLink no uid found +0.006s … 0.013s
#6 composed specs +0.001s … 0.014s
#7 did output specs +0s … 0.014s
#8 getting avg benchmarks for device 11281 +0s .
.. 0.014s
#9 linkCache_getLink using $NBC_LINKCACHE +0s … 0.014s
#10 linkCache_getLink using $NBC_LINKCACHE +0s … 0.014s
#11 got single benchmarks 11281 +0.001s … 0.016s
#12 linkCache_getLink using $NBC_LINKCACHE +0.005s … 0.02s
#13 getting avg benchmarks for device 9206 +0.001s … 0.021s
#14 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.024s
#15 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.026s
#16 got single benchmarks 9206 +0.233s … 0.258s
#17 got avg benchmarks for devices +0s … 0.258s
#18 linkCache_getLink no uid found +0s … 0.258s
#19 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.26s
#20 linkCache_getLink no uid found +0s … 0.26s
#21 linkCache_getLink no uid found +0.001s … 0.261s
#22 linkCache_getLink no uid found +0s … 0.261s
#23 linkCache_getLink no uid found +0s .
.. 0.261s
#24 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s
#25 linkCache_getLink no uid found +0.001s … 0.262s
#26 linkCache_getLink no uid found +0s … 0.262s
#27 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s
#28 linkCache_getLink no uid found +0s … 0.262s
#29 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s
#30 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s
#31 linkCache_getLink no uid found +0.001s … 0.264s
#32 linkCache_getLink no uid found +0s … 0.264s
#33 linkCache_getLink no uid found +0s … 0.264s
#34 linkCache_getLink no uid found +0s … 0.264s
#35 linkCache_getLink no uid found +0s … 0.264s
#36 linkCache_getLink no uid found +0.001s … 0.265s
#37 linkCache_getLink no uid found +0s … 0.265s
#38 linkCache_getLink no uid found +0s … 0.266s
#39 linkCache_getLink no uid found +0s .
.. 0.266s
#40 linkCache_getLink no uid found +0s … 0.266s
#41 linkCache_getLink no uid found +0s … 0.266s
#42 linkCache_getLink no uid found +0s … 0.266s
#43 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s
#44 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.267s
#45 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s
#46 linkCache_getLink no uid found +0s … 0.268s
#47 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.269s
#48 linkCache_getLink no uid found +0s … 0.269s
#49 linkCache_getLink no uid found +0s … 0.269s
#50 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.27s
#51 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s
#52 linkCache_getLink no uid found +0.378s … 0.648s
#53 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#54 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.649s
#55 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#56 linkCache_getLink no uid found +0s … 0.649s
#57 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#58 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#59 linkCache_getLink no uid found +0s … 0.649s
#60 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#61 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#62 linkCache_getLink no uid found +0s … 0.649s
#63 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#64 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#65 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#66 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#67 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#68 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#69 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.649s
#70 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#71 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#72 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#73 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#74 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#75 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#76 linkCache_getLink no uid found +0s … 0.649s
#77 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#78 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#79 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#80 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#81 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#82 linkCache_getLink no uid found +0s … 0.649s
#83 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#84 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.649s
#85 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#86 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#87 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#88 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#89 linkCache_getLink no uid found +0s … 0.649s
#90 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#91 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#92 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#93 linkCache_getLink no uid found +0s … 0.649s
#94 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#95 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#96 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#97 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#98 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#99 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.649s
#100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#105 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#107 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#110 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#113 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.649s
#114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#116 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#119 linkCache_getLink no uid found +0s … 0.649s
#120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#123 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#124 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#125 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#126 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#127 linkCache_getLink no uid found +0s … 0.649s
#128 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.649s
#129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#130 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#133 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#137 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#138 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#139 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#140 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#141 linkCache_getLink no uid found +0s … 0.649s
#142 linkCache_getLink no uid found +0s … 0.649s
#143 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.649s
#144 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#147 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#148 linkCache_getLink no uid found +0s … 0.649s
#149 linkCache_getLink using $NBC_LINKCACHE +0s … 0.649s
#150 linkCache_getLink no uid found +0.001s … 0.65s
#151 linkCache_getLink no uid found +0s … 0.65s
#152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#153 linkCache_getLink no uid found +0s … 0.651s
#154 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#155 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#157 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#158 linkCache_getLink no uid found +0s .
.. 0.651s
#159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#160 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#161 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#162 linkCache_getLink no uid found +0s … 0.651s
#163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#164 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#165 linkCache_getLink no uid found +0s … 0.651s
#166 linkCache_getLink no uid found +0s … 0.651s
#167 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#169 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#171 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#172 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#173 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.651s
#174 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#175 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#176 linkCache_getLink no uid found +0s … 0.651s
#177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#179 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#180 linkCache_getLink no uid found +0s … 0.651s
#181 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#182 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#183 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#184 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#185 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#186 linkCache_getLink using $NBC_LINKCACHE +0s … 0.651s
#187 linkCache_getLink no uid found +0.001s … 0.652s
#188 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.653s
#189 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#191 linkCache_getLink no uid found +0s … 0.653s
#192 linkCache_getLink no uid found +0s … 0.653s
#193 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#194 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#195 linkCache_getLink no uid found +0s … 0.653s
#196 linkCache_getLink no uid found +0s … 0.653s
#197 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#198 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#199 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#200 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#201 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#202 linkCache_getLink no uid found +0s … 0.653s
#203 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.653s
#204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#205 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#206 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#207 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#208 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#209 linkCache_getLink no uid found +0s … 0.653s
#210 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#211 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#212 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#213 linkCache_getLink no uid found +0s … 0.653s
#214 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#215 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#217 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#218 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.653s
#219 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#220 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#221 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#222 linkCache_getLink using $NBC_LINKCACHE +0s … 0.653s
#223 linkCache_getLink no uid found +0.001s … 0.654s
#224 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#225 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#226 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#227 linkCache_getLink no uid found +0s … 0.654s
#228 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#229 linkCache_getLink no uid found +0s … 0.654s
#230 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#231 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#232 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#233 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.654s
#234 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#235 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#236 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#237 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#238 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#239 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#240 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#241 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#242 linkCache_getLink no uid found +0s … 0.654s
#243 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#244 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#245 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#246 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#247 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.654s
#248 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#249 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#250 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#251 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#252 linkCache_getLink using $NBC_LINKCACHE +0s … 0.654s
#253 linkCache_getLink no uid found +0s … 0.655s
#254 linkCache_getLink using $NBC_LINKCACHE +0s … 0.655s
#255 linkCache_getLink using $NBC_LINKCACHE +0s … 0.655s
#256 linkCache_getLink using $NBC_LINKCACHE +0s … 0.655s
#257 linkCache_getLink no uid found +0s … 0.655s
#258 linkCache_getLink using $NBC_LINKCACHE +0s … 0.655s
#259 linkCache_getLink using $NBC_LINKCACHE +0s … 0.655s
#260 linkCache_getLink using $NBC_LINKCACHE +0s … 0.655s
#261 linkCache_getLink using $NBC_LINKCACHE +0s … 0.655s
#262 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.655s
#263 linkCache_getLink using $NBC_LINKCACHE +0s … 0.655s
#264 linkCache_getLink using $NBC_LINKCACHE +0s … 0.655s
#265 linkCache_getLink using $NBC_LINKCACHE +0s … 0.655s
#266 linkCache_getLink no uid found +0.001s … 0.656s
#267 linkCache_getLink no uid found +0s … 0.656s
#268 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#269 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#270 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#271 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#272 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#273 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#274 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#275 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#276 linkCache_getLink using $NBC_LINKCACHE +0s … 0.
656s
#277 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#278 linkCache_getLink no uid found +0s … 0.656s
#279 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#280 linkCache_getLink no uid found +0s … 0.656s
#281 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#282 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#283 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#284 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#285 linkCache_getLink no uid found +0s … 0.656s
#286 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#287 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#288 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#289 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#290 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#291 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.656s
#292 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#293 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#294 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#295 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#296 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#297 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#298 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#299 linkCache_getLink no uid found +0s … 0.656s
#300 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#301 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#302 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#303 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#304 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#305 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.656s
#306 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#307 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#308 linkCache_getLink using $NBC_LINKCACHE +0s … 0.656s
#309 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.657s
#310 linkCache_getLink using $NBC_LINKCACHE +0s … 0.657s
#311 linkCache_getLink using $NBC_LINKCACHE +0s … 0.657s
#312 linkCache_getLink using $NBC_LINKCACHE +0s … 0.657s
#313 linkCache_getLink using $NBC_LINKCACHE +0s … 0.657s
#314 linkCache_getLink using $NBC_LINKCACHE +0s … 0.657s
#315 linkCache_getLink using $NBC_LINKCACHE +0s … 0.657s
#316 linkCache_getLink using $NBC_LINKCACHE +0s … 0.657s
#317 linkCache_getLink using $NBC_LINKCACHE +0s … 0.657s
#318 linkCache_getLink using $NBC_LINKCACHE +0s … 0.657s
#319 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.657s
#320 linkCache_getLink using $NBC_LINKCACHE +0s … 0.657s
#321 linkCache_getLink using $NBC_LINKCACHE +0s … 0.658s
#322 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.658s
#323 linkCache_getLink using $NBC_LINKCACHE +0s … 0.658s
#324 linkCache_getLink using $NBC_LINKCACHE +0s … 0.658s
#325 linkCache_getLink using $NBC_LINKCACHE +0s … 0.658s
#326 linkCache_getLink using $NBC_LINKCACHE +0s … 0.658s
#327 linkCache_getLink using $NBC_LINKCACHE +0s … 0.658s
#328 linkCache_getLink using $NBC_LINKCACHE +0s … 0.658s
#329 linkCache_getLink using $NBC_LINKCACHE +0s … 0.659s
#330 linkCache_getLink using $NBC_LINKCACHE +0s … 0.659s
#331 linkCache_getLink using $NBC_LINKCACHE +0s … 0.659s
#332 linkCache_getLink using $NBC_LINKCACHE +0s … 0.659s
#333 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.659s
#334 linkCache_getLink using $NBC_LINKCACHE +0s … 0.659s
#335 linkCache_getLink no uid found +0.001s … 0.66s
#336 linkCache_getLink using $NBC_LINKCACHE +0s … 0.66s
#337 linkCache_getLink using $NBC_LINKCACHE +0s … 0.66s
#338 linkCache_getLink using $NBC_LINKCACHE +0s … 0.66s
#339 linkCache_getLink using $NBC_LINKCACHE +0s … 0.66s
#340 linkCache_getLink no uid found +0s … 0.66s
#341 linkCache_getLink using $NBC_LINKCACHE +0s … 0.66s
#342 linkCache_getLink using $NBC_LINKCACHE +0s … 0.66s
#343 linkCache_getLink no uid found +0s … 0.66s
#344 linkCache_getLink using $NBC_LINKCACHE +0s … 0.66s
#345 linkCache_getLink using $NBC_LINKCACHE +0s … 0.66s
#346 linkCache_getLink no uid found +0s … 0.66s
#347 linkCache_getLink using $NBC_LINKCACHE +0s … 0.66s
#348 linkCache_getLink no uid found +0s .
.. 0.66s
#349 linkCache_getLink no uid found +0.001s … 0.661s
#350 linkCache_getLink using $NBC_LINKCACHE +0s … 0.662s
#351 linkCache_getLink using $NBC_LINKCACHE +0s … 0.662s
#352 linkCache_getLink using $NBC_LINKCACHE +0s … 0.662s
#353 linkCache_getLink using $NBC_LINKCACHE +0s … 0.662s
#354 linkCache_getLink using $NBC_LINKCACHE +0s … 0.662s
#355 linkCache_getLink using $NBC_LINKCACHE +0s … 0.662s
#356 linkCache_getLink no uid found +0s … 0.662s
#357 linkCache_getLink using $NBC_LINKCACHE +0s … 0.662s
#358 linkCache_getLink no uid found +0s … 0.662s
#359 linkCache_getLink using $NBC_LINKCACHE +0s … 0.662s
#360 linkCache_getLink no uid found +0s … 0.662s
#361 linkCache_getLink no uid found +0s … 0.662s
#362 linkCache_getLink using $NBC_LINKCACHE +0s … 0.662s
#363 linkCache_getLink no uid found +0.
001s … 0.663s
#364 linkCache_getLink no uid found +0s … 0.663s
#365 linkCache_getLink no uid found +0s … 0.663s
#366 linkCache_getLink no uid found +0.002s … 0.666s
#367 linkCache_getLink using $NBC_LINKCACHE +0s … 0.666s
#368 linkCache_getLink using $NBC_LINKCACHE +0s … 0.666s
#369 linkCache_getLink no uid found +0s … 0.666s
#370 linkCache_getLink using $NBC_LINKCACHE +0s … 0.666s
#371 linkCache_getLink using $NBC_LINKCACHE +0s … 0.666s
#372 linkCache_getLink no uid found +0.002s … 0.667s
#373 linkCache_getLink using $NBC_LINKCACHE +0s … 0.667s
#374 linkCache_getLink using $NBC_LINKCACHE +0s … 0.667s
#375 linkCache_getLink no uid found +0s … 0.667s
#376 linkCache_getLink using $NBC_LINKCACHE +0s … 0.667s
#377 linkCache_getLink using $NBC_LINKCACHE +0s … 0.667s
#378 linkCache_getLink no uid found +0.
002s … 0.669s
#379 linkCache_getLink using $NBC_LINKCACHE +0s … 0.669s
#380 linkCache_getLink using $NBC_LINKCACHE +0s … 0.669s
#381 linkCache_getLink no uid found +0s … 0.669s
#382 linkCache_getLink no uid found +0s … 0.669s
#383 linkCache_getLink no uid found +0.001s … 0.67s
#384 linkCache_getLink using $NBC_LINKCACHE +0s … 0.671s
#385 linkCache_getLink no uid found +0s … 0.671s
#386 linkCache_getLink using $NBC_LINKCACHE +0s … 0.671s
#387 linkCache_getLink no uid found +0s … 0.671s
#388 linkCache_getLink no uid found +0.001s … 0.672s
#389 linkCache_getLink using $NBC_LINKCACHE +0s … 0.672s
#390 linkCache_getLink using $NBC_LINKCACHE +0s … 0.672s
#391 linkCache_getLink no uid found +0s … 0.672s
#392 linkCache_getLink using $NBC_LINKCACHE +0s … 0.672s
#393 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.672s
#394 linkCache_getLink using $NBC_LINKCACHE +0s … 0.672s
#395 linkCache_getLink using $NBC_LINKCACHE +0s … 0.672s
#396 linkCache_getLink no uid found +0.057s … 0.729s
#397 linkCache_getLink no uid found +0s … 0.73s
#398 linkCache_getLink no uid found +0s … 0.73s
#399 linkCache_getLink using $NBC_LINKCACHE +0s … 0.73s
#400 linkCache_getLink no uid found +0s … 0.73s
#401 linkCache_getLink using $NBC_LINKCACHE +0s … 0.73s
#402 linkCache_getLink no uid found +0.001s … 0.731s
#403 linkCache_getLink no uid found +0s … 0.732s
#404 linkCache_getLink no uid found +0s … 0.732s
#405 linkCache_getLink no uid found +0s … 0.732s
#406 linkCache_getLink using $NBC_LINKCACHE +0s … 0.732s
#407 linkCache_getLink using $NBC_LINKCACHE +0s … 0.732s
#408 linkCache_getLink no uid found +0.
002s … 0.733s
#409 linkCache_getLink using $NBC_LINKCACHE +0s … 0.734s
#410 linkCache_getLink no uid found +0s … 0.734s
#411 linkCache_getLink no uid found +0s … 0.734s
#412 linkCache_getLink no uid found +0s … 0.734s
#413 linkCache_getLink using $NBC_LINKCACHE +0s … 0.734s
#414 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.735s
#415 linkCache_getLink using $NBC_LINKCACHE +0s … 0.735s
#416 linkCache_getLink using $NBC_LINKCACHE +0s … 0.735s
#417 linkCache_getLink no uid found +0s … 0.735s
#418 linkCache_getLink using $NBC_LINKCACHE +0s … 0.735s
#419 linkCache_getLink using $NBC_LINKCACHE +0s … 0.735s
#420 linkCache_getLink no uid found +0s … 0.735s
#421 linkCache_getLink using $NBC_LINKCACHE +0s … 0.735s
#422 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.738s
#423 linkCache_getLink no uid found +0s .
.. 0.738s
#424 linkCache_getLink no uid found +0s … 0.738s
#425 linkCache_getLink using $NBC_LINKCACHE +0s … 0.738s
#426 linkCache_getLink no uid found +0.002s … 0.74s
#427 linkCache_getLink using $NBC_LINKCACHE +0s … 0.74s
#428 linkCache_getLink using $NBC_LINKCACHE +0s … 0.74s
#429 linkCache_getLink using $NBC_LINKCACHE +0s … 0.74s
#430 linkCache_getLink no uid found +0s … 0.74s
#431 linkCache_getLink using $NBC_LINKCACHE +0s … 0.74s
#432 linkCache_getLink using $NBC_LINKCACHE +0s … 0.74s
#433 linkCache_getLink using $NBC_LINKCACHE +0s … 0.74s
#434 linkCache_getLink using $NBC_LINKCACHE +0s … 0.74s
#435 linkCache_getLink using $NBC_LINKCACHE +0s … 0.74s
#436 linkCache_getLink using $NBC_LINKCACHE +0s … 0.74s
#437 linkCache_getLink using $NBC_LINKCACHE +0s … 0.74s
#438 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.74s
#439 linkCache_getLink using $NBC_LINKCACHE +0s … 0.74s
#440 linkCache_getLink using $NBC_LINKCACHE +0s … 0.74s
#441 linkCache_getLink no uid found +0.002s … 0.742s
#442 linkCache_getLink no uid found +0s … 0.743s
#443 linkCache_getLink using $NBC_LINKCACHE +0s … 0.743s
#444 linkCache_getLink using $NBC_LINKCACHE +0s … 0.743s
#445 linkCache_getLink using $NBC_LINKCACHE +0s … 0.743s
#446 linkCache_getLink using $NBC_LINKCACHE +0s … 0.743s
#447 linkCache_getLink using $NBC_LINKCACHE +0s … 0.743s
#448 linkCache_getLink using $NBC_LINKCACHE +0s … 0.743s
#449 linkCache_getLink using $NBC_LINKCACHE +0s … 0.743s
#450 linkCache_getLink no uid found +0s … 0.743s
#451 linkCache_getLink no uid found +0s … 0.743s
#452 linkCache_getLink no uid found +0s … 0.743s
#453 linkCache_getLink no uid found +0.
002s … 0.744s
#454 linkCache_getLink no uid found +0s … 0.745s
#455 linkCache_getLink using $NBC_LINKCACHE +0s … 0.745s
#456 linkCache_getLink using $NBC_LINKCACHE +0s … 0.745s
#457 linkCache_getLink no uid found +0s … 0.745s
#458 linkCache_getLink using $NBC_LINKCACHE +0s … 0.745s
#459 linkCache_getLink using $NBC_LINKCACHE +0s … 0.745s
#460 linkCache_getLink using $NBC_LINKCACHE +0s … 0.745s
#461 linkCache_getLink using $NBC_LINKCACHE +0s … 0.745s
#462 linkCache_getLink using $NBC_LINKCACHE +0s … 0.745s
#463 linkCache_getLink no uid found +0s … 0.745s
#464 linkCache_getLink no uid found +0s … 0.745s
#465 linkCache_getLink no uid found +0.001s … 0.746s
#466 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.747s
#467 linkCache_getLink using $NBC_LINKCACHE +0s … 0.747s
#468 linkCache_getLink no uid found +0s .
.. 0.747s
#469 linkCache_getLink no uid found +0s … 0.747s
#470 linkCache_getLink using $NBC_LINKCACHE +0s … 0.747s
#471 linkCache_getLink using $NBC_LINKCACHE +0s … 0.747s
#472 linkCache_getLink using $NBC_LINKCACHE +0s … 0.747s
#473 linkCache_getLink using $NBC_LINKCACHE +0s … 0.747s
#474 linkCache_getLink no uid found +0s … 0.747s
#475 linkCache_getLink using $NBC_LINKCACHE +0s … 0.747s
#476 linkCache_getLink no uid found +0s … 0.747s
#477 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.748s
#478 linkCache_getLink using $NBC_LINKCACHE +0s … 0.748s
#479 linkCache_getLink using $NBC_LINKCACHE +0s … 0.748s
#480 linkCache_getLink using $NBC_LINKCACHE +0s … 0.748s
#481 linkCache_getLink no uid found +0.001s … 0.75s
#482 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#483 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.75s
#484 linkCache_getLink no uid found +0s … 0.75s
#485 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#486 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#487 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#488 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#489 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#490 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#491 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#492 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#493 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#494 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#495 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#496 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#497 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#498 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.75s
#499 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#500 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#501 linkCache_getLink no uid found +0s … 0.75s
#502 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#503 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#504 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#505 linkCache_getLink no uid found +0s … 0.75s
#506 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#507 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#508 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#509 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#510 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#511 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#512 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#513 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.75s
#514 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#515 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#516 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#517 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#518 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#519 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#520 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#521 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#522 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#523 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#524 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#525 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#526 linkCache_getLink using $NBC_LINKCACHE +0s … 0.75s
#527 linkCache_getLink no uid found +0s … 0.751s
#528 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.751s
#529 linkCache_getLink no uid found +0s … 0.751s
#530 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#531 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#532 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#533 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#534 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#535 linkCache_getLink no uid found +0s … 0.751s
#536 linkCache_getLink no uid found +0s … 0.751s
#537 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#538 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#539 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#540 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#541 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#542 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#543 linkCache_getLink no uid found +0s .
.. 0.751s
#544 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#545 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#546 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#547 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#548 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#549 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#550 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#551 linkCache_getLink no uid found +0s … 0.751s
#552 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#553 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#554 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#555 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#556 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#557 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.751s
#558 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#559 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#560 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#561 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#562 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#563 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#564 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#565 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#566 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#567 linkCache_getLink no uid found +0s … 0.751s
#568 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#569 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#570 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#571 linkCache_getLink using $NBC_LINKCACHE +0s …
0.751s
#572 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#573 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#574 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#575 linkCache_getLink no uid found +0s … 0.751s
#576 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#577 linkCache_getLink using $NBC_LINKCACHE +0s … 0.751s
#578 linkCache_getLink no uid found +0.001s … 0.752s
#579 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#580 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#581 linkCache_getLink no uid found +0s … 0.753s
#582 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#583 linkCache_getLink no uid found +0s … 0.753s
#584 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#585 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#586 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.753s
#587 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#588 linkCache_getLink no uid found +0s … 0.753s
#589 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#590 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#591 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#592 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#593 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#594 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#595 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#596 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#597 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#598 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#599 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#600 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.753s
#601 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#602 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#603 linkCache_getLink no uid found +0s … 0.753s
#604 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#605 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#606 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#607 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#608 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#609 linkCache_getLink using $NBC_LINKCACHE +0s … 0.753s
#610 linkCache_getLink no uid found +0s … 0.753s
#611 linkCache_getLink no uid found +0.002s … 0.755s
#612 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#613 linkCache_getLink no uid found +0s … 0.755s
#614 linkCache_getLink no uid found +0s … 0.755s
#615 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.755s
#616 linkCache_getLink no uid found +0s … 0.755s
#617 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#618 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#619 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#620 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#621 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#622 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#623 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#624 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#625 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#626 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#627 linkCache_getLink no uid found +0s … 0.755s
#628 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#629 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#630 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.755s
#631 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#632 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#633 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#634 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#635 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#636 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#637 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#638 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#639 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#640 linkCache_getLink using $NBC_LINKCACHE +0s … 0.755s
#641 linkCache_getLink no uid found +0s … 0.755s
#642 linkCache_getLink no uid found +0.001s … 0.757s
#643 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#644 linkCache_getLink no uid found +0s … 0.757s
#645 linkCache_getLink no uid found +0s .
.. 0.757s
#646 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#647 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#648 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#649 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#650 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#651 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#652 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#653 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#654 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#655 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#656 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#657 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#658 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#659 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.757s
#660 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#661 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#662 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#663 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#664 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#665 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#666 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#667 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#668 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#669 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#670 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#671 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#672 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#673 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.757s
#674 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#675 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#676 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#677 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#678 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#679 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#680 linkCache_getLink no uid found +0s … 0.757s
#681 linkCache_getLink no uid found +0s … 0.757s
#682 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#683 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#684 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#685 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#686 linkCache_getLink using $NBC_LINKCACHE +0s … 0.757s
#687 linkCache_getLink no uid found +0.002s … 0.759s
#688 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.76s
#689 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#690 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#691 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#692 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#693 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#694 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#695 linkCache_getLink no uid found +0s … 0.76s
#696 linkCache_getLink no uid found +0s … 0.76s
#697 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#698 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#699 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#700 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#701 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#702 linkCache_getLink no uid found +0s … 0.76s
#703 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.76s
#704 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#705 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#706 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#707 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#708 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#709 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#710 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#711 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#712 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#713 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#714 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#715 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#716 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#717 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#718 linkCache_getLink no uid found +0s .
.. 0.76s
#719 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#720 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#721 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#722 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#723 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#724 linkCache_getLink no uid found +0s … 0.76s
#725 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#726 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#727 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#728 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#729 linkCache_getLink no uid found +0s … 0.76s
#730 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#731 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#732 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#733 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.76s
#734 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#735 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#736 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#737 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#738 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#739 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#740 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#741 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#742 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#743 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#744 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#745 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#746 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#747 linkCache_getLink no uid found +0s … 0.76s
#748 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.76s
#749 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#750 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#751 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#752 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#753 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#754 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#755 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#756 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#757 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#758 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#759 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#760 linkCache_getLink no uid found +0s … 0.76s
#761 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#762 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#763 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.76s
#764 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#765 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#766 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#767 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#768 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#769 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#770 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#771 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#772 linkCache_getLink using $NBC_LINKCACHE +0s … 0.76s
#773 linkCache_getLink no uid found +0.002s … 0.762s
#774 linkCache_getLink using $NBC_LINKCACHE +0s … 0.762s
#775 linkCache_getLink using $NBC_LINKCACHE +0s … 0.762s
#776 linkCache_getLink using $NBC_LINKCACHE +0s … 0.762s
#777 linkCache_getLink no uid found +0s … 0.762s
#778 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.762s
#779 linkCache_getLink using $NBC_LINKCACHE +0s … 0.762s
#780 linkCache_getLink using $NBC_LINKCACHE +0s … 0.762s
#781 linkCache_getLink using $NBC_LINKCACHE +0s … 0.762s
#782 linkCache_getLink using $NBC_LINKCACHE +0s … 0.762s
#783 linkCache_getLink using $NBC_LINKCACHE +0s … 0.762s
#784 linkCache_getLink no uid found +0s … 0.762s
#785 linkCache_getLink using $NBC_LINKCACHE +0s … 0.762s
#786 linkCache_getLink using $NBC_LINKCACHE +0s … 0.762s
#787 linkCache_getLink using $NBC_LINKCACHE +0s … 0.762s
#788 linkCache_getLink using $NBC_LINKCACHE +0s … 0.762s
#789 linkCache_getLink using $NBC_LINKCACHE +0s … 0.762s
#790 linkCache_getLink no uid found +0s … 0.763s
#791 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#792 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#793 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.763s
#794 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#795 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#796 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#797 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#798 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#799 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#800 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#801 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#802 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#803 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#804 linkCache_getLink no uid found +0s … 0.763s
#805 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#806 linkCache_getLink no uid found +0s … 0.763s
#807 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#808 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.763s
#809 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#810 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#811 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#812 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#813 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#814 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#815 linkCache_getLink no uid found +0s … 0.763s
#816 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#817 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#818 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#819 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#820 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#821 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#822 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.763s
#823 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#824 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#825 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#826 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#827 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#828 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#829 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#830 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#831 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#832 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#833 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#834 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#835 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#836 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.763s
#837 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#838 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#839 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#840 linkCache_getLink no uid found +0s … 0.763s
#841 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#842 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#843 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#844 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#845 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#846 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#847 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#848 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#849 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#850 linkCache_getLink no uid found +0s … 0.763s
#851 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.763s
#852 linkCache_getLink no uid found +0s … 0.763s
#853 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#854 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#855 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#856 linkCache_getLink using $NBC_LINKCACHE +0s … 0.763s
#857 linkCache_getLink no uid found +0.002s … 0.765s
#858 linkCache_getLink no uid found +0s … 0.765s
#859 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#860 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#861 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#862 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#863 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#864 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#865 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#866 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.765s
#867 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#868 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#869 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#870 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#871 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#872 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#873 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#874 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#875 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#876 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#877 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#878 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#879 linkCache_getLink no uid found +0s … 0.765s
#880 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.765s
#881 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#882 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#883 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#884 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.768s
#885 linkCache_getLink no uid found +0s … 0.768s
#886 linkCache_getLink using $NBC_LINKCACHE +0s … 0.768s
#887 linkCache_getLink no uid found +0s … 0.768s
#888 linkCache_getLink using $NBC_LINKCACHE +0s … 0.768s
#889 linkCache_getLink no uid found +0.002s … 0.769s
#890 linkCache_getLink using $NBC_LINKCACHE +0s … 0.769s
#891 linkCache_getLink using $NBC_LINKCACHE +0s … 0.769s
#892 linkCache_getLink using $NBC_LINKCACHE +0s … 0.769s
#893 linkCache_getLink no uid found +0s … 0.769s
#894 linkCache_getLink no uid found +0.002s … 0.771s
#895 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.771s
#896 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.773s
#897 linkCache_getLink no uid found +0s … 0.773s
#898 linkCache_getLink no uid found +0.002s … 0.775s
#899 linkCache_getLink no uid found +0s … 0.775s
#900 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#901 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#902 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#903 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#904 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#905 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#906 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#907 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#908 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#909 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#910 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.775s
#911 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#912 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#913 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#914 linkCache_getLink no uid found +0s … 0.775s
#915 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#916 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#917 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#918 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#919 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#920 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#921 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#922 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#923 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#924 linkCache_getLink no uid found +0.001s … 0.
777s
#925 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#926 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#927 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#928 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#929 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#930 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#931 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#932 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#933 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#934 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#935 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#936 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#937 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#938 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.777s
#939 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#940 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#941 linkCache_getLink no uid found +0s … 0.777s
#942 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#943 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#944 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#945 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#946 linkCache_getLink no uid found +0s … 0.777s
#947 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#948 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#949 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#950 linkCache_getLink no uid found +0.001s … 0.779s
#951 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#952 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#953 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.779s
#954 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#955 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#956 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#957 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#958 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#959 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#960 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#961 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#962 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#963 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#964 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#965 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#966 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#967 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.779s
#968 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#969 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#970 linkCache_getLink no uid found +0.002s … 0.781s
#971 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#972 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#973 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#974 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#975 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#976 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#977 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#978 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#979 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#980 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#981 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.781s
#982 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#983 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#984 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#985 linkCache_getLink using $NBC_LINKCACHE +0s … 0.782s
#986 linkCache_getLink using $NBC_LINKCACHE +0s … 0.782s
#987 linkCache_getLink using $NBC_LINKCACHE +0s … 0.782s
#988 linkCache_getLink using $NBC_LINKCACHE +0s … 0.782s
#989 linkCache_getLink using $NBC_LINKCACHE +0s … 0.782s
#990 linkCache_getLink no uid found +0.002s … 0.783s
#991 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#992 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#993 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#994 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#995 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.784s
#996 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#997 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#998 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#999 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#1000 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#1001 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#1002 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#1003 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#1004 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#1005 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#1006 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#1007 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#1008 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#1009 linkCache_getLink no uid found +0.
001s … 0.785s
#1010 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1011 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1012 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1013 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1014 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1015 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1016 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1017 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1018 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1019 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1020 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1021 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1022 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1023 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.786s
#1024 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1025 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1026 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1027 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#1028 linkCache_getLink no uid found +0.001s … 0.787s
#1029 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s
#1030 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s
#1031 linkCache_getLink no uid found +0.001s … 0.789s
#1032 linkCache_getLink using $NBC_LINKCACHE +0s … 0.789s
#1033 linkCache_getLink using $NBC_LINKCACHE +0s … 0.789s
#1034 linkCache_getLink no uid found +0.001s … 0.791s
#1035 linkCache_getLink no uid found +0.001s … 0.792s
#1036 linkCache_getLink no uid found +0.001s … 0.793s
#1037 linkCache_getLink no uid found +0.001s … 0.
794s
#1038 linkCache_getLink no uid found +0.001s … 0.796s
#1039 linkCache_getLink no uid found +0.001s … 0.797s
#1040 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#1041 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#1042 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#1043 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#1044 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#1045 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#1046 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#1047 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#1048 linkCache_getLink no uid found +0s … 0.797s
#1049 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#1050 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#1051 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.797s
#1052 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#1053 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#1054 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#1055 linkCache_getLink no uid found +0s … 0.798s
#1056 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1057 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1058 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1059 linkCache_getLink no uid found +0s … 0.798s
#1060 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1061 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1062 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1063 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1064 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1065 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.798s
#1066 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1067 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1068 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1069 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1070 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1071 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1072 linkCache_getLink no uid found +0s … 0.798s
#1073 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1074 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1075 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1076 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1077 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1078 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1079 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.798s
#1080 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1081 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1082 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1083 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1084 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1085 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1086 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1087 linkCache_getLink no uid found +0s … 0.798s
#1088 linkCache_getLink no uid found +0s … 0.798s
#1089 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1090 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1091 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1092 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1093 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.798s
#1094 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1095 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1096 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1097 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s
#1098 linkCache_getLink no uid found +0.002s … 0.799s
#1099 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s
#1100 linkCache_getLink no uid found +0s … 0.8s
#1101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s
#1102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s
#1103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s
#1104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s
#1105 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s
#1106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s
#1107 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s
#1108 linkCache_getLink no uid found +0s .
.. 0.8s
#1109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s
#1110 linkCache_getLink no uid found +0s … 0.8s
#1111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s
#1112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s
#1113 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s
#1114 linkCache_getLink no uid found +0.003s … 0.803s
#1115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1116 linkCache_getLink no uid found +0s … 0.803s
#1117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1123 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.803s
#1124 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1125 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1126 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1127 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1128 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1130 linkCache_getLink no uid found +0s … 0.803s
#1131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1132 linkCache_getLink no uid found +0s … 0.803s
#1133 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1137 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.803s
#1138 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1139 linkCache_getLink no uid found +0s … 0.803s
#1140 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1141 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1143 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1144 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1147 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1148 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1149 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1150 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1151 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.803s
#1152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1153 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1154 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1155 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1157 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1158 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1160 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1161 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1162 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1164 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1165 linkCache_getLink no uid found +0s .
.. 0.803s
#1166 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1167 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s
#1169 linkCache_getLink no uid found +0.003s … 0.806s
#1170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s
#1171 linkCache_getLink no uid found +0s … 0.807s
#1172 linkCache_getLink no uid found +0s … 0.807s
#1173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s
#1174 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.81s
#1175 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.811s
#1176 linkCache_getLink no uid found +0s … 0.811s
#1177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s
#1178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s
#1179 linkCache_getLink using $NBC_LINKCACHE +0.001s .
.. 0.812s
#1180 linkCache_getLink no uid found +0s … 0.812s
#1181 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s
#1182 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s
#1183 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.815s
#1184 linkCache_getLink using $NBC_LINKCACHE +0s … 0.815s
#1185 linkCache_getLink no uid found +0s … 0.815s
#1186 linkCache_getLink using $NBC_LINKCACHE +0s … 0.815s
#1187 min, max, avg, median took s +0.001s … 0.816s
#1188 linkCache_getLink using $NBC_LINKCACHE +0.022s … 0.838s
#1189 return log +0.004s … 0.841s
AMD A6-9225 vs Intel Core i5-8265U
Comparative analysis of AMD A6-9225 and Intel Core i5-8265U processors for all known characteristics in the following categories: Essentials, Performance, Memory, Graphics, Graphics interfaces, Graphics API support, Compatibility, Peripherals, Advanced Technologies, Virtualization, Graphics image quality, Security & Reliability.
Benchmark processor performance analysis: PassMark — Single thread mark, PassMark — CPU mark, GFXBench 4.0 — Car Chase Offscreen (Frames), GFXBench 4.0 — Car Chase Offscreen (Fps), GFXBench 4.0 — Manhattan (Frames), GFXBench 4.0 — Manhattan (Fps), GFXBench 4.0 — T-Rex (Frames), GFXBench 4.0 — T-Rex (Fps), CompuBench 1.5 Desktop — Face Detection (mPixels/s), Geekbench 4 — Single Core, Geekbench 4 — Multi-Core, 3DMark Fire Strike — Physics Score, CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s), CompuBench 1.5 Desktop — T-Rex (Frames/s), CompuBench 1.5 Desktop — Video Composition (Frames/s), CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s).
AMD A6-9225
Buy on Amazon
vs
Intel Core i5-8265U
Buy on Amazon
Differences
Reasons to consider the Intel Core i5-8265U
- 2 more cores, run more applications at once: 4 vs 2
- Around 50% higher clock speed: 3.
90 GHz vs 2.6 GHz - Around 11% higher maximum core temperature: 100°C vs 90°C
- A newer manufacturing process allows for a more powerful, yet cooler running processor: 14 nm vs 28 nm
- Around 79% better performance in PassMark — Single thread mark: 2111 vs 1182
- 4.5x better performance in PassMark — CPU mark: 6072 vs 1343
- 2.2x better performance in GFXBench 4.0 — Car Chase Offscreen (Frames): 1665 vs 754
- 2.2x better performance in GFXBench 4.0 — Car Chase Offscreen (Fps): 1665 vs 754
- 2.1x better performance in GFXBench 4.0 — Manhattan (Frames): 3208 vs 1522
- 2.1x better performance in GFXBench 4.0 — Manhattan (Fps): 3208 vs 1522
- Around 37% better performance in GFXBench 4.0 — T-Rex (Frames): 5740 vs 4199
- Around 37% better performance in GFXBench 4.0 — T-Rex (Fps): 5740 vs 4199
- 18.8x better performance in CompuBench 1.5 Desktop — Face Detection (mPixels/s): 26.164 vs 1.391
| Number of cores | 4 vs 2 |
| Maximum frequency | 3. 90 GHz vs 2.6 GHz |
| Maximum core temperature | 100°C vs 90°C |
| Manufacturing process technology | 14 nm vs 28 nm |
| PassMark — Single thread mark | 2111 vs 1182 |
| PassMark — CPU mark | 6072 vs 1343 |
| GFXBench 4.0 — Car Chase Offscreen (Frames) | 1665 vs 754 |
| GFXBench 4.0 — Car Chase Offscreen (Fps) | 1665 vs 754 |
| GFXBench 4.0 — Manhattan (Frames) | 3208 vs 1522 |
GFXBench 4. 0 — Manhattan (Fps) |
3208 vs 1522 |
| GFXBench 4.0 — T-Rex (Frames) | 5740 vs 4199 |
| GFXBench 4.0 — T-Rex (Fps) | 5740 vs 4199 |
| CompuBench 1.5 Desktop — Face Detection (mPixels/s) | 26.164 vs 1.391 |
Compare benchmarks
CPU 1: AMD A6-9225
CPU 2: Intel Core i5-8265U
| PassMark — Single thread mark |
|
|
|||
| PassMark — CPU mark |
|
|
|||
GFXBench 4. 0 — Car Chase Offscreen (Frames) |
|
|
|||
| GFXBench 4.0 — Car Chase Offscreen (Fps) |
|
|
|||
| GFXBench 4.0 — Manhattan (Frames) |
|
|
|||
GFXBench 4. 0 — Manhattan (Fps) |
|
|
|||
| GFXBench 4.0 — T-Rex (Frames) |
|
|
|||
| GFXBench 4.0 — T-Rex (Fps) |
|
|
|||
| CompuBench 1.5 Desktop — Face Detection (mPixels/s) |
|
|
164| Name | AMD A6-9225 | Intel Core i5-8265U |
|---|---|---|
| PassMark — Single thread mark | 1182 | 2111 |
| PassMark — CPU mark | 1343 | 6072 |
| GFXBench 4.0 — Car Chase Offscreen (Frames) | 754 | 1665 |
| GFXBench 4.0 — Car Chase Offscreen (Fps) | 754 | 1665 |
| GFXBench 4.0 — Manhattan (Frames) | 1522 | 3208 |
GFXBench 4. 0 — Manhattan (Fps) |
1522 | 3208 |
| GFXBench 4.0 — T-Rex (Frames) | 4199 | 5740 |
| GFXBench 4.0 — T-Rex (Fps) | 4199 | 5740 |
| CompuBench 1.5 Desktop — Face Detection (mPixels/s) | 1.391 | 26.164 |
| Geekbench 4 — Single Core | 908 | |
| Geekbench 4 — Multi-Core | 2803 | |
| 3DMark Fire Strike — Physics Score | 2529 | |
CompuBench 1. 5 Desktop — Ocean Surface Simulation (Frames/s) |
296.492 | |
| CompuBench 1.5 Desktop — T-Rex (Frames/s) | 1.652 | |
| CompuBench 1.5 Desktop — Video Composition (Frames/s) | 17.731 | |
| CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s) | 29.943 |
Compare specifications (specs)
| AMD A6-9225 | Intel Core i5-8265U | |
|---|---|---|
| Family | AMD A-Series Processors | |
| Launch date | Q2 2018 | 21 August 2018 |
| OPN Tray | AM9225AYN23AC | |
| OS Support | Windows 10 — 64-Bit Edition, RHEL x86 64-Bit, Ubuntu x86 64-Bit | |
| Place in performance rating | 1221 | 543 |
| Series | AMD A6-Series APU for Laptops | 8th Generation Intel® Core™ i5 Processors |
| Vertical segment | Laptop | Mobile |
| Architecture codename | Whiskey Lake | |
| Price now | $297 | |
| Processor Number | i5-8265U | |
| Status | Launched | |
| Value for money (0-100) | 8. 04 |
|
| Base frequency | 3.1 GHz | 1.60 GHz |
| Compute Cores | 5 | |
| L2 cache | 1 MB | 1 MB |
| Manufacturing process technology | 28 nm | 14 nm |
| Maximum core temperature | 90°C | 100°C |
| Maximum frequency | 2.6 GHz | 3.90 GHz |
| Number of cores | 2 | 4 |
| Number of GPU cores | 3 | |
| Unlocked | ||
| 64 bit support | ||
| Bus Speed | 4 GT/s OPI | |
| Die size | 123 mm | |
| L1 cache | 256 KB | |
| L3 cache | 6 MB | |
| Maximum case temperature (TCase) | 72 °C | |
| Number of threads | 8 | |
| Max memory channels | 1 | 2 |
| Supported memory frequency | 2133 MHz | |
| Maximum memory bandwidth | 37. 5 GB/s |
|
| Maximum memory size | 32 GB | |
| Supported memory types | DDR4-2400, LPDDR3-2133 | |
| Enduro | ||
| Graphics max frequency | 686 MHz | |
| Processor graphics | AMD Radeon R4 Graphics | Intel® UHD Graphics 620 |
| Switchable graphics | ||
| Unified Video Decoder (UVD) | ||
| Video Codec Engine (VCE) | ||
| Device ID | 0x3EA0 | |
| Graphics base frequency | 300 MHz | |
| Graphics max dynamic frequency | 1. 10 GHz |
|
| Intel® Clear Video HD technology | ||
| Intel® Clear Video technology | ||
| Intel® Quick Sync Video | ||
| Max video memory | 32 GB | |
| DisplayPort | ||
| HDMI | ||
| DVI | ||
| eDP | ||
| Number of displays supported | 3 | |
| DirectX | 12 | 12 |
| Vulkan | ||
| OpenGL | 4. 5 |
|
| Configurable TDP | 10-15 Watt | |
| Thermal Design Power (TDP) | 15 Watt | 15 Watt |
| Configurable TDP-down | 10 W | |
| Configurable TDP-down Frequency | 800 MHz | |
| Configurable TDP-up | 25 W | |
| Configurable TDP-up Frequency | 1.80 GHz | |
| Low Halogen Options Available | ||
| Max number of CPUs in a configuration | 1 | |
| Package Size | 46×24 | |
| Sockets supported | FCBGA1528 | |
| PCI Express revision | 3. 0 |
3.0 |
| Max number of PCIe lanes | 16 | |
| PCIe configurations | 1×4, 2×2, 1×2+2×1 and 4×1 | |
| Adaptive Voltage and Frequency Scaling (AVFS) | ||
| AMD App Acceleration | ||
| AMD HD3D technology | ||
| AMD Mantle API | ||
| DualGraphics | ||
| Fused Multiply-Add 4 (FMA4) | ||
| Intel® AES New Instructions | ||
| Enhanced Intel SpeedStep® technology | ||
| Idle States | ||
| Instruction set extensions | Intel® SSE4. 1, Intel® SSE4.2, Intel® AVX2 |
|
| Intel 64 | ||
| Intel® Advanced Vector Extensions (AVX) | ||
| Intel® Flex Memory Access | ||
| Intel® Hyper-Threading technology | ||
| Intel® My WiFi technology | ||
| Intel® Optane™ Memory Supported | ||
| Intel® Smart Response technology | ||
| Intel® Stable Image Platform Program (SIPP) | ||
| Intel® TSX-NI | ||
| Intel® Turbo Boost technology | ||
| Intel® vPro™ Platform Eligibility | ||
| Speed Shift technology | ||
| Thermal Monitoring | ||
| AMD Virtualization (AMD-V™) | ||
| Intel® Virtualization Technology (VT-x) | ||
| Intel® Virtualization Technology for Directed I/O (VT-d) | ||
| Intel® VT-x with Extended Page Tables (EPT) | ||
| 4K resolution support | ||
| Max resolution over DisplayPort | [email protected] | |
| Max resolution over eDP | [email protected] | |
| Max resolution over HDMI 1. |
[email protected] | |
| Execute Disable Bit (EDB) | ||
| Intel® Identity Protection technology | ||
| Intel® OS Guard | ||
| Intel® Secure Key technology | ||
| Intel® Software Guard Extensions (Intel® SGX) | ||
| Intel® Trusted Execution technology (TXT) |
AMD A6-9225 vs Intel Core i5-11300H
|
|
|
|
|
AMD A6-9225 vs Intel Core i5-11300H
Comparison of the technical characteristics between the processors, with the AMD A6-9225 on one side and the Intel Core i5-11300H on the other side. The first is dedicated to the notebook sector, It has 2 cores, 2 threads, a maximum frequency of 3,0GHz. The second is used on the mobile workstation segment, it has a total of 4 cores, 8 threads, its turbo frequency is set to 4,4 GHz. The following table also compares the lithography, the number of transistors (if indicated), the amount of cache memory, the maximum RAM memory capacity, the type of memory accepted, the release date, the maximum number of PCIe lanes, the values obtained in Geekbench 4 and Cinebench R15.
Note: Commissions may be earned from the links above.
This page contains references to products from one or more of our advertisers. We may receive compensation when you click on links to those products. For an explanation of our advertising policy, please visit this page.
Specifications:
| Processor | AMD A6-9225 | Intel Core i5-11300H | ||||||
| Market (main) | Notebook | Mobile workstation | ||||||
| ISA | x86-64 (64 bit) | x86-64 (64 bit) | ||||||
| Microarchitecture | Excavator | Tiger Lake | ||||||
| Core name | Stoney Ridge | Tiger Lake-h45 | ||||||
| Family | A6-9000 | Core i5-11000 | ||||||
| Part number(s), S-Spec | AM9225AYN23AC | FH8069004600005, SRKH6 |
||||||
| Release date | Q2 2018 | Q1 2021 | ||||||
| Lithography | 28 nm | 10 nm SuperFin | ||||||
| Transistors | 1. |
— | ||||||
| Cores | 2 | 4 | ||||||
| Threads | 2 | 8 | ||||||
| Base frequency | 2,6 GHz | 2,6 GHz | ||||||
| Turbo frequency | 3,0 GHz | 4,4 GHz | ||||||
| Cache memory | 1 MB | 8 MB | ||||||
| Max memory capacity | 8 GB | 64 GB | ||||||
| Memory types | DDR4-2133 | DDR4-3200, LPDDR4x-4267 | ||||||
| Max # of memory channels | 1 | 2 | ||||||
| Max PCIe lanes | 8 | 16 | ||||||
| TDP | 15 W | 35 W | ||||||
| GPU integrated graphics | AMD Radeon R4 Mobile Graphics (Stoney) | Intel Iris Xe Graphics G7 80EU | ||||||
| GPU cores | 3 | — | ||||||
| GPU execution units | — | 80 | ||||||
| GPU shading units | 192 | 640 | ||||||
| GPU base clock | 200 MHz | 300 MHz | ||||||
| GPU boost clock | 686 MHz | 1300 MHz | ||||||
| GPU FP32 floating point | 251,5 GFLOPS | 1. |
||||||
| Socket | BGA | BGA1449 | ||||||
| Maximum temperature | 90°C | 100°C | ||||||
| AI accelerator | — | Gaussian & Neural Accelerator | ||||||
| Crypto engine | — | AES New Instructions | ||||||
| Security | — | OS Guard, Boot Guard, Mode-based Execute Control, Control-Flow Enforcement Technology |
||||||
| Max display resolution | — | 4096×2304@60Hz | ||||||
| CPU-Z single thread | 185 | 464 | ||||||
| CPU-Z multi thread | 307 | 2. |
||||||
| Cinebench R15 single thread | 70 | 148 | ||||||
| Cinebench R15 multi-thread | 110 | 832 | ||||||
| Cinebench R20 single thread | 180 | 528 | ||||||
| Cinebench R20 multi-thread | 270 | 2.225 | ||||||
| PassMark single thread | 1.175 | 2.849 | ||||||
| PassMark CPU Mark | 1.324 | 11.552 | ||||||
| (Windows 64-bit) Geekbench 4 single core |
1.756 | 5.870 | ||||||
| (Windows 64-bit) Geekbench 4 multi-core |
2. |
19.040 | ||||||
| (Windows) Geekbench 5 single core |
319 | 1.246 | ||||||
| (Windows) Geekbench 5 multi-core |
506 | 4.377 | ||||||
| (SGEMM) GFLOPS performance |
30,44 GFLOPS | 349,1 GFLOPS | ||||||
| (Multi-core / watt performance) Performance / watt ratio |
177 pts / W | 544 pts / W | ||||||
| Amazon | ||||||||
| eBay |
Note: Commissions may be earned from the links above.
We can better compare what are the technical differences between the two processors.
Price: For technical reasons, we cannot currently display a price less than 24 hours, or a real-time price. This is why we prefer for the moment not to show a price. You should refer to the respective online stores for the latest price, as well as availability.
The processor Intel Core i5-11300H has a larger number of cores, the turbo frequency of Intel Core i5-11300H is bigger, that the PDT of AMD A6-9225 is lower. The Intel Core i5-11300H was started more recently.
Performances :
Performance comparison between the two processors, for this we consider the results generated on benchmark software such as Geekbench 4.
| CPU-Z — Multi-thread & single thread score | |
|---|---|
| Intel Core i5-11300H |
464 2.467 |
| AMD A6-9225 |
185 307 |
In single core, the difference is 151%. In multi-core, the difference in terms of gap is 704%.
Note: Commissions may be earned from the links above. These scores are only an
average of the performances got with these processors, you may get different results.
CPU-Z is a system information software that provides the name of the processor, its model number, the codename, the cache levels, the package, the process. It can also gives data about the mainboard, the memory. It makes real time measurement, with finally a benchmark for the single thread, as well as for the multi thread.
| Cinebench R15 — Multi-thread & single thread score | |
|---|---|
| Intel Core i5-11300H |
148 832 |
| AMD A6-9225 |
70 110 |
In single core, the difference is 111%. In multi-core, the difference in terms of gap is 656%.
Note: Commissions may be earned from the links above. These scores are only an
average of the performances got with these processors, you may get different results.
Cinebench R15 evaluates the performance of CPU calculations by restoring a photorealistic 3D scene. The scene has 2,000 objects, 300,000 polygons, uses sharp and fuzzy reflections, bright areas, shadows, procedural shaders, antialiasing, and so on. The faster the rendering of the scene is created, the more powerful the PC is, with a high number of points.
| Cinebench R20 — Multi-thread & single thread score | |
|---|---|
| Intel Core i5-11300H |
528 2.225 |
| AMD A6-9225 |
180 270 |
In single core, the difference is 193%. In multi-core, the difference in terms of gap is 724%.
Note: Commissions may be earned from the links above. These scores are only an
average of the performances got with these processors, you may get different results.
Cinebench R20 is a multi-platform test software which allows to evaluate the hardware capacities of a device such as a computer, a tablet, a server. This version of Cinebench takes into account recent developments in processors with multiple cores and the latest improvements in rendering techniques. The evaluation is ultimately even more relevant.
| PassMark — CPU Mark & single thread | |
|---|---|
| Intel Core i5-11300H |
2.849 11.552 |
| AMD A6-9225 |
1.175 1.324 |
In single core, the difference is 142%. In multi-core, the difference in terms of gap is 773%.
Note: Commissions may be earned from the links above. These scores are only an
average of the performances got with these processors, you may get different results.
PassMark is a benchmarking software that performs several performance tests including prime numbers, integers, floating point, compression, physics, extended instructions, encoding, sorting. The higher the score is, the higher is the device capacity.
On Windows 64-bit:
| Geekbench 4 — Multi-core & single core score — Windows 64-bit | |
|---|---|
| Intel Core i5-11300H |
5.870 19.040 |
| AMD A6-9225 |
1.756 2.650 |
In single core, the difference is 234%. In multi-core, the difference in terms of gap is 618%.
On Linux 64-bit:
| Geekbench 4 — Multi-core & single core score — Linux 64-bit | |
|---|---|
| Intel Core i5-11300H |
5. 18.264 |
| AMD A6-9225 |
2.024 2.943 |
In single core, the difference is 188%. In multi-core, the difference in terms of gap is 521%.
On Android 64-bit:
| Geekbench 4 — Multi-core & single core score — Android 64-bit | |
|---|---|
| Intel Core i5-11300H |
5.025 15.635 |
| AMD A6-9225 |
1.415 2.142 |
In single core, the difference is 255%. In multi-core, the difference in terms of gap is 630%.
Note: Commissions may be earned from the links above. These scores are only an
average of the performances got with these processors, you may get different results.
Geekbench 4 is a complete benchmark platform with several types of tests, including data compression, images, AES encryption, SQL encoding, HTML, PDF file rendering, matrix computation, Fast Fourier Transform, 3D object simulation, photo editing, memory testing. This allows us to better visualize the respective power of these devices. For each result, we took an average of 250 values on the famous benchmark software.
On Windows:
| Geekbench 5 — Multi-core & single core score — Windows | |
|---|---|
| Intel Core i5-11300H |
1.246 4.377 |
| AMD A6-9225 |
319 506 |
In single core, the difference is 291%. In multi-core, the difference in terms of gap is 765%.
On Linux:
| Geekbench 5 — Multi-core & single core score — Linux | |
|---|---|
| Intel Core i5-11300H |
1.467 4.791 |
| AMD A6-9225 |
388 481 |
In single core, the difference is 278%. In multi-core, the difference in terms of gap is 896%.
On macOS:
| Geekbench 5 — Multi-core & single core score — macOS | |
|---|---|
| Intel Core i5-11300H |
975 4.225 |
| AMD A6-9225 |
272 276 |
In single core, the difference is 258%. In multi-core, the difference in terms of gap is 1431%.
Note: Commissions may be earned from the links above. These scores are only an
average of the performances got with these processors, you may get different results.
Geekbench 5 is a software for measuring the performance of a computer system, for fixed devices, mobile devices, servers. This platform makes it possible to better compare the power of the CPU, the computing power and to compare it with similar or totally different systems. Geekbench 5 includes new workloads that represent work tasks and applications that we can find in reality.
Equivalence:
AMD A6-9225 Intel equivalentIntel Core i5-11300H AMD equivalent
See also:
AMD A6-9220AMD A6-9220CAMD A6-9220e
AMD A6-9225 vs Intel Core i5-9600KF
VS
AMD A6-9225 vs Intel Core i5-9600KF Comparison by technical specs (TDP, performance, memory, compatibility). CPU performance analysis in the benchmark comparison (in the mode of a single core and all the cores).
Which one?
The comparative analysis of technical specifications of AMD A6-9225 and Intel Core i5-9600KF shows which model is better for games and operational apps. We recommend paying your attention to yellow highlighted specs.
CPU Cores and Base Frequency
AMD A6-9225 vs Intel Core i5-9600KF
2.60 GHz
Frequency
3.70 GHz
2
CPU Cores
6
3.00 GHz
Turbo (1 Core)
4. 60 GHz
2
CPU Threads
6
2.60 GHz
Turbo (2 Cores)
no data
No
Hyperthreading
No
No
Overclocking
Yes
no data
Turbo (6 Cores)
4.30 GHz
Internal Graphics
AMD Radeon R4 (Stoney Ridge)
GPU name
0.66 GHz
GPU frequency
No turbo
GPU (Turbo)
No turbo
7
Generation
12
DirectX Version
3
Execution units
192
Shader
2 GB
Max. Memory
—
3
Max. displays
28 nm
Technology
Q2/2016
Release date
Hardware codec support
Decode
h364
No
Decode / Encode
JPEG
No
Decode
h365 8bit
No
Decode
h365 10bit
No
Decode
VP8
No
Decode
VP9
No
Decode
VC-1
No
Decode / Encode
AVC
No
RAM and PCIe
DDR4-2133
Memory type
DDR4-2666
8 GB
Max. Memory
128 GB
1
Memory channels
2
No
ECC
No
3.0
PCIe version
3.0
8
PCIe lanes
16
Encryption
Yes
AES-NI
Yes
Thermal Management
15 W
TDP
95 W
90 °C
Tjunction max.
100 °C
—
TDP up
—
10 W
TDP down
—
Technical details
2.00 MB
L3-Cache
9.00 MB
28 nm
Technology
14 nm
Stoney Ridge (Excavator)
Architecture
Coffee Lake Refresh
AMD-V, AMD-Vi
Virtualization
VT-x, VT-x EPT, VT-d
FP4
Socket
LGA 1151-2
Q3/2018
Release date
Q1/2019
Market price
ca. 260 $
Devices using this processor
Unknown
Used in
Unknown
CPU generation and family
AMD A6-9225 vs Intel Core i5-9600KF
Which to buy
The benchmark comparison of AMD A6-9225 and Intel Core i5-9600KF allows defining which CPU is currently better, more modern and efficient. The more points, the better.
Compare Benchmarks
Real world tests of AMD A6-9225 vs Intel Core i5-9600KF:
Popular comparisons
| 1. |
AMD A6-9225 vs. AMD A8-7650K |
|
| 2. |
AMD A6-9225 vs. Intel Celeron J4115 |
|
| 3. |
AMD A6-9225 vs. Intel Core i5-6300U |
|
| 4. |
AMD A6-9225 vs. Intel Core i7-1185G7 |
|
|
5. |
AMD A6-9225 vs. Intel Core i3-3240 |
|
| 6. |
AMD A6-9225 vs. Intel Core i7-5500U |
|
| 7. |
AMD A6-9225 vs. AMD FX-4350 |
AMD A6-9225 vs. Intel Core i5-1035G4
AMD A6-9225
The AMD A6-9225 operates with 2 cores and 2 CPU threads. It run at 3.00 GHz base 2.60 GHz all cores while the TDP is set at 15 W.The processor is attached to the FP4 CPU socket. This version includes 2.00 MB of L3 cache on one chip, supports 1 memory channels to support DDR4-2133 RAM and features 3.0 PCIe Gen 8 lanes. Tjunction keeps below 90 °C degrees C. In particular, Stoney Ridge (Excavator) Architecture is enhanced with 28 nm technology and supports AMD-V. The product was launched on Q3/2018
Intel Core i5-1035G4
The Intel Core i5-1035G4 operates with 4 cores and 2 CPU threads. It run at 3.70 GHz base 3.30 GHz all cores while the TDP is set at 15 W.The processor is attached to the BGA 1526 CPU socket. This version includes 6.00 MB of L3 cache on one chip, supports 2 memory channels to support DDR4-3200, LPDDR4-3733 RAM and features 3. 0 PCIe Gen 16 lanes. Tjunction keeps below 100 °C degrees C. In particular, Ice Lake U Architecture is enhanced with 10 nm technology and supports VT-x, VT-x EPT, VT-d. The product was launched on Q3/2019
AMD A6-9225
Intel Core i5-1035G4
Compare Detail
| 2.60 GHz | Frequency | 1.10 GHz |
| 2 | Cores | 4 |
| 3.00 GHz | Turbo (1 Core) | 3.70 GHz |
| 2.60 GHz | Turbo (All Cores) | 3.30 GHz |
| No | Hyperthreading | Yes |
| No | Overclocking | No |
| normal | Core Architecture | normal |
|
AMD Radeon R4 (Stoney Ridge) |
GPU |
Intel Iris Plus Graphics (Ice Lake G4) |
| No turbo | GPU (Turbo) | 1.05 GHz |
| 28 nm | Technology | 10 nm |
| No turbo | GPU (Turbo) | 1. |
| 12 | DirectX Version | 12 |
| 3 | Max. displays | 3 |
| DDR4-2133 | Memory | DDR4-3200 LPDDR4-3733 |
| 1 | Memory channels | 2 |
| Max memory | ||
| No | ECC | No |
| — | L2 Cache | — |
| 2.00 MB | L3 Cache | 6.00 MB |
| 3.0 | PCIe version | 3.0 |
| 8 | PCIe lanes | 16 |
| 28 nm | Technology | 10 nm |
| FP4 | Socket | BGA 1526 |
| 15 W | TDP | 15 W |
| AMD-V | Virtualization | VT-x, VT-x EPT, VT-d |
| Q3/2018 | Release date | Q3/2019 |
|
Show more data |
Show more data |
Cinebench R23 (Single-Core)
Cinebench R23 is the successor of Cinebench R20 and is also based on the Cinema 4 Suite. Cinema 4 is a worldwide used software to create 3D forms. The single-core test only uses one CPU core, the amount of cores or hyperthreading ability doesn’t count.
Cinebench R23 (Multi-Core)
Cinebench R23 is the successor of Cinebench R20 and is also based on the Cinema 4 Suite. Cinema 4 is a worldwide used software to create 3D forms. The multi-core test involves all CPU cores and taks a big advantage of hyperthreading.
Cinebench R20 (Single-Core)
Cinebench R20 is the successor of Cinebench R15 and is also based on the Cinema 4 Suite. Cinema 4 is a worldwide used software to create 3D forms. The single-core test only uses one CPU core, the amount of cores or hyperthreading ability doesn’t count.
Cinebench R20 (Multi-Core)
Cinebench R20 is the successor of Cinebench R15 and is also based on the Cinema 4 Suite. Cinema 4 is a worldwide used software to create 3D forms. The multi-core test involves all CPU cores and taks a big advantage of hyperthreading.
Cinebench R15 (Single-Core)
Cinebench R15 is the successor of Cinebench 11.5 and is also based on the Cinema 4 Suite. Cinema 4 is a worldwide used software to create 3D forms. The single-core test only uses one CPU core, the amount of cores or hyperthreading ability doesn’t count.
Cinebench R15 (Multi-Core)
Cinebench R15 is the successor of Cinebench 11.5 and is also based on the Cinema 4 Suite. Cinema 4 is a worldwide used software to create 3D forms. The multi-core test involves all CPU cores and taks a big advantage of hyperthreading.
Geekbench 5, 64bit (Single-Core)
Geekbench 5 is a cross plattform benchmark that heavily uses the systems memory. A fast memory will push the result a lot. The single-core test only uses one CPU core, the amount of cores or hyperthreading ability doesn’t count.
Geekbench 5, 64bit (Multi-Core)
Geekbench 5 is a cross plattform benchmark that heavily uses the systems memory. A fast memory will push the result a lot. The multi-core test involves all CPU cores and taks a big advantage of hyperthreading.
iGPU — FP32 Performance (Single-precision GFLOPS)
The theoretical computing performance of the internal graphics unit of the processor with simple accuracy (32 bit) in GFLOPS. GFLOPS indicates how many billion floating point operations the iGPU can perform per second.
Estimated results for PassMark CPU Mark
Some of the CPUs listed below have been benchmarked by CPU-Comparison. However the majority of CPUs have not been tested and the results have been estimated by a CPU-Comparison’s secret proprietary formula. As such they do not accurately reflect the actual Passmark CPU mark values and are not endorsed by PassMark Software Pty Ltd.
Electric Usage Estimate
Average hours of use per day
Average CPU Utilization (0-100%)
Power cost, dollar per kWh
Electric Usage Estimate
Average hours of use per day
Average CPU Utilization (0-100%)
Power cost, dollar per kWh
| AMD A6-9225 | Intel Core i5-1035G4 | |
| 15 W | Max TDP | 15 W |
| NA | Power consumption per day (kWh) | NA |
| NA | Running cost per day | NA |
| NA | Power consumption per year (kWh) | NA |
| NA | Running cost per year | NA |
Popular Comparision
Comments
Compare AMD A6-9225 and Intel Core i5-4440
Comparative analysis of AMD A6-9225 and Intel Core i5-4440 processors by all known characteristics in the categories: General information, Performance, Memory, Graphics, Graphical interfaces, Graphics API support, Compatibility, Peripherals, Technologies, Virtualization, Image quality in graphics, Safety and reliability.
Processor performance analysis by benchmarks: PassMark — Single thread mark, PassMark — CPU mark, GFXBench 4.0 — Car Chase Offscreen (Frames), GFXBench 4.0 — Car Chase Offscreen (Fps), GFXBench 4.0 — Manhattan (Frames), GFXBench 4.0 — Manhattan ( Fps), GFXBench 4.0 — T-Rex (Frames), GFXBench 4.0 — T-Rex (Fps), CompuBench 1.5 Desktop — Face Detection (mPixels/s), Geekbench 4 — Single Core, Geekbench 4 — Multi-Core, 3DMark Fire Strike — Physics Score, CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s), CompuBench 1.5 Desktop — T-Rex (Frames/s), CompuBench 1.5 Desktop — Video Composition (Frames/s), CompuBench 1.5 Desktop — Bitcoin Mining ( mHash/s).
AMD A6-9225
versus
Intel Core i5-4440
Benefits
Reasons to choose AMD A6-9225
- Approx. vs 84 Watt
| Max Core Temp | 90°C vs 72. |
| Power consumption (TDP) | 15 Watt vs 84 Watt |
Reasons to choose Intel Core i5-4440
- 2 more cores, able to run more applications at the same time: 4 vs 2
- About 27% more clock speed: 3.30 GHz vs 2.6 GHz
- Newer manufacturing process processor allows it to be more powerful, but with lower power consumption: 22 nm vs 28 nm
- About 57% better performance in PassMark — Single thread mark benchmark: 1858 vs 1182
- 3.5 times better performance in PassMark — CPU mark benchmark: 4741 vs 1343
- Performance in CompuBench 1.5 Desktop — Face Detection benchmark (mPixels/s) 2.4 times larger: 3.29 vs 1.391
| Number of cores | 4 vs 2 |
| Maximum frequency | 3. |
| Process | 22 nm vs 28 nm |
| PassMark — Single thread mark | 1858 vs 1182 |
| PassMark — CPU mark | 4741 vs 1343 |
| CompuBench 1.5 Desktop — Face Detection (mPixels/s) | 3.29 vs 1.391 |
Benchmark comparison
CPU 1: AMD A6-9225
CPU 2: Intel Core i5-4440
| PassMark — Single thread mark |
|
|||
| PassMark — CPU mark |
|
|||
| CompuBench 1. |
|
| Name | AMD A6-9225 | Intel Core i5-4440 |
|---|---|---|
| PassMark — Single thread mark | 1182 | 1858 |
| PassMark — CPU mark | 1343 | 4741 |
| GFXBench 4.0 — Car Chase Offscreen (Frames) | 754 | |
| GFXBench 4. |
754 | |
| GFXBench 4.0 — Manhattan (Frames) | 1522 | |
| GFXBench 4.0 — Manhattan (Fps) | 1522 | |
| GFXBench 4.0 — T-Rex (Frames) | 4199 | |
| GFXBench 4.0 — T-Rex (Fps) | 4199 | |
| CompuBench 1.5 Desktop — Face Detection (mPixels/s) | 1.391 | 3.29 |
| Geekbench 4 — Single Core | 779 | |
| Geekbench 4 — Multi-Core | 2503 | |
| 3DMark Fire Strike — Physics Score | 2659 | |
| CompuBench 1. |
68.836 | |
| CompuBench 1.5 Desktop — T-Rex (Frames/s) | 0.368 | |
| CompuBench 1.5 Desktop — Video Composition (Frames/s) | 1.861 | |
| CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s) | 5.326 |
Performance comparison
| AMD A6-9225 | Intel Core i5-4440 | |
|---|---|---|
| Family | AMD A-Series Processors | |
| Production date | Q2 2018 | September 2013 |
| OPN Tray | AM9225AYN23AC | |
| OS Support | Windows 10 — 64-Bit Edition, RHEL x86 64-Bit, Ubuntu x86 64-Bit | |
| Place in the ranking | 1221 | 1722 |
| Series | AMD A6-Series APU for Laptops | 4th Generation Intel® Core™ i5 Processors |
| Applicability | Laptop | Desktop |
| Architecture name | Haswell | |
| Price at first issue date | $335 | |
| Price now | $169. |
|
| Processor Number | i5-4440 | |
| Status | Discontinued | |
| Price/performance ratio (0-100) | 11.25 | |
| Base frequency | 3.1 GHz | 3.10 GHz |
| Compute Cores | 5 | |
| Level 2 cache | 1MB | 256 KB (per core) |
| Process | 28nm | 22nm |
| Maximum core temperature | 90°C | 72. |
| Maximum frequency | 2.6 GHz | 3.30 GHz |
| Number of cores | 2 | 4 |
| Number of GPU cores | 3 | |
| Unlocked | ||
| Support 64 bit | ||
| Bus Speed | 5 GT/s DMI2 | |
| Crystal area | 177mm | |
| Level 1 cache | 64 KB (per core) | |
| Level 3 cache | 6144 KB (shared) | |
| Maximum case temperature (TCase) | 72 °C | |
| Number of threads | 4 | |
| Number of transistors | 1400 million | |
| Maximum number of memory channels | 1 | 2 |
| Supported memory frequency | 2133MHz | |
| Maximum memory bandwidth | 25. |
|
| Maximum memory size | 32GB | |
| Supported memory types | DDR3-1333/1600, DDR3L-1333/1600 @ 1.5V | |
| Enduro | ||
| Maximum GPU clock | 686MHz | 1.1 GHz |
| Integrated graphics | AMD Radeon R4 Graphics | Intel® HD Graphics 4600 |
| Switchable graphics | ||
| Unified Video Decoder (UVD) | ||
| Video Codec Engine (VCE) | ||
| Device ID | 0x412 | |
| Graphics base frequency | 350 MHz | |
| Graphics max dynamic frequency | 1. |
|
| Intel® Clear Video HD Technology | ||
| Intel® Flexible Display Interface (Intel® FDI) | ||
| Intel® InTru™ 3D Technology | ||
| Intel® Quick Sync Video | ||
| Video memory size | 2GB | |
| DisplayPort | ||
| HDMI | ||
| eDP | ||
| Maximum number of monitors supported | 3 | |
| VGA | ||
| WiDi support | ||
| DirectX | 12 | 11. |
| Vulcan | ||
| OpenGL | 4.3 | |
| Configurable TDP | 10-15 Watt | |
| Power consumption (TDP) | 15 Watt | 84 Watt |
| Low Halogen Options Available | ||
| Maximum number of processors in configuration | 1 | |
| Package Size | 37.5mm x 37.5mm | |
| Supported sockets | FCLGA1150 | |
| Thermal Solution | PCG 2013D | |
| PCI Express revision | 3. |
Up to 3.0 |
| Number of PCI Express lanes | 16 | |
| PCIe configurations | Up to 1×16, 2×8, 1×8+2×4 | |
| Scalability | 1S Only | |
| Adaptive Voltage and Frequency Scaling (AVFS) | ||
| AMD App Acceleration | ||
| AMD HD3D technology | ||
| AMD Mantle API | ||
| DualGraphics | ||
| Fused Multiply-Add 4 (FMA4) | ||
| Intel® AES New Instructions | ||
| Enhanced Intel SpeedStep® Technology | ||
| Flexible Display interface (FDI) | ||
| Idle States | ||
| Extended instructions | Intel® SSE4. |
|
| Intel 64 | ||
| Intel® Advanced Vector Extensions (AVX) | ||
| Intel® Hyper-Threading Technology | ||
| Intel® My WiFi Technology | ||
| Intel® Stable Image Platform Program (SIPP) | ||
| Intel® TSX-NI | ||
| Intel® Turbo Boost Technology | ||
| Intel® vPro™ Platform Eligibility | ||
| Thermal Monitoring | ||
| AMD Virtualization (AMD-V™) | ||
| Intel® Virtualization Technology (VT-x) | ||
| Intel® Virtualization Technology for Directed I/O (VT-d) | ||
| Intel® VT-x with Extended Page Tables (EPT) | ||
| Maximum resolution via DisplayPort | [email protected] | |
| Maximum resolution via eDP | [email protected] | |
| Maximum resolution via HDMI 1. |
[email protected] | |
| Maximum resolution via VGA | [email protected] | |
| Anti-Theft Technology | ||
| Execute Disable Bit (EDB) | ||
| Intel® Identity Protection Technology | ||
| Intel® OS Guard | ||
| Intel® Secure Key Technology | ||
| Intel® Trusted Execution Technology (TXT) |
AMD A6-9225 vs.
Intel Core i5-7200U
AMD A6-9225
AMD A6-9225 runs with 2 and 2 CPU threads It runs at 3.00 GHz base 2.60 GHz all cores while TDP is set to 15 W .CPU connects to CPU socket FP4 This version includes 2.00 MB of L3 cache on a single die, supports 1 to support DDR4-2133 RAM, and supports 3.0 PCIe Gen 8 . Tjunction keeps below 90 °C degrees C. In particular, the Stoney Ridge (Excavator) architecture has been advanced over 28 nm and supports AMD-V . The product was launched Q3/2018
Intel Core i5-7200U
Intel Core i5-7200U runs with 2 and 2 CPU threads It runs at 3.10 GHz base 3.10 GHz all cores while TDP is set to 15 W .CPU connects to BGA 1356 CPU socket This version includes 3.00 MB of L3 cache on a single die, supports 2 to support DDR4-2133 SO-DIMM RAM, and supports 3.0 PCIe Gen 12 . Tjunction is kept below — degrees C. In particular, Kaby Lake U architecture is advanced over 14 nm and supports VT-x, VT-x EPT, VT-d . The product was launched Q4/2016
AMD A6-9225
Intel Core i5-7200U
AMD Radeon R4 (Stoney Ridge)
Intel HD Graphics 620
Show more details
Show more details
Cinebench R23 (Single-Core)
Cinebench R23 is the successor to Cinebench R20 and is also based on Cinema 4 Suite. Cinema 4 is software used all over the world to create 3D shapes. The single-core test uses only one CPU core, the number of cores or hyper-threading capability is not taken into account.
Cinebench R23 (Multi-Core)
Cinebench R23 is the successor to Cinebench R20 and is also based on Cinema 4 Suite. Cinema 4 is software used all over the world to create 3D forms. The multi-core test uses all the CPU cores and has a big advantage of hyper-threading.
Cinebench R20 (Single-Core)
Cinebench R20 is the successor to Cinebench R15 and is also based on Cinema 4 Suite. Cinema 4 is software used all over the world to create 3D forms. The single-core test uses only one CPU core, the number of cores or hyper-threading capability is not taken into account.
Cinebench R20 (Multi-Core)
Cinebench R20 is the successor to Cinebench R15 and is also based on the Cinema 4 Suite. Cinema 4 is software used all over the world to create 3D forms. The multi-core test uses all the CPU cores and has a big advantage of hyper-threading.
Cinebench R15 (Single-Core)
Cinebench R15 is the successor to Cinebench 11.5 and is also based on the Cinema 4 Suite. Cinema 4 is software used all over the world to create 3D forms. The single-core test uses only one CPU core, the number of cores or hyper-threading capability is not taken into account.
Cinebench R15 (Multi-Core)
Cinebench R15 is the successor to Cinebench 11.5 and is also based on Cinema 4 Suite. Cinema 4 is software used all over the world to create 3D forms. The multi-core test uses all the CPU cores and has a big advantage of hyper-threading.
Geekbench 5, 64bit (Single-Core)
Geekbench 5 is a memory-intensive, cross-platform test. A fast memory will greatly push the result. The single-core test uses only one CPU core, the number of cores or hyper-threading capability is not taken into account.
Geekbench 5, 64bit (Multi-Core)
Geekbench 5 is a memory-intensive, cross-platform test. A fast memory will greatly push the result. The multi-core test uses all the CPU cores and has a big advantage of hyper-threading.
iGPU — FP32 Performance (Single-precision GFLOPS)
Theoretical processing performance of the processor’s internal graphics unit with simple precision (32 bits) in GFLOPS. GFLOPS specifies how many billions of floating point operations the iGPU can perform per second.
Blender 2.81 (bmw27)
Blender is a free 3D graphics software for rendering (creating) 3D bodies that can also be textured and animated in the program. The Blender test creates predefined scenes and measures the time(s) required for the entire scene. The less time it takes, the better. We chose the bmw27 as our reference scene.
Geekbench 3, 64bit (Single-Core)
Geekbench 3 is a cross-platform benchmark that is memory intensive. A fast memory will greatly push the result. The single-core test uses only one CPU core, the number of cores or hyper-threading capability is not taken into account.
Geekbench 3, 64bit (Multi-Core)
Geekbench 3 is a cross-platform benchmark that is memory intensive. A fast memory will greatly push the result. The multi-core test uses all the CPU cores and has a big advantage of hyper-threading.
Cinebench R11.
5, 64bit (Single-Core)
Cinebench 11.5 is based on the Cinema 4D Suite, a software that is popular for creating shapes and other things in 3D. The single-core test uses only one CPU core, the number of cores or hyper-threading capability is not taken into account.
Cinebench R11.5, 64bit (Multi-Core)
Cinebench 11.5 is based on Cinema 4D Suite, a software that is popular for creating shapes and other things in 3D. The multi-core test uses all the CPU cores and has a big advantage of hyper-threading.
Cinebench R11.5, 64bit (iGPU, OpenGL)
Cinebench 11.5 is based on Cinema 4D Suite, a software that is popular for creating shapes and other things in 3D. The iGPU test uses the CPU’s internal graphics unit to execute OpenGL commands.
Estimated results for PassMark CPU Mark
Some of the processors listed below have been tested with CPU-Comparison. However, most of the processors were not tested and the results were evaluated by the secret patented CPU-Comparison formula. As such, they do not accurately reflect the actual values of Passmark CPU ratings and are not endorsed by PassMark Software Pty Ltd.
Energy usage estimate
Average hours of use per day
Average CPU usage (0-100%)
Cost of electricity, USD/kWh
Energy usage estimate
Average hours of use per day
Average CPU usage (0-100%)
Cost of electricity, USD/kWh
| AMD A6-9225 | Intel Core i5-7200U | |
| 15 W | Max TDP | 15W |
| NA | Power consumption per day (kWh) | NA |
| NA | Operating cost per day | NA |
| NA | Power consumption per year (kWh) | NA |
| NA | Operating cost per year | NA |
Popular comparison
Comments0001
VS
AMD A6-9225
Intel Core i5-4210U
Which one to choose?
It’s time to choose the winner. What is the difference and which is better in AMD A6-9225 vs Intel Core i5-4210U comparison? Which processor is more powerful and faster? It is quite simple to determine — look at the comparative table of all characteristics. A processor with more cores/threads, as well as a higher frequency and large L2-L3 is the absolute winner!
Cores, base and turbo frequency of the processor
Who will win in the comparison of AMD A6-9225 and Intel Core i5-4210U. The overall performance of a processor can be easily determined based on the number of cores, threads, base and turbo clock speed + L2-L3 volume. The more cores, L3, and clock speed, the more efficient the processor. Please note that high specifications require the use of a powerful cooling system.
2.60 GHz
Clock frequency
1.70 GHZ
2
Number of nuclei
2
3.00 GHZ
turbo (1 core)
2.70 GHZ
2
Number
2.35 GHZ
No
Hypertureuding
YES
NO
Acceleration
NO
Family and generation of the processor
Internal graphics
It is difficult to compare AMD A6-99999225 against the Intel Core i5-4210U when the function and performance of the graphics card only matters in laptops. In workstations, this is not an advantage, due to the installation of an additional graphics accelerator.
AMD Radeon R4 (Stony Ridge)
Name GPU
Intel HD Graphics 4400
0.66 GHZ
Frequency GPU
0.20 GHZ
NO TURBO
1.000 GPU
1.00 GPU (TURBO)
1.00 GPU (TURBO)
1.00 GPU (TURBO) Generation
7.5
12
version DirectX
11.1
3
Executive blocks
20,0002
160
GB
Maximum memory
9000 2 gb
9000 2 9000 2
Number of monitors
3
28 nm
Technology
22 nm
Q2/2016
Release date
Q2/2013
Codec support
0015
Here we are dealing with specifications that are used by some processor manufacturers. These figures are mostly technical and can be disregarded for comparative purposes.
Decode
h364
Decode / Encode
Decode / Encode
JPEG
Decode
Decode
h365 8bit
No
Decode
h365 10bit
No
Decode
VP8
DDR3L-1600 SO-DIMM
8 GB
Maximum memory
1
Memory channels
2
NO
ECC
No.
9000 3.0
version PCIe
2.0
9000 9000 9000 9000 Memory & AMP; PCIe
Thermal management and TDP
Today’s systems are loaded with demanding games and work applications, which consequently unleash the full potential of the processor. When choosing between AMD A6-9225 and Intel Core i5-4210U, it is better to choose the option with less heat dissipation (TDP).
15 W
TDP
15 W
90 ° C
Maximum temperature
—
—
0002-
Technical details
2.00 MB
L3-CACHE
3.00 MB
28 NM
Technology
22 22 NM
Stony Ridge
Architecture
HASWEL RED -V, AMD-VI
Virtualization
VT-X, VT-X EPT, VT-D
FP4
SOCK (connector)
BGA 1168
Q3/2018
Output
/2014
Price
ca. 185 $
Devices compatible with this processor
You probably already know which devices use processors. It can be a desktop computer or a laptop.
Unknown
Used in
Unknown
Cinebench R11.5, 64bit (Single-Core)
This synthetic benchmark will help you determine the actual processing power of a single CPU core. Cinebench R11.5 is based on MAXON CINEMA 4D and uses 9 different test scenarios0003
AMD A6-9225
2x 2.60 GHz (3.00 GHz)
Intel Core i5-4210U
2x 1.70 GHz (2.70 GHz) HT
107 (100%)
Cinebench R11.5, 64bit (Multi-Core)
Cinebench R11.5 performs simultaneous cross-platform tests on all processor cores. Running realistic 3D scenes, this benchmark will unleash the full potential of your single-core Intel or AMD
processor
AMD A6-9225
2x 2. 60 GHz (3.00 GHz)
Intel Core i5-4210U
2x 1.70 GHz (2.70 GHz) HT
241 (100%)
Cinebench R11.5, 64bit (iGPU, OpenGL)
Cinebench 11.5 is based on Cinema 4D Suite, a popular software for creating shapes and other things in 3D. The iGPU test uses the processor’s internal graphics unit to execute OpenGL commands.
AMD A6-9225
2x 2.60 GHz (3.00 GHz)
Intel Core i5-4210U
2x 1.70 GHz (2.70 GHz) HT
148 (100%)
Cinebench R15 (Single Core)
The latter is used to create 3D models and shapes. Cinebench R15 is used to benchmark the performance of single core processors. Hyperthreading capability is not taken into account. It is an updated version of Cinebench 11.5. Like all new versions, the updated benchmark is based on Cinema 4 Suite software
AMD A6-9225
2x 2.60 GHz (3.00 GHz)
Intel Core i5-4210U
2x 1.70 GHz (2.70 GHz) HT
92 (100%)
Cinebench R15 (Multi-Core)
Cinebench R15 can be used to test the performance of multi-core processors. The test produces accurate and reliable results. This benchmark is an updated version of Cinebench 11.5, which is based on Cinema 4 Suite soft.
AMD A6-9225
2x 2.60 GHz (3.00 GHz)
Intel Core i5-4210U
2x 1.70 GHz (2.70 GHz) HT
236 (100%)
Cinebench R20 (Single Core)
Cinebench R20 is based on Cinema 4 Suite. This is software used to create 3D shapes. The benchmark runs in single-core mode without considering the possibility of hyper-threading.
AMD A6-9225
2x 2.60 GHz (3.00 GHz)
182 (90%)
Intel Core i5-4210U
2x 1. 70 GHz (2.70 GHz) HT
202 (100%)
Cinebench R20 (Multi-Core)
This is a new version of the benchmark based on Cinebench R15 (both versions are based on Cinema 4, the most popular 3D modeling software). Cinebench R20 is used for benchmark tests of multi-core processor performance and hyper-threading capability.
AMD A6-9225
2x 2.60 GHz (3.00 GHz)
273 (60%)
Intel Core i5-4210U
2x 1.70 GHz (2.70 GHz) HT
449 (100%)
Geekbench 3, 64bit (Single-Core)
Geekbench 3 is a benchmark for 64-bit Intel and AMD processors. It uses a new power rating system for a single processor core. This software simulates real scenarios for accurate results
AMD A6-9225
2x 2.60 GHz (3.00 GHz)
Intel Core i5-4210U
2x 1.70 GHz (2.70 GHz) HT
2544 (100%)
Geekbench 3, 64bit (Multi-Core)
Geekbench 3 supports multi-core AMD and Intel processors. Being based on MAXON CINEMA 4D, it allows you to get the real comparative potential of the processor
AMD A6-9225
2x 2.60 GHz (3.00 GHz)
Intel Core i5-4210U
2x 1. 70 GHz (2.70 GHz) HT
4659 (100%)
Geekbench 5, 64bit (Single-Core)
Geekbench 5 is the latest software. Completely new algorithms provide fairly accurate test results for single-core processors.
AMD A6-9225
2x 2.60 GHz (3.00 GHz)
Intel Core i5-4210U
2x 1.70 GHz (2.70 GHz) HT
547 (100%)
Geekbench 5, 64bit (Multi-Core)
Geekbench 5 software package shows benchmark results for memory performance and multi-core processor speed. This takes into account the ability to hyperthreading.
AMD A6-9225
2x 2. 60 GHz (3.00 GHz)
Intel Core i5-4210U
2x 1.70 GHz (2.70 GHz) HT
1150 (100%)
Estimated results for PassMark CPU Mark
It tests all and general CPU performance (math calculations, compression and decompression speed, 2D&3D graphics tests). Please note that data may differ from actual situations.
AMD A6-9225
2x 2.60 GHz (3.00 GHz)
2115 (61%)
Intel Core i5-4210U
2x 1.70 GHz (2.70 GHz) HT
3431 (100%)
iGPU — FP32 Performance (Single-precision GFLOPS)
This test measures the performance of integrated graphics on Intel and AMD processors. The result is the calculated processing power in Single-Precision mode FP32
AMD A6-9225
2x 2.60 GHz (3.00 GHz)
251 (78%)
Intel Core i5-4210U
2x 1.70 GHz (2.70 GHz) HT
320 (100%)
Popular processor comparisons
| one. |
AMD A6-9225 vs. Intel Core i5-4210U |
|
|
2. |
AMD A6-9225 vs. Intel Core i7-1165G7 |
|
| 3. |
AMD A6-9225 vs. Intel Celeron J4115 |
|
| four. |
AMD A6-9225 vs. Intel Core i5-6300U |
|
| 5. |
AMD A6-9225 vs. Intel Core i3-3240 |
|
| 6. |
Intel Celeron N4020 vs. AMD A6-9225 |
|
|
7. |
AMD A6-9225 vs. Intel Core i3-6157U |
|
| eight. |
AMD A6-9225 vs. AMD A8-7650K |
|
| 9. |
AMD A6-9225 vs. Intel Core i7-1185G7 |
|
| ten. |
AMD A6-9225 vs. Intel Core i7-5500U |
|
| eleven. |
AMD A6-9225 vs. AMD FX-4350 |
|
|
12. |
AMD A6-9225 vs. AMD A10-8700P |
|
| 13. |
AMD A6-9225 vs. AMD Ryzen 5 PRO 4650G |
|
| fourteen. |
AMD A6-9225 vs. Intel Core i5-3470S |
|
| fifteen. |
AMD A6-9225 vs. Intel Pentium 997 |
AMD A6-9225 vs Intel Core i3-2357M processor comparison in 4 benchmarks nm — 1.30 GHz DDR3-1066
DDR3-1333
AMD A6-9225
Intel Core i3-2357M
AMD A6-9225 vs. Intel Core i3-2357M
Processor cores and base frequency
When comparing AMD A6-9225 and Intel Core i3-2357M, you should choose a model with more cores and threads with base and turbo frequencies. All functions affect system performance.
2x
Colors
No data
2 /2
Streams of processor
2/4
Normal
Basic architecture
NO
NO
Hyper Acceleration
No
2.60 GHZ
Frequency
1.30 GHZ
3.00 GHZ
turbo (1 core)
NO TURBO
2.60 GHZ
turbo (2 nuclei)
No TURBO
AMD A625 vs. Intel Core i3-2357M
Generation and family CP
2
Processor nuclei
2
AMD A6-9225
Name
No data
AMD A
No data
9,000
AMD A6-9000
Group CP
No data
7
Generation
6
Mobile
Segment
n/a
AMD A6-9225 vs. Intel Core i3-2357M
Internal graphics
Some manufacturers include a graphics core in many processors, which is an added benefit. If you are using a graphics card separated from the CPU, we recommend skipping this comparison as there is no need to compare AMD A6-9225 with Intel Core i3-2357M for integrated graphics. AMD Radeon R4 (Stony Ridge)
Graphic processor Name
Intel HD Graphics 3000
0.66 GHZ
0.35 GHZ
NO TURBO
GP (turbo)
GP (turbo)
GP (turbo) Max. GPU memory
n/a
3
Max. Displays
2
7
Generation
6
12
Direct X
10.1
28 28 NM
Technology
32 nm
Q2/2016
Date of release
9000 q1/2011
AMD A6-9225 vs. Intel Core i3-2357M
Hardware codec support
Please note the support of various technology options by processors. Does not affect overall performance. In the interest of saving time, you can skip this section.
Decode
H365 8 bits
No.
Decode
H365 10 bits
NO
Decode
H365/HEVC (8 bits)
decode
H365/Hev)
No data
Decode
H364
Decode / Encode
Decode
VP8
NO
Decode
NO
No
9000 9000 9000 9000 20003
Decode / Encode
AVC
Decode / Encode
Decode
-1
Decode
Decode / Encode
JPEG
No
AMD A6-9225 vs.
Intel Core i3-2357M
RAM and PCIe
Modern processors support multi-channel memory for fast data transfer and improved performance. The higher the clock speed of the RAM, its standard (for example, DDR3, DDR4, DDR5) and the maximum amount in the system, the better it is.
3.0
PCI version
2.0
8
PCIe lanes
16
DDR3-1333
8 GB
Max. Memory
16 GB
1
002 Yes
AES-NI
No
AMD A6-9225 vs. Intel Core i3-2357M
Thermal management
High performance and powerful processors require a good power supply. Here you will find out how many TDPs AMD A6-9225 and Intel Core i3-2357M have. We recommend to pay attention to the model with a lower TDP.
15 W
Rated power
17 W
15 W
Rated power (PL1)
n/a
—
Settlement capacity (PL2)
No data
—
TDP up
—
10 W
TDP
—
90 ° C
Max compound.
100°C
AMD A6-9225 vs. Intel Core i3-2357M
Technical Details
Here is the basic information that can determine the best processor by comparing specifications. Thus, the higher the L2 and L3 cache, the better. The lower the CPU manufacturing process, the better it is. An important factor is the year of manufacture, which directly affects the terms of support by the manufacturer and the possibility of upgrading the system with minimal costs in the future.
x86-64 (64 bit)
Instruction set (ISA)
n.a.
L2-kesh
No data
2.00 MB
L3-Kash
3.00 MB
Stony Ridge (Excavator)
Sandy Bridge
28 NM
Technology
9000 32 NM 9000. V, AMD-Vi
Virtualization
VT-X, VT-X EPT
FP4
SOCKET
BGA 1023
Q3/2018
Date of release
/2011
—
Number
No data
AMD A6 AMD A6 -9225 vs. Intel Core i3-2357M
Devices that use this processor
After completing the comparison between AMD A6-9225 and Intel Core i3-2357M, you can find out which computer systems use these models.
Unknown
Used in
Unknown
Popular comparisons with these processors
| one. |
AMD A6-9225 vs. AMD A8-7650K |
|
| 2. |
AMD A6-9225 vs. Intel Celeron J4115 |
|
|
3. |
AMD A6-9225 vs. Intel Core i5-6300U |
|
| four. |
AMD A6-9225 vs. Intel Core i7-1185G7 |
|
| 5. |
AMD A6-9225 vs. Intel Core i3-3240 |
|
| 6. |
AMD A6-9225 vs. AMD FX-4350 |
|
| 7. |
AMD A6-9225 vs. Intel Core i7-5500U |
Processor AMD A6-9225 — features, prices, tests » BNAME.
RU
Processor search
A6-9225
Compare A6-9225
Main information
Brand
AMD
Family of processors
A-Series
Processor line
A6
9000 9000 9000 $ 9000 $ 9000 $ 9000 $
Processor type
Mobile
Purpose
for laptops
Date of exit
June 1, 2018
Main Harcatericism
Number
2 Nuclei
Streams
2 Streams
SOCKET (connector)
SOCKET FT4
Architecture 9000 9000 9000 STONE Ridge
Base frequency
2600 MHz
Auto overclock
Yes
Maximum frequency
3000 MHz
Free processor multiplier
no
processor
Technological process
28 nm
transistors (millions)
1200 million
Crystal size
124. 5 9000 L1 cache
96 + 2×32 Kb
L2 level 2 cache
1024 Kb
L3 level 3 cache
no Kb
RAM controller
3
There are
Types of RAM
DDR4
memory channels
1
Support for peripheral devices
version of PCI Express
3.03
Lines PCIE
8
Support SSD SSD SSD Support Support
M.2 SSD support
Integrated video adapter
GPU
AMD Radeon R4 (Stoney Ridge)
Speed rating A6-9225
Attention! The general rating calculation method is chosen, which means that the rating percentage is calculated relative to the most powerful processor participating on our site.
Rating calculation method:
Overall ratingBy Stoney Ridge architectureBy socket FT4Among Intel processorsAmong AMD processorsAmong mobile processorsAmong A-series processorsAmong A6-series processorsAmong 2-core processorsAmong 2017 processors
General performance rating
1620. 22
(1.53%)
Passmark CPU Mark
1337
(1.52%)
Cinebench 10 (32 bits) single -test test 9000 2532
(24 01%)
Cinebench 10 (32 bits) Multipotive test
4193
(6.76%)
Cinebench 11.5 (64-bit) Multipoque test
1.2
(1.13%)
Cinebench 11.5 (64-bit) Single thread test
0.85
(9.83%)
Cinebench 15 (64-bit) Multipotive test
109
(1.03%)
Cinebench 15 (64-bit) single-circuit test
9000 73
(21 .78%)
Geekbench 4.0 (64-bit) Multi-threaded test
3035
(1.64%)
Geekbench 4.0 (64-bit) Single-threaded test
1920
3 1.64% Geekbench 3 (32bit) Multi-threaded test
3103
(3.83%)
Geekbench 3 (32 bits) Single -Test Test
1855
(38.05%)
Geekbench 2
3936
(9,04%)
x264 HD 4.0 Pass 1
9000 49
(1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1IOUA 89%)
x264 HD 4. 0 Pass 2
9,0003
(1.46%)
3dmark06 CPU
2132
(1.49%)
WinRAR 4.0
852
(1.43% )
TrueCrypt AES
1
(3.85%)
Positions in rating
Attention! The general rating calculation method is chosen, which means that the rating percentage is calculated relative to the most powerful processor participating on our site.
Rating calculation method:
Overall ratingBy Stoney Ridge architectureBy socket FT4Among Intel processorsAmong AMD processorsAmong mobile processorsAmong A-series processorsAmong A6-series processorsAmong 2-core processorsAmong 2017 processors
The total performance rating
in the ranking is involved ) Single-threaded test
739 processors
288th place
(out of 739)
Cinebench 10 (32 bit) Multi-threaded test
723 processors 9 participate in the rating0003
182 Place
(out of 723)
Cinebench 11. 5 (64-bit) multipropoped test
in the ranking 3221 processor
843 place
(out of 3221)
Cinebench 11.5 (64-bit) single-flow Test
V. The rating is participated in 3215 processors
1692 place
(out of 3215)
Cinebench 15 (64-bit) multipropoped test
in the ranking 3218 processors
861 place
(out of 3218)
Cinebench 15 (64-Byt) (64-Byt) Single Thread Test
The ranking is involved in 3217 processors
1554 place
(out of 3217)
Geekbench 4.0 (64-bit) Multipotive test
In the ranking, 3209 processors
1003 place
(out of 3209)
9000 Geekbench 4.0 (64- bit) Single-threaded test
3209 processors participate in the rating
1310 place
(out of 3209)
Geekbench 3 (32 bit) Multi-threaded test
232 processors participate in the rating
36th place
(out of 232)
Geekbench 3 (32 bits) Single -Treaty Test
In the ranking 232 processors
66 place
(from 232)
Geekbench 2
The ranking is involved in 197 processors
59 place
(from from 197)
x264 HD 4. 0 Pass 1
The ranking is involved in the ranking 3211 processors
1305 place
(out of 3211)
x264 HD 4.0 Pass 2
The ranking is participated in the ranking 3211 processors
1121 place
9000
002 (out of 3211)
3dmark06 CPU
The ranking is participated in the rating 3242 processor
1138 place
(out of 3242)
Winrar 4.0
in the ranking 3212 processors
906
457 processors participate in the rating
102nd place
(out of 457)
| Name of technology or instruction | Meaning | Short description |
|---|---|---|
| Turbo Core | AMD Auto Overclocking Technology . |
| Technology or instruction name | Meaning | Short description |
|---|---|---|
| PowerNow! | PowerNow! idle frequency reduction technology. |
| Technology or instruction name | Meaning | Short description |
|---|---|---|
| MMX (Multimedia Extensions) | Multimedia extensions. | |
| SSE (Streaming SIMD Extensions) | Streaming SIMD processor extension. | |
| SSE2 (Streaming SIMD Extensions 2) | Processor Streaming SIMD Extension 2. | |
| SSE3 (Streaming SIMD Extensions 3) | Streaming SIMD Processor Extension 3. | |
| SSSE3 (Supplemental Streaming SIMD Extension 3) | Additional SIMD extensions for streaming 3. | |
| SSE4 (Streaming SIMD Extensions 4) | Processor Streaming SIMD Extension 4. |
|
| AES (Intel Advanced Encryption Standard New Instructions) | Command system extension. | |
| AVX (Advanced Vector Extensions) | Command system extension. | |
| F16C (16-bit Floating-Point conversion) | 16-bit floating point conversion. | |
| FMA3 (Fused Multiply-Add 3) | Multiply Add with Round One (FMA3). | |
| SSE4A (Streaming SIMD Extensions 4A) | Processor 4A streaming SIMD extension. | |
| AVX 2 (Advanced Vector Extensions 2) | Command extension 2. | |
| BMI1 (Bit manipulation instructions 1) | BMI1 bit control command set. | |
| AMD64 | 64-bit microprocessor architecture developed by AMD. |
|
| FMA4 (Fused Multiply-Add 4) | Multiply Add with Round One (FMA4). | |
| XOP (eXtended Operations) | Advanced operations. |
| Name of technology or instruction | Meaning | Short description |
|---|---|---|
| EVP (Enhanced Virus Protection) | Improved virus protection. |
| Technology or instruction name | Meaning | Short description |
|---|---|---|
| AMD-V | AMD-V Virtualization Technology. |
| Technology or instruction name | Meaning | Short description |
|---|---|---|
| TBM (Trailing Bit Manipulation) | End bit manipulation. |
AMD A6-9225 Processor Overview
The A6-9225 belongs to the AMD mobile CPU series based on the Stoney Ridge microarchitecture. It began to be produced in stores on June 1, 2018.
The processor has built-in support for PCI Express, thanks to which you have the ability to install a variety of peripherals. The installed PCI bus controller version 3.0 supports 8 lanes. PCI-e version 3.0 allows you to install an NVMe SSD through the corresponding slot in the motherboard of a PCI card, U.2 or M.2.
Boasts integrated AMD Radeon R4 (Stoney Ridge) graphics. The processor is installed on motherboards with Socket FT4. With a manufacturing process of 28 Nm, the total number of transistors is 1200 million. The maximum temperature threshold at the highest load reaches 90°C.
The frequency of 2600 MHz per core is enough for many primary tasks of a computer user. And the new auto-overclocking mode will make this processor much more productive by significantly raising the core frequency from 2600 to 3000 MHz.
Budget processor manufactured in 2017, will perfectly prove itself in office activities, work and study. A6-9225 and today does not lose its relevance.
Competitors and analogues
Model 39 should be noted among competitors from INTEL65U on socket BGA1356 among Celeron processor series, more recent model of Pentium 4425Y processor, Pentium 3825U of 2015, newer Celeron N4000C processor, model 4415Y BGA1515 from Pentium family, N4020 BGA1090 model from Celeron processor series can be added here. On the Socket FT4 socket, AMD models should be singled out among the rivals: A4-9125 of 2017, model 9425 on the socket FT4 among the A9 processor series, model 7350B from the PRO A6 line, model 9220C Socket FT4 from the A6 processor family, model 9430 on Socket FT4 among the 2016 A9, A6-9230 processor family.
Other models that have the same graphics card as A6-9225 — model 9220 among the A6 processor series, model 9220e among the A6 processor series. Nevertheless, the productive processor with an integrated Radeon R4 (Stoney Ridge) video system is the A6-9225.