AMD A6-5200 vs Intel Core i5-4200U: What is the difference?
30points
AMD A6-5200
33points
Intel Core i5-4200U
Comparison winner
vs
64 facts in comparison
AMD A6-5200
Intel Core i5-4200U
Why is AMD A6-5200 better than Intel Core i5-4200U?
- 2.5x faster CPU speed?
4 x 2GHzvs2 x 1.6GHz - 425MHz faster GPU clock speed?
625MHzvs200MHz - 1.5MB bigger L2 cache?
2MBvs0.5MB - 128KB bigger L1 cache?
256KBvs128KB - 0.3 newer version of OpenGL?
4.3vs4
Why is Intel Core i5-4200U better than AMD A6-5200?
- 6nm smaller semiconductor size?
22nmvs28nm - Uses multithreading?
- 125MHz faster GPU turbo speed?
1000MHzvs875MHz - 0.1 newer version of OpenCL?
1.2vs1.1
- Has NX bit?
- Has FMA3?
Which are the most popular comparisons?
AMD A6-5200
vs
Intel Core i5-3337U
Intel Core i5-4200U
vs
Intel Celeron N3060
AMD A6-5200
vs
Intel Core i5-2537M
Intel Core i5-4200U
vs
Intel Core i3-7100
AMD A6-5200
vs
Intel Core i3-2348M
Intel Core i5-4200U
vs
AMD A6-5350M
AMD A6-5200
vs
Intel Core i3-3110M
Intel Core i5-4200U
vs
Intel Celeron N3350
AMD A6-5200
vs
Intel Core i7-7700HQ
Intel Core i5-4200U
vs
AMD A8-5550M
AMD A6-5200
vs
Intel Core i3-3227U
Intel Core i5-4200U
vs
Intel Core i5-1135G7
AMD A6-5200
vs
AMD A4-5000
Intel Core i5-4200U
vs
AMD A10-5750M
AMD A6-5200
vs
Intel Celeron N4020
Intel Core i5-4200U
vs
Intel Celeron N4020
AMD A6-5200
vs
Intel Core i3-2377M
Intel Core i5-4200U
vs
Intel Pentium G3430
Price comparison
User reviews
Performance
1.
CPU speed
4 x 2GHz
2 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
Unknown. Help us by suggesting a value. (AMD A6-5200)
2.6GHz
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-5200
✖Intel Core i5-4200U
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-5200)
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.25MB/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-5200)
1.5MB/core
More data can be stored in the L3 cache for access by each core of the CPU.
Memory
1.RAM speed
Unknown. Help us by suggesting a value. (AMD A6-5200)
1600MHz
It can support faster memory, which will give quicker system performance.
2.maximum memory bandwidth
Unknown. Help us by suggesting a value. (AMD A6-5200)
25.6GB/s
This is the maximum rate that data can be read from or stored into memory.
3.DDR memory version
Unknown. Help us by suggesting a value. (AMD A6-5200)
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
Unknown. Help us by suggesting a value. (AMD A6-5200)
More memory channels increases the speed of data transfer between the memory and the CPU.
5.maximum memory amount
Unknown. Help us by suggesting a value. (AMD A6-5200)
The maximum amount of memory (RAM) supported.
6.bus transfer rate
Unknown. Help us by suggesting a value. (AMD A6-5200)
Unknown.
Help us by suggesting a value. (Intel Core i5-4200U)
The bus is responsible for transferring data between different components of a computer or device.
7.Supports ECC memory
✖AMD A6-5200
✖Intel Core i5-4200U
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-5200)
Unknown. Help us by suggesting a value. (Intel Core i5-4200U)
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-5200)
Unknown. Help us by suggesting a value. (Intel Core i5-4200U)
The bus is responsible for transferring data between different components of a computer or device.
Benchmarks
1.PassMark result
Unknown. Help us by suggesting a value. (AMD A6-5200)
This benchmark measures the performance of the CPU using multiple threads.
2.PassMark result (single)
Unknown. Help us by suggesting a value. (AMD A6-5200)
This benchmark measures the performance of the CPU using a single thread.
3.Geekbench 5 result (multi)
Unknown. Help us by suggesting a value. (AMD A6-5200)
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. (AMD A6-5200)
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. (AMD A6-5200)
Cinebench R20 is a benchmark tool that measures a CPU’s single-core performance by rendering a 3D scene.
6.Geekbench 5 result (single)
Unknown. Help us by suggesting a value. (AMD A6-5200)
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-5200)
Unknown. Help us by suggesting a value. (Intel Core i5-4200U)
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-5200)
Unknown. Help us by suggesting a value. (Intel Core i5-4200U)
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
Unknown. Help us by suggesting a value. (AMD A6-5200)
Unknown. Help us by suggesting a value. (Intel Core i5-4200U)
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-5200
✔Intel Core i5-4200U
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-5200
✔Intel Core i5-4200U
AES is used to speed up encryption and decryption.
3.Has AVX
✔AMD A6-5200
✔Intel Core i5-4200U
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-5200
✔Intel Core i5-4200U
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-5200)
Unknown. Help us by suggesting a value. (Intel Core i5-4200U)
NEON provides acceleration for media processing, such as listening to MP3s.
7.Has MMX
✔AMD A6-5200
✔Intel Core i5-4200U
MMX is used to speed up tasks such as adjusting the contrast of an image or adjusting volume.
8.Has TrustZone
✖AMD A6-5200
✖Intel Core i5-4200U
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-5200)
Unknown. Help us by suggesting a value. (Intel Core i5-4200U)
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-10210U: What is the difference?
35points
AMD A6-9225
53points
Intel Core i5-10210U
Comparison winner
vs
64 facts in comparison
AMD A6-9225
Intel Core i5-10210U
Why is AMD A6-9225 better than Intel Core i5-10210U?
- 0.25MB/core more L2 cache per core?
0.5MB/corevs0.25MB/core - Has FMA4?
Why is Intel Core i5-10210U better than AMD A6-9225?
- 23.08% faster CPU speed?
4 x 1.6GHzvs2 x 2.6GHz - 533MHz higher ram speed?
2666MHzvs2133MHz - 6 more CPU threads?
8vs2 - 10°C higher maximum operating temperature?
100°Cvs90°C - 14nm smaller semiconductor size?
14nmvs28nm - 4.
84x higher PassMark result?
6464vs1336 - 1.1GHz higher turbo clock speed?
4.2GHzvs3.1GHz - 96KB bigger L1 cache?
256KBvs160KB
Which are the most popular comparisons?
AMD A6-9225
vs
Intel Core i3-8130U
Intel Core i5-10210U
vs
AMD Ryzen 7 3700U
AMD A6-9225
vs
Intel Core i5-8265U
Intel Core i5-10210U
vs
AMD Ryzen 5 3500U
AMD A6-9225
vs
Intel Core i3-7020U
Intel Core i5-10210U
vs
Intel Core i3-1115G4
AMD A6-9225
vs
Intel Celeron N4020
Intel Core i5-10210U
vs
AMD Ryzen 5 5500U
AMD A6-9225
vs
AMD Ryzen 3 3200U
Intel Core i5-10210U
vs
Intel Core i7-8550U
AMD A6-9225
vs
Intel Core i3-1115G4
Intel Core i5-10210U
vs
Intel Core i5-1135G7
AMD A6-9225
vs
AMD Ryzen 5 2500U
Intel Core i5-10210U
vs
AMD Ryzen 5 3450U
AMD A6-9225
vs
Intel Core i5-6200U
Intel Core i5-10210U
vs
Intel Core i3-10110U
AMD A6-9225
vs
Intel Core i5-8250U
Intel Core i5-10210U
vs
Intel Core i7-6500U
Intel Core i5-10210U
vs
AMD Ryzen 3 5300U
Price comparison
User reviews
Overall Rating
AMD A6-9225
2 User reviews
AMD A6-9225
8.
0/10
2 User reviews
Intel Core i5-10210U
3 User reviews
Intel Core i5-10210U
7.0/10
3 User reviews
Features
Value for money
8.5/10
2 votes
6.7/10
3 votes
Gaming
6.5/10
2 votes
5.7/10
3 votes
Performance
8.0/10
2 votes
6.3/10
3 votes
Reliability
8.0/10
2 votes
8.0/10
3 votes
Energy efficiency
8.0/10
1 votes
8.0/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
4.2GHz
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-10210U
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
2666MHz
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)
41.66GB/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-10210U
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-10210U)
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-10210U)
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
Cinebench R20 is a benchmark tool that measures a CPU’s multi-core performance by rendering a 3D scene.
5.Cinebench R20 (single) result
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)
790.56seconds
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)
2274.84seconds
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-10210U
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-10210U
AES is used to speed up encryption and decryption.
3.Has AVX
✔AMD A6-9225
✔Intel Core i5-10210U
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-10210U
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-10210U)
NEON provides acceleration for media processing, such as listening to MP3s.
7.Has MMX
✔AMD A6-9225
✔Intel Core i5-10210U
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-10210U
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-10210U)
The CPU can decode more instructions per clock (IPC), meaning that the CPU performs better
Price comparison
Cancel
Which are the best CPUs?
Intel Core i5-8250U vs AMD A6-9220 vs Intel Core i3-8130U
log 12. 12:30:14
#0 checking url part for id 9206 +0s … 0s
#1 checking url part for id 9326 +0s … 0s
#2 checking url part for id 9518 +0s … 0s
#3 not redirecting to Ajax server +0s … 0s
#4 did not recreate cache, as it is less than 5 days old! Created at Sat, 10 Sep 2022 13:14:02 +0200 +0s … 0s
#5 linkCache_getLink no uid found +0.009s … 0.009s
#6 linkCache_getLink no uid found +0.006s … 0.015s
#7 linkCache_getLink no uid found +0.
007s … 0.022s
#8 linkCache_getLink using $NBC_LINKCACHE +0s … 0.022s
#9 linkCache_getLink using $NBC_LINKCACHE +0s … 0.022s
#10 linkCache_getLink using $NBC_LINKCACHE +0s … 0.022s
#11 linkCache_getLink using $NBC_LINKCACHE +0s … 0.022s
#12 linkCache_getLink using $NBC_LINKCACHE +0s … 0.022s
#13 composed specs +0s … 0.022s
#14 did output specs +0s … 0.022s
#15 linkCache_getLink using $NBC_LINKCACHE +0.005s … 0.027s
#16 getting avg benchmarks for device 9206 +0.001s … 0.028s
#17 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.031s
#18 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.032s
#19 got single benchmarks 9206 +0.229s … 0.262s
#20 getting avg benchmarks for device 9326 +0.001s … 0.262s
#21 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.263s
#22 got single benchmarks 9326 +0.
009s … 0.272s
#23 getting avg benchmarks for device 9518 +0s … 0.273s
#24 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.273s
#25 got single benchmarks 9518 +0.023s … 0.296s
#26 got avg benchmarks for devices +0s … 0.296s
#27 linkCache_getLink no uid found +0s … 0.297s
#28 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.298s
#29 linkCache_getLink no uid found +0s … 0.298s
#30 linkCache_getLink no uid found +0.001s … 0.299s
#31 linkCache_getLink no uid found +0s … 0.299s
#32 linkCache_getLink using $NBC_LINKCACHE +0s … 0.299s
#33 linkCache_getLink no uid found +0.002s … 0.301s
#34 linkCache_getLink using $NBC_LINKCACHE +0s … 0.301s
#35 linkCache_getLink no uid found +0s … 0.301s
#36 linkCache_getLink using $NBC_LINKCACHE +0s … 0.301s
#37 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.301s
#38 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.302s
#39 linkCache_getLink no uid found +0.001s … 0.302s
#40 linkCache_getLink no uid found +0s … 0.303s
#41 linkCache_getLink no uid found +0s … 0.303s
#42 linkCache_getLink no uid found +0.001s … 0.304s
#43 linkCache_getLink no uid found +0s … 0.304s
#44 linkCache_getLink no uid found +0.001s … 0.305s
#45 linkCache_getLink no uid found +0s … 0.305s
#46 linkCache_getLink no uid found +0s … 0.306s
#47 linkCache_getLink no uid found +0s … 0.306s
#48 linkCache_getLink no uid found +0s … 0.306s
#49 linkCache_getLink using $NBC_LINKCACHE +0s … 0.306s
#50 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.307s
#51 linkCache_getLink using $NBC_LINKCACHE +0s … 0.307s
#52 linkCache_getLink no uid found +0.001s .
.. 0.307s
#53 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.308s
#54 linkCache_getLink no uid found +0s … 0.309s
#55 linkCache_getLink no uid found +0.001s … 0.309s
#56 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.31s
#57 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.31s
#58 linkCache_getLink using $NBC_LINKCACHE +0.438s … 0.748s
#59 linkCache_getLink using $NBC_LINKCACHE +0.017s … 0.765s
#60 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#61 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#62 linkCache_getLink no uid found +0s … 0.765s
#63 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#64 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#65 linkCache_getLink no uid found +0s … 0.765s
#66 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#67 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.765s
#68 linkCache_getLink no uid found +0s … 0.765s
#69 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#70 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#71 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#72 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#73 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#74 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#75 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#76 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#77 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#78 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#79 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#80 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#81 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#82 linkCache_getLink no uid found +0s .
.. 0.765s
#83 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#84 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#85 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#86 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#87 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#88 linkCache_getLink no uid found +0s … 0.765s
#89 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#90 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#91 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#92 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#93 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#94 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#95 linkCache_getLink no uid found +0s … 0.765s
#96 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#97 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.765s
#98 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#99 linkCache_getLink no uid found +0s … 0.765s
#100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#105 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#107 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#110 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.
765s
#112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#113 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#116 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#123 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#124 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#125 linkCache_getLink no uid found +0s … 0.765s
#126 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.765s
#127 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#128 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#130 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#133 linkCache_getLink no uid found +0s … 0.765s
#134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#137 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#138 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#139 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#140 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.765s
#141 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#143 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#144 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#147 linkCache_getLink no uid found +0s … 0.765s
#148 linkCache_getLink no uid found +0s … 0.765s
#149 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#150 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#151 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#153 linkCache_getLink using $NBC_LINKCACHE +0s … 0.765s
#154 linkCache_getLink no uid found +0s … 0.765s
#155 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.765s
#156 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.766s
#157 linkCache_getLink using $NBC_LINKCACHE +0s … 0.766s
#158 linkCache_getLink using $NBC_LINKCACHE +0s … 0.766s
#159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.766s
#160 linkCache_getLink using $NBC_LINKCACHE +0s … 0.766s
#161 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.767s
#162 linkCache_getLink no uid found +0s … 0.767s
#163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#164 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#165 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#166 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#167 linkCache_getLink no uid found +0s … 0.767s
#168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#169 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.767s
#170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#171 linkCache_getLink no uid found +0s … 0.767s
#172 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#174 linkCache_getLink no uid found +0s … 0.767s
#175 linkCache_getLink no uid found +0s … 0.767s
#176 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#179 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#180 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#181 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#182 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#183 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#184 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.767s
#185 linkCache_getLink no uid found +0s … 0.767s
#186 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#187 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#188 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#189 linkCache_getLink no uid found +0s … 0.767s
#190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#191 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#192 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#193 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#194 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#195 linkCache_getLink using $NBC_LINKCACHE +0s … 0.767s
#196 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.769s
#197 linkCache_getLink using $NBC_LINKCACHE +0s … 0.769s
#198 linkCache_getLink using $NBC_LINKCACHE +0.001s ..
. 0.77s
#199 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#200 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#201 linkCache_getLink no uid found +0s … 0.77s
#202 linkCache_getLink no uid found +0s … 0.77s
#203 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#205 linkCache_getLink no uid found +0s … 0.77s
#206 linkCache_getLink no uid found +0s … 0.77s
#207 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#208 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#209 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#210 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#211 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#212 linkCache_getLink no uid found +0s … 0.77s
#213 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.77s
#214 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#215 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#217 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#218 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#219 linkCache_getLink no uid found +0s … 0.77s
#220 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#221 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#222 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#223 linkCache_getLink no uid found +0s … 0.77s
#224 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#225 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#226 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#227 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#228 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.77s
#229 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#230 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#231 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#232 linkCache_getLink using $NBC_LINKCACHE +0s … 0.77s
#233 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.771s
#234 linkCache_getLink using $NBC_LINKCACHE +0s … 0.771s
#235 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.772s
#236 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#237 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#238 linkCache_getLink no uid found +0s … 0.772s
#239 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#240 linkCache_getLink no uid found +0s … 0.772s
#241 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#242 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#243 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.772s
#244 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#245 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#246 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#247 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#248 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#249 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#250 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#251 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#252 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#253 linkCache_getLink no uid found +0s … 0.772s
#254 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#255 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#256 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#257 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.772s
#258 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#259 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#260 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#261 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#262 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#263 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#264 linkCache_getLink no uid found +0s … 0.772s
#265 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#266 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#267 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#268 linkCache_getLink no uid found +0s … 0.772s
#269 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#270 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#271 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#272 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.772s
#273 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#274 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#275 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#276 linkCache_getLink using $NBC_LINKCACHE +0s … 0.772s
#277 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.773s
#278 linkCache_getLink using $NBC_LINKCACHE +0s … 0.773s
#279 linkCache_getLink using $NBC_LINKCACHE +0s … 0.773s
#280 linkCache_getLink no uid found +0.001s … 0.774s
#281 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#282 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#283 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#284 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#285 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#286 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.774s
#287 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#288 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#289 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#290 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#291 linkCache_getLink no uid found +0s … 0.774s
#292 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#293 linkCache_getLink no uid found +0s … 0.774s
#294 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#295 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#296 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#297 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#298 linkCache_getLink no uid found +0s … 0.774s
#299 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#300 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#301 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.774s
#302 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#303 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#304 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#305 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#306 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#307 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#308 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#309 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#310 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#311 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#312 linkCache_getLink no uid found +0s … 0.774s
#313 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#314 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#315 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.774s
#316 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#317 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#318 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#319 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#320 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#321 linkCache_getLink using $NBC_LINKCACHE +0s … 0.774s
#322 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.775s
#323 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#324 linkCache_getLink using $NBC_LINKCACHE +0s … 0.775s
#325 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.776s
#326 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#327 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#328 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#329 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.776s
#330 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#331 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#332 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#333 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#334 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#335 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#336 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#337 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#338 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.777s
#339 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#340 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#341 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#342 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#343 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.777s
#344 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#345 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#346 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#347 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#348 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#349 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#350 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#351 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.778s
#352 linkCache_getLink using $NBC_LINKCACHE +0s … 0.778s
#353 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#354 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#355 linkCache_getLink no uid found +0s … 0.779s
#356 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#357 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.779s
#358 linkCache_getLink no uid found +0s … 0.779s
#359 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#360 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#361 linkCache_getLink no uid found +0s … 0.779s
#362 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#363 linkCache_getLink no uid found +0s … 0.779s
#364 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.779s
#365 linkCache_getLink using $NBC_LINKCACHE +0s … 0.78s
#366 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.781s
#367 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#368 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#369 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#370 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#371 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#372 linkCache_getLink no uid found +0s .
.. 0.781s
#373 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#374 linkCache_getLink no uid found +0s … 0.781s
#375 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#376 linkCache_getLink no uid found +0s … 0.781s
#377 linkCache_getLink no uid found +0s … 0.781s
#378 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#379 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.781s
#380 linkCache_getLink using $NBC_LINKCACHE +0s … 0.782s
#381 linkCache_getLink no uid found +0.001s … 0.783s
#382 linkCache_getLink no uid found +0s … 0.783s
#383 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.785s
#384 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#385 linkCache_getLink no uid found +0.001s … 0.786s
#386 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#387 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.786s
#388 linkCache_getLink no uid found +0s … 0.786s
#389 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#390 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#391 linkCache_getLink no uid found +0.002s … 0.787s
#392 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s
#393 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s
#394 linkCache_getLink no uid found +0s … 0.787s
#395 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s
#396 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s
#397 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.789s
#398 linkCache_getLink using $NBC_LINKCACHE +0s … 0.789s
#399 linkCache_getLink no uid found +0s … 0.789s
#400 linkCache_getLink no uid found +0s … 0.789s
#401 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.79s
#402 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.79s
#403 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.791s
#404 linkCache_getLink no uid found +0s … 0.791s
#405 linkCache_getLink using $NBC_LINKCACHE +0s … 0.791s
#406 linkCache_getLink no uid found +0s … 0.791s
#407 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.792s
#408 linkCache_getLink using $NBC_LINKCACHE +0s … 0.792s
#409 linkCache_getLink no uid found +0.001s … 0.793s
#410 linkCache_getLink using $NBC_LINKCACHE +0s … 0.793s
#411 linkCache_getLink using $NBC_LINKCACHE +0s … 0.793s
#412 linkCache_getLink no uid found +0s … 0.793s
#413 linkCache_getLink using $NBC_LINKCACHE +0s … 0.793s
#414 linkCache_getLink using $NBC_LINKCACHE +0s … 0.793s
#415 linkCache_getLink using $NBC_LINKCACHE +0s … 0.793s
#416 linkCache_getLink using $NBC_LINKCACHE +0s … 0.793s
#417 linkCache_getLink no uid found +0.
059s … 0.852s
#418 linkCache_getLink no uid found +0s … 0.852s
#419 linkCache_getLink using $NBC_LINKCACHE +0s … 0.852s
#420 linkCache_getLink no uid found +0s … 0.852s
#421 linkCache_getLink using $NBC_LINKCACHE +0s … 0.852s
#422 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.852s
#423 linkCache_getLink using $NBC_LINKCACHE +0s … 0.852s
#424 linkCache_getLink no uid found +0.001s … 0.854s
#425 linkCache_getLink no uid found +0s … 0.854s
#426 linkCache_getLink no uid found +0s … 0.854s
#427 linkCache_getLink using $NBC_LINKCACHE +0s … 0.854s
#428 linkCache_getLink using $NBC_LINKCACHE +0s … 0.854s
#429 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.854s
#430 linkCache_getLink using $NBC_LINKCACHE +0s … 0.855s
#431 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.856s
#432 linkCache_getLink no uid found +0s .
.. 0.856s
#433 linkCache_getLink no uid found +0s … 0.856s
#434 linkCache_getLink no uid found +0s … 0.856s
#435 linkCache_getLink using $NBC_LINKCACHE +0s … 0.856s
#436 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.856s
#437 linkCache_getLink using $NBC_LINKCACHE +0s … 0.857s
#438 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.858s
#439 linkCache_getLink using $NBC_LINKCACHE +0s … 0.858s
#440 linkCache_getLink using $NBC_LINKCACHE +0s … 0.858s
#441 linkCache_getLink no uid found +0s … 0.858s
#442 linkCache_getLink using $NBC_LINKCACHE +0s … 0.858s
#443 linkCache_getLink using $NBC_LINKCACHE +0s … 0.858s
#444 linkCache_getLink no uid found +0s … 0.858s
#445 linkCache_getLink using $NBC_LINKCACHE +0s … 0.858s
#446 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.86s
#447 linkCache_getLink no uid found +0s .
.. 0.86s
#448 linkCache_getLink no uid found +0s … 0.86s
#449 linkCache_getLink using $NBC_LINKCACHE +0s … 0.86s
#450 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.862s
#451 linkCache_getLink using $NBC_LINKCACHE +0s … 0.862s
#452 linkCache_getLink using $NBC_LINKCACHE +0s … 0.862s
#453 linkCache_getLink no uid found +0s … 0.862s
#454 linkCache_getLink using $NBC_LINKCACHE +0s … 0.862s
#455 linkCache_getLink using $NBC_LINKCACHE +0s … 0.862s
#456 linkCache_getLink using $NBC_LINKCACHE +0s … 0.862s
#457 linkCache_getLink using $NBC_LINKCACHE +0s … 0.862s
#458 linkCache_getLink using $NBC_LINKCACHE +0s … 0.862s
#459 linkCache_getLink using $NBC_LINKCACHE +0s … 0.862s
#460 linkCache_getLink using $NBC_LINKCACHE +0s … 0.862s
#461 linkCache_getLink using $NBC_LINKCACHE +0s … 0.862s
#462 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.862s
#463 linkCache_getLink using $NBC_LINKCACHE +0s … 0.862s
#464 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.863s
#465 linkCache_getLink using $NBC_LINKCACHE +0s … 0.863s
#466 linkCache_getLink no uid found +0.001s … 0.864s
#467 linkCache_getLink using $NBC_LINKCACHE +0s … 0.864s
#468 linkCache_getLink using $NBC_LINKCACHE +0s … 0.864s
#469 linkCache_getLink using $NBC_LINKCACHE +0s … 0.864s
#470 linkCache_getLink using $NBC_LINKCACHE +0s … 0.864s
#471 linkCache_getLink using $NBC_LINKCACHE +0s … 0.864s
#472 linkCache_getLink using $NBC_LINKCACHE +0s … 0.864s
#473 linkCache_getLink using $NBC_LINKCACHE +0s … 0.864s
#474 linkCache_getLink no uid found +0s … 0.864s
#475 linkCache_getLink no uid found +0s … 0.864s
#476 linkCache_getLink no uid found +0s … 0.864s
#477 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.865s
#478 linkCache_getLink using $NBC_LINKCACHE +0s … 0.866s
#479 linkCache_getLink no uid found +0.001s … 0.867s
#480 linkCache_getLink using $NBC_LINKCACHE +0s … 0.867s
#481 linkCache_getLink using $NBC_LINKCACHE +0s … 0.867s
#482 linkCache_getLink no uid found +0s … 0.867s
#483 linkCache_getLink using $NBC_LINKCACHE +0s … 0.867s
#484 linkCache_getLink using $NBC_LINKCACHE +0s … 0.867s
#485 linkCache_getLink using $NBC_LINKCACHE +0s … 0.867s
#486 linkCache_getLink using $NBC_LINKCACHE +0s … 0.867s
#487 linkCache_getLink using $NBC_LINKCACHE +0s … 0.867s
#488 linkCache_getLink no uid found +0s … 0.867s
#489 linkCache_getLink no uid found +0s … 0.867s
#490 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.867s
#491 linkCache_getLink using $NBC_LINKCACHE +0s … 0.868s
#492 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.869s
#493 linkCache_getLink using $NBC_LINKCACHE +0s … 0.869s
#494 linkCache_getLink no uid found +0s … 0.869s
#495 linkCache_getLink no uid found +0s … 0.869s
#496 linkCache_getLink using $NBC_LINKCACHE +0s … 0.869s
#497 linkCache_getLink using $NBC_LINKCACHE +0s … 0.869s
#498 linkCache_getLink using $NBC_LINKCACHE +0s … 0.869s
#499 linkCache_getLink using $NBC_LINKCACHE +0s … 0.869s
#500 linkCache_getLink no uid found +0s … 0.869s
#501 linkCache_getLink using $NBC_LINKCACHE +0s … 0.869s
#502 linkCache_getLink no uid found +0s … 0.869s
#503 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.87s
#504 linkCache_getLink using $NBC_LINKCACHE +0s … 0.87s
#505 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.871s
#506 linkCache_getLink using $NBC_LINKCACHE +0s … 0.871s
#507 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.871s
#508 linkCache_getLink using $NBC_LINKCACHE +0s … 0.871s
#509 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.872s
#510 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.873s
#511 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#512 linkCache_getLink no uid found +0s … 0.873s
#513 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#514 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#515 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#516 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#517 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#518 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#519 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#520 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#521 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.873s
#522 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#523 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#524 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#525 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#526 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#527 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#528 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#529 linkCache_getLink no uid found +0s … 0.873s
#530 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#531 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#532 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#533 linkCache_getLink no uid found +0s … 0.873s
#534 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#535 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#536 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.873s
#537 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#538 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#539 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#540 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#541 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#542 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#543 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#544 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#545 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#546 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#547 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#548 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#549 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#550 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.873s
#551 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#552 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#553 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#554 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#555 linkCache_getLink no uid found +0s … 0.873s
#556 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#557 linkCache_getLink no uid found +0s … 0.873s
#558 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#559 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#560 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#561 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#562 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#563 linkCache_getLink no uid found +0s … 0.873s
#564 linkCache_getLink no uid found +0s … 0.873s
#565 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.873s
#566 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#567 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#568 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#569 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#570 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#571 linkCache_getLink no uid found +0s … 0.873s
#572 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#573 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#574 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#575 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#576 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#577 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#578 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#579 linkCache_getLink no uid found +0s … 0.873s
#580 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.873s
#581 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#582 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#583 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#584 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#585 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#586 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#587 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#588 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#589 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#590 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#591 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#592 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#593 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#594 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.873s
#595 linkCache_getLink no uid found +0s … 0.873s
#596 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#597 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#598 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#599 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#600 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#601 linkCache_getLink using $NBC_LINKCACHE +0s … 0.873s
#602 linkCache_getLink using $NBC_LINKCACHE +0s … 0.874s
#603 linkCache_getLink no uid found +0s … 0.874s
#604 linkCache_getLink using $NBC_LINKCACHE +0s … 0.874s
#605 linkCache_getLink using $NBC_LINKCACHE +0s … 0.874s
#606 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.874s
#607 linkCache_getLink using $NBC_LINKCACHE +0s … 0.874s
#608 linkCache_getLink using $NBC_LINKCACHE +0s … 0.
875s
#609 linkCache_getLink using $NBC_LINKCACHE +0s … 0.875s
#610 linkCache_getLink using $NBC_LINKCACHE +0s … 0.875s
#611 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.876s
#612 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#613 linkCache_getLink no uid found +0s … 0.876s
#614 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#615 linkCache_getLink no uid found +0s … 0.876s
#616 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#617 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#618 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#619 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#620 linkCache_getLink no uid found +0s … 0.876s
#621 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#622 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#623 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.876s
#624 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#625 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#626 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#627 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#628 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#629 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#630 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#631 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#632 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#633 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#634 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#635 linkCache_getLink no uid found +0s … 0.876s
#636 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#637 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.876s
#638 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#639 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#640 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#641 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#642 linkCache_getLink no uid found +0s … 0.876s
#643 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.877s
#644 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.878s
#645 linkCache_getLink no uid found +0s … 0.878s
#646 linkCache_getLink no uid found +0s … 0.878s
#647 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#648 linkCache_getLink no uid found +0s … 0.878s
#649 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#650 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#651 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#652 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.878s
#653 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#654 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#655 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#656 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#657 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#658 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#659 linkCache_getLink no uid found +0s … 0.878s
#660 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#661 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#662 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#663 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#664 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#665 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#666 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.878s
#667 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#668 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#669 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#670 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#671 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#672 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#673 linkCache_getLink no uid found +0s … 0.878s
#674 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.878s
#675 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.88s
#676 linkCache_getLink no uid found +0s … 0.88s
#677 linkCache_getLink no uid found +0s … 0.88s
#678 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#679 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#680 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#681 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.88s
#682 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#683 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#684 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#685 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#686 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#687 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#688 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#689 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#690 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#691 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#692 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#693 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#694 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#695 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#696 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.88s
#697 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#698 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#699 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#700 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#701 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#702 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#703 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#704 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#705 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#706 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#707 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#708 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#709 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#710 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#711 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.88s
#712 linkCache_getLink no uid found +0s … 0.88s
#713 linkCache_getLink no uid found +0s … 0.88s
#714 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#715 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#716 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#717 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#718 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#719 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.881s
#720 linkCache_getLink using $NBC_LINKCACHE +0s … 0.881s
#721 linkCache_getLink using $NBC_LINKCACHE +0s … 0.881s
#722 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.882s
#723 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#724 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#725 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#726 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.882s
#727 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#728 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#729 linkCache_getLink no uid found +0s … 0.882s
#730 linkCache_getLink no uid found +0s … 0.882s
#731 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#732 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#733 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#734 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#735 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#736 linkCache_getLink no uid found +0s … 0.882s
#737 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#738 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#739 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#740 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#741 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.882s
#742 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#743 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#744 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#745 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#746 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#747 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#748 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#749 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#750 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#751 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#752 linkCache_getLink no uid found +0s … 0.882s
#753 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#754 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#755 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.882s
#756 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#757 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#758 linkCache_getLink no uid found +0s … 0.882s
#759 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#760 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#761 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#762 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#763 linkCache_getLink no uid found +0s … 0.882s
#764 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#765 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#766 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#767 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#768 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#769 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#770 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.882s
#771 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#772 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#773 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#774 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#775 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#776 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#777 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#778 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#779 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#780 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#781 linkCache_getLink no uid found +0s … 0.883s
#782 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#783 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#784 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.883s
#785 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#786 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#787 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#788 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#789 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#790 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#791 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#792 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#793 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#794 linkCache_getLink no uid found +0s … 0.883s
#795 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#796 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#797 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#798 linkCache_getLink using $NBC_LINKCACHE +0s …
0.883s
#799 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#800 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#801 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#802 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#803 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#804 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#805 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#806 linkCache_getLink using $NBC_LINKCACHE +0s … 0.883s
#807 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.883s
#808 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#809 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#810 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#811 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.885s
#812 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.885s
#813 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#814 linkCache_getLink no uid found +0s … 0.885s
#815 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#816 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#817 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#818 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#819 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#820 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#821 linkCache_getLink no uid found +0s … 0.885s
#822 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#823 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#824 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#825 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#826 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#827 linkCache_getLink no uid found +0s .
.. 0.885s
#828 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#829 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#830 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#831 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#832 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#833 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#834 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#835 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#836 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#837 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#838 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#839 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#840 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#841 linkCache_getLink no uid found +0s ..
. 0.885s
#842 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#843 linkCache_getLink no uid found +0s … 0.885s
#844 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#845 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#846 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#847 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#848 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#849 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#850 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#851 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#852 linkCache_getLink no uid found +0s … 0.885s
#853 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#854 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#855 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#856 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.885s
#857 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#858 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#859 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#860 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#861 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#862 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#863 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#864 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#865 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#866 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#867 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#868 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#869 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#870 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.885s
#871 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#872 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#873 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#874 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#875 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#876 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#877 linkCache_getLink no uid found +0s … 0.885s
#878 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#879 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#880 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#881 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#882 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#883 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#884 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.886s
#885 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#886 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#887 linkCache_getLink no uid found +0s … 0.886s
#888 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#889 linkCache_getLink no uid found +0s … 0.886s
#890 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#891 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#892 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#893 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#894 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.886s
#895 linkCache_getLink using $NBC_LINKCACHE +0s … 0.887s
#896 linkCache_getLink using $NBC_LINKCACHE +0s … 0.887s
#897 linkCache_getLink no uid found +0.001s … 0.888s
#898 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#899 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.888s
#900 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#901 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#902 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#903 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#904 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#905 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#906 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#907 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#908 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#909 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#910 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#911 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#912 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#913 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.888s
#914 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#915 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#916 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#917 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#918 linkCache_getLink no uid found +0s … 0.888s
#919 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#920 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#921 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#922 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#923 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#924 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.891s
#925 linkCache_getLink no uid found +0s … 0.891s
#926 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#927 linkCache_getLink no uid found +0s … 0.891s
#928 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.891s
#929 linkCache_getLink no uid found +0.002s … 0.892s
#930 linkCache_getLink using $NBC_LINKCACHE +0s … 0.892s
#931 linkCache_getLink using $NBC_LINKCACHE +0s … 0.892s
#932 linkCache_getLink using $NBC_LINKCACHE +0s … 0.892s
#933 linkCache_getLink no uid found +0s … 0.892s
#934 linkCache_getLink no uid found +0.001s … 0.894s
#935 linkCache_getLink using $NBC_LINKCACHE +0s … 0.894s
#936 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.896s
#937 linkCache_getLink no uid found +0s … 0.896s
#938 linkCache_getLink no uid found +0.002s … 0.898s
#939 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#940 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#941 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#942 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#943 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.898s
#944 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#945 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#946 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#947 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#948 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#949 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#950 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#951 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#952 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#953 linkCache_getLink no uid found +0s … 0.898s
#954 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#955 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#956 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#957 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.898s
#958 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#959 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#960 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#961 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#962 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#963 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.899s
#964 linkCache_getLink using $NBC_LINKCACHE +0s … 0.899s
#965 linkCache_getLink using $NBC_LINKCACHE +0s … 0.899s
#966 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.9s
#967 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#968 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#969 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#970 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#971 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.9s
#972 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#973 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#974 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#975 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#976 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#977 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#978 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#979 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#980 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#981 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#982 linkCache_getLink no uid found +0s … 0.9s
#983 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#984 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#985 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#986 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.9s
#987 linkCache_getLink no uid found +0s … 0.9s
#988 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#989 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#990 linkCache_getLink using $NBC_LINKCACHE +0s … 0.9s
#991 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.901s
#992 linkCache_getLink using $NBC_LINKCACHE +0s … 0.901s
#993 linkCache_getLink using $NBC_LINKCACHE +0s … 0.901s
#994 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.903s
#995 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#996 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#997 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#998 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#999 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#1000 linkCache_getLink using $NBC_LINKCACHE +0s …
0.903s
#1001 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#1002 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#1003 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#1004 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#1005 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#1006 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#1007 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#1008 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#1009 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#1010 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#1011 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#1012 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s
#1013 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.904s
#1014 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.904s
#1015 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.906s
#1016 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1017 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1018 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1019 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1020 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1021 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1022 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1023 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1024 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1025 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1026 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1027 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1028 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.906s
#1029 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1030 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1031 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1032 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1033 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#1034 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.907s
#1035 linkCache_getLink using $NBC_LINKCACHE +0s … 0.907s
#1036 linkCache_getLink using $NBC_LINKCACHE +0s … 0.907s
#1037 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.908s
#1038 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#1039 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#1040 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#1041 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#1042 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.908s
#1043 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#1044 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#1045 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#1046 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#1047 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#1048 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#1049 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#1050 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#1051 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#1052 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#1053 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#1054 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#1055 linkCache_getLink using $NBC_LINKCACHE +0s … 0.909s
#1056 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.909s
#1057 linkCache_getLink using $NBC_LINKCACHE +0s … 0.909s
#1058 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.91s
#1059 linkCache_getLink using $NBC_LINKCACHE +0s … 0.91s
#1060 linkCache_getLink using $NBC_LINKCACHE +0s … 0.91s
#1061 linkCache_getLink using $NBC_LINKCACHE +0s … 0.91s
#1062 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#1063 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#1064 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#1065 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#1066 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#1067 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#1068 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#1069 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#1070 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.911s
#1071 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#1072 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#1073 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#1074 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#1075 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#1076 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#1077 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#1078 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#1079 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.913s
#1080 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1081 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1082 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1083 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.915s
#1084 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.915s
#1085 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1086 linkCache_getLink using $NBC_LINKCACHE +0s … 0.916s
#1087 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.917s
#1088 linkCache_getLink using $NBC_LINKCACHE +0s … 0.917s
#1089 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.918s
#1090 linkCache_getLink using $NBC_LINKCACHE +0s … 0.919s
#1091 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.92s
#1092 linkCache_getLink using $NBC_LINKCACHE +0s … 0.92s
#1093 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.922s
#1094 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s
#1095 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.923s
#1096 linkCache_getLink using $NBC_LINKCACHE +0s … 0.924s
#1097 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.925s
#1098 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.925s
#1099 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1105 linkCache_getLink no uid found +0s … 0.925s
#1106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1107 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1110 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1112 linkCache_getLink no uid found +0s .
.. 0.925s
#1113 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1116 linkCache_getLink no uid found +0s … 0.925s
#1117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1123 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1124 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1125 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1126 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.925s
#1127 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1128 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1129 linkCache_getLink no uid found +0s … 0.925s
#1130 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1133 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1137 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1138 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1139 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1140 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.925s
#1141 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1143 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1144 linkCache_getLink no uid found +0s … 0.925s
#1145 linkCache_getLink no uid found +0s … 0.925s
#1146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1147 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1148 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1149 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1150 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1151 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1153 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s
#1154 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.925s
#1155 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.926s
#1156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.926s
#1157 linkCache_getLink using $NBC_LINKCACHE +0s … 0.926s
#1158 linkCache_getLink using $NBC_LINKCACHE +0s … 0.926s
#1159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.926s
#1160 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.928s
#1161 linkCache_getLink no uid found +0s … 0.928s
#1162 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1164 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1165 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1166 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1167 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1168 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.928s
#1169 linkCache_getLink no uid found +0s … 0.928s
#1170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1171 linkCache_getLink no uid found +0s … 0.928s
#1172 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1174 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1175 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.93s
#1176 linkCache_getLink using $NBC_LINKCACHE +0s … 0.93s
#1177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.93s
#1178 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.932s
#1179 linkCache_getLink no uid found +0s … 0.932s
#1180 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1181 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1182 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.932s
#1183 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1184 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1185 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1186 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1187 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1188 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1189 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1191 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1192 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1193 linkCache_getLink no uid found +0s … 0.932s
#1194 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1195 linkCache_getLink no uid found +0s … 0.932s
#1196 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.932s
#1197 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1198 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1199 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1200 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1201 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1202 linkCache_getLink no uid found +0s … 0.932s
#1203 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1205 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1206 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1207 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1208 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1209 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1210 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.932s
#1211 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1212 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1213 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1214 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1215 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1217 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1218 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1219 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1220 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1221 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1222 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1223 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1224 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.932s
#1225 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1226 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1227 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1228 linkCache_getLink no uid found +0s … 0.932s
#1229 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1230 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1231 linkCache_getLink using $NBC_LINKCACHE +0s … 0.932s
#1232 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.934s
#1233 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1234 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1235 linkCache_getLink using $NBC_LINKCACHE +0s … 0.935s
#1236 linkCache_getLink using $NBC_LINKCACHE +0s … 0.935s
#1237 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.936s
#1238 linkCache_getLink no uid found +0s .
.. 0.936s
#1239 linkCache_getLink no uid found +0s … 0.936s
#1240 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s
#1241 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.937s
#1242 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.939s
#1243 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.941s
#1244 linkCache_getLink no uid found +0s … 0.941s
#1245 linkCache_getLink using $NBC_LINKCACHE +0s … 0.941s
#1246 linkCache_getLink using $NBC_LINKCACHE +0s … 0.941s
#1247 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.942s
#1248 linkCache_getLink no uid found +0s … 0.942s
#1249 linkCache_getLink using $NBC_LINKCACHE +0s … 0.942s
#1250 linkCache_getLink using $NBC_LINKCACHE +0s … 0.942s
#1251 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.945s
#1252 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.945s
#1253 linkCache_getLink no uid found +0s … 0.945s
#1254 linkCache_getLink using $NBC_LINKCACHE +0s … 0.945s
#1255 min, max, avg, median took s +0.001s … 0.946s
#1256 return log +0.001s … 0.946s
AMD A6-7310 vs Intel Core i5-4210U
Comparative analysis of AMD A6-7310 and Intel Core i5-4210U 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, Geekbench 4 — Single Core, Geekbench 4 — Multi-Core, CompuBench 1.5 Desktop — Face Detection (mPixels/s), 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), GFXBench 4.0 — Car Chase Offscreen (Frames), GFXBench 4.0 — Manhattan (Frames), GFXBench 4.0 — T-Rex (Frames), GFXBench 4.0 — Car Chase Offscreen (Fps), GFXBench 4.0 — Manhattan (Fps), GFXBench 4.0 — T-Rex (Fps).
AMD A6-7310
Buy on Amazon
vs
Intel Core i5-4210U
Buy on Amazon
Differences
Reasons to consider the AMD A6-7310
- CPU is newer: launch date 1 year(s) 0 month(s) later
- 2 more cores, run more applications at once: 4 vs 2
- 4x more L2 cache, more data can be stored in the L2 cache for quick access later
- Around 59% better performance in CompuBench 1.5 Desktop — Face Detection (mPixels/s): 2.556 vs 1.608
- 5.1x better performance in CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s): 21.75 vs 4.
244 - Around 20% better performance in GFXBench 4.0 — T-Rex (Frames): 4016 vs 3360
- Around 20% better performance in GFXBench 4.0 — T-Rex (Fps): 4016 vs 3360
| Launch date | 7 May 2015 vs 14 April 2014 |
| Number of cores | 4 vs 2 |
| L2 cache | 2 MB vs 512 KB |
| CompuBench 1.5 Desktop — Face Detection (mPixels/s) | 2.556 vs 1.608 |
| CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s) | 21.75 vs 4.244 |
| GFXBench 4.0 — T-Rex (Frames) | 4016 vs 3360 |
GFXBench 4. 0 — T-Rex (Fps) |
4016 vs 3360 |
Reasons to consider the Intel Core i5-4210U
- Around 13% higher clock speed: 2.70 GHz vs 2.4 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: 22 nm vs 28 nm
- Around 76% better performance in PassMark — Single thread mark: 1378 vs 785
- Around 32% better performance in PassMark — CPU mark: 2297 vs 1737
- 2.2x better performance in Geekbench 4 — Single Core: 547 vs 247
- Around 61% better performance in Geekbench 4 — Multi-Core: 1145 vs 712
- 8.3x better performance in CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s): 25.476 vs 3.068
- Around 42% better performance in CompuBench 1.5 Desktop — T-Rex (Frames/s): 0.182 vs 0.128
- Around 11% better performance in GFXBench 4.0 — Car Chase Offscreen (Frames): 742 vs 671
- 2.
3x better performance in GFXBench 4.0 — Manhattan (Frames): 1697 vs 750 - Around 11% better performance in GFXBench 4.0 — Car Chase Offscreen (Fps): 742 vs 671
- 2.3x better performance in GFXBench 4.0 — Manhattan (Fps): 1697 vs 750
| Maximum frequency | 2.70 GHz vs 2.4 GHz |
| Maximum core temperature | 100°C vs 90°C |
| Manufacturing process technology | 22 nm vs 28 nm |
| PassMark — Single thread mark | 1378 vs 785 |
| PassMark — CPU mark | 2297 vs 1737 |
| Geekbench 4 — Single Core | 547 vs 247 |
| Geekbench 4 — Multi-Core | 1145 vs 712 |
CompuBench 1. 5 Desktop — Ocean Surface Simulation (Frames/s) |
25.476 vs 3.068 |
| CompuBench 1.5 Desktop — T-Rex (Frames/s) | 0.182 vs 0.128 |
| GFXBench 4.0 — Car Chase Offscreen (Frames) | 742 vs 671 |
| GFXBench 4.0 — Manhattan (Frames) | 1697 vs 750 |
| GFXBench 4.0 — Car Chase Offscreen (Fps) | 742 vs 671 |
| GFXBench 4.0 — Manhattan (Fps) | 1697 vs 750 |
Compare benchmarks
CPU 1: AMD A6-7310
CPU 2: Intel Core i5-4210U
| PassMark — Single thread mark |
|
|
|||
| PassMark — CPU mark |
|
|
|||
| Geekbench 4 — Single Core |
|
|
|||
| Geekbench 4 — Multi-Core |
|
|
|||
CompuBench 1. 5 Desktop — Face Detection (mPixels/s) |
|
|
|||
| CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s) |
|
|
|||
| CompuBench 1.5 Desktop — T-Rex (Frames/s) |
|
|
|||
CompuBench 1. 5 Desktop — Bitcoin Mining (mHash/s) |
|
|
|||
| GFXBench 4.0 — Car Chase Offscreen (Frames) |
|
|
|||
| GFXBench 4.0 — Manhattan (Frames) |
|
|
|||
GFXBench 4. 0 — T-Rex (Frames) |
|
|
|||
| GFXBench 4.0 — Car Chase Offscreen (Fps) |
|
|
|||
| GFXBench 4.0 — Manhattan (Fps) |
|
|
|||
GFXBench 4. 0 — T-Rex (Fps) |
|
|
| Name | AMD A6-7310 | Intel Core i5-4210U |
|---|---|---|
| PassMark — Single thread mark | 785 | 1378 |
| PassMark — CPU mark | 1737 | 2297 |
| Geekbench 4 — Single Core | 247 | 547 |
| Geekbench 4 — Multi-Core | 712 | 1145 |
CompuBench 1. 5 Desktop — Face Detection (mPixels/s) |
2.556 | 1.608 |
| CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s) | 3.068 | 25.476 |
| CompuBench 1.5 Desktop — T-Rex (Frames/s) | 0.128 | 0.182 |
| CompuBench 1.5 Desktop — Video Composition (Frames/s) | 7.012 | |
| CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s) | 21.75 | 4.244 |
| GFXBench 4.0 — Car Chase Offscreen (Frames) | 671 | 742 |
GFXBench 4. 0 — Manhattan (Frames) |
750 | 1697 |
| GFXBench 4.0 — T-Rex (Frames) | 4016 | 3360 |
| GFXBench 4.0 — Car Chase Offscreen (Fps) | 671 | 742 |
| GFXBench 4.0 — Manhattan (Fps) | 750 | 1697 |
| GFXBench 4.0 — T-Rex (Fps) | 4016 | 3360 |
Compare specifications (specs)
| AMD A6-7310 | Intel Core i5-4210U | |
|---|---|---|
| Architecture codename | Carrizo-L | Haswell |
| Family | AMD A-Series Processors | |
| Launch date | 7 May 2015 | 14 April 2014 |
| OPN Tray | AM7310JBY44JB | |
| Place in performance rating | 1850 | 1632 |
| Series | AMD A6-Series APU for Laptops | 4th Generation Intel® Core™ i5 Processors |
| Vertical segment | Laptop | Mobile |
| Launch price (MSRP) | $281 | |
| Processor Number | i5-4210U | |
| Status | Launched | |
| 64 bit support | ||
| Base frequency | 2 GHz | 1. 70 GHz |
| L2 cache | 2 MB | 512 KB |
| Manufacturing process technology | 28 nm | 22 nm |
| Maximum core temperature | 90°C | 100°C |
| Maximum frequency | 2.4 GHz | 2.70 GHz |
| Number of cores | 4 | 2 |
| Number of threads | 4 | 4 |
| Transistor count | 930 Million | 1400 million |
| Unlocked | ||
| Bus Speed | 5 GT/s DMI2 | |
| Die size | 118 mm | |
| L1 cache | 128 KB | |
| L3 cache | 3 MB | |
| Max memory channels | 1 | 2 |
| Supported memory frequency | 1866 MHz | |
| Supported memory types | DDR3L | DDR3L 1333/1600, LPDDR3 1333/1600 |
| Maximum memory bandwidth | 25. 6 GB/s |
|
| Maximum memory size | 16 GB | |
| Enduro | ||
| Graphics max frequency | 800 MHz | 1 GHz |
| Processor graphics | AMD Radeon R4 Graphics | Intel® HD Graphics 4400 |
| Switchable graphics | ||
| Unified Video Decoder (UVD) | ||
| Video Codec Engine (VCE) | ||
| Device ID | 0xA16 | |
| Graphics base frequency | 200 MHz | |
| Graphics max dynamic frequency | 1. 00 GHz |
|
| Intel® Clear Video HD technology | ||
| Intel® Flexible Display Interface (Intel® FDI) | ||
| Intel® InTru™ 3D technology | ||
| Intel® Quick Sync Video | ||
| Max video memory | 2 GB | |
| DisplayPort | ||
| HDMI | ||
| eDP | ||
| Number of displays supported | 3 | |
| Wireless Display (WiDi) support | ||
| DirectX | 12 | 11. 2/12 |
| Vulkan | ||
| OpenGL | 4.3 | |
| Sockets supported | FP4, FT3b | FCBGA1168 |
| Thermal Design Power (TDP) | 15 Watt | 15 Watt |
| Low Halogen Options Available | ||
| Max number of CPUs in a configuration | 1 | |
| Package Size | 40mm x 24mm x 1. 5mm |
|
| PCI Express revision | 2.0 | 2.0 |
| Integrated IDE | ||
| Integrated LAN | ||
| Max number of PCIe lanes | 12 | |
| Max number of SATA 6 Gb/s Ports | 4 | |
| Number of USB ports | 4 | |
| PCI support | ||
| PCIe configurations | 4×1, 2×4 | |
| Total number of SATA ports | 4 | |
| UART | ||
| USB revision | 3. 0 |
|
| AMD App Acceleration | ||
| AMD Elite Experiences | ||
| AMD HD3D technology | ||
| Enhanced Virus Protection (EVP) | ||
| Fused Multiply-Add (FMA) | ||
| Fused Multiply-Add 4 (FMA4) | ||
| Intel® Advanced Vector Extensions (AVX) | ||
| Intel® AES New Instructions | ||
| PowerGating | ||
| PowerNow | ||
| VirusProtect | ||
| Enhanced Intel SpeedStep® technology | ||
| Flexible Display interface (FDI) | ||
| General-Purpose Input/Output (GPIO) | ||
| HD Audio | ||
| Idle States | ||
| Instruction set extensions | Intel® SSE4. 1, Intel® SSE4.2, Intel® AVX2 |
|
| Intel 64 | ||
| Intel® Active Management technology (AMT) | ||
| Intel® Hyper-Threading technology | ||
| Intel® ME Firmware Version | 9.5 | |
| Intel® Rapid Storage technology (RST) | ||
| Intel® TSX-NI | ||
| Intel® Turbo Boost technology | ||
| Intel® vPro™ Platform Eligibility | ||
| Matrix Storage | ||
| Smart Connect | ||
| Thermal Monitoring | ||
| AMD Virtualization (AMD-V™) | ||
IOMMU 2. 0 |
||
| Intel® Virtualization Technology (VT-x) | ||
| Intel® Virtualization Technology for Directed I/O (VT-d) | ||
| Intel® VT-x with Extended Page Tables (EPT) | ||
| Max resolution over DisplayPort | [email protected] | |
| Max resolution over HDMI 1.4 | [email protected] | |
| Anti-Theft technology | ||
| Execute Disable Bit (EDB) | ||
| Intel® Identity Protection technology | ||
| Intel® Secure Key technology | ||
| Intel® Trusted Execution technology (TXT) |
AMD A6 vs Intel i3 (Complete Guide & Reviews In 2022)
Every gamer wants to build or buy their dream PC in which they can have endless fun with the latest games and get maximum performance.
For this purpose, manufacturers make the best gaming PCs on which gamers can utilize their time to enjoy the best of their lives. But since gaming PCs are costly, some people can’t afford them, and they look for cheap alternatives that can play games that don’t demand high requirements.
Under such conditions, you might want to look at AMD A6 and Intel i3 systems that give you a budget-friendly and stable gaming system with good performance. These computers support less graphics-oriented games, but which one is better than the other? We will discuss this in complete detail to understand which one you should choose and why.
Table of Contents
AMD A-Series Vs Intel i3 (The Basic Features And Performance)
The AMD A6 has a 3.6 GHz processor over the 3.3 GHz processor of the i3, whereas there is a great price difference between both where you will find an i3 for more than double the cost of an AMD processor. AMD is better at game performance but not at multitasking as compared to i3 as it has 2 cores in contrast to i3, which comes with 4 cores.
With the progression of time, computer processor developers redesign/refine their central processors so they can give higher performance than previously released models. Along these lines, both AMD and Intel computer chips are acceptable spending choices for anybody.
Their lone similitude is that they’re both dual cores; from that point onward, their innovations change incredibly. Beginning with the primary central processor of core i3, the 3220 is a 3.3 GHz with 3MB cache. It packs an HD 2500 GPU and takes a 55W TDP. An extraordinary component is that it’s hyperthreaded, which boosts the use of every processor unit.
In contrast, the AMD A6 clocked faster at 3.6 GHz but at the expense of a lower cache of only 0.5 MB. As an Advanced Processing Unit (APU), its focus is on a beefier GPU: it packs integrated graphics of Radeon HD 7540D, which is much better than ordinary integrated graphics. It’s capable of playing casual games. It is overclockable, but it eats more power at 65W TDP.
Now we take a look at each of them separately.
The 10th generation in Intel processors is the most powerful generation. For i3 with 10th generation, these systems come with AI and with a boost of 2.5x than ordinary i3. This means that these systems can handle better graphics and high CPU usage under any conditions without any limitations.
It is a budget-friendly processor on which players can play lots of games without any interruption and slow performance as it gives a surprisingly impressive performance and pretty shocking results. With this processor, your system is all set up to play games like DMC 4, Assasin Creed Brotherhood, Far Cry 3, Call of duty modern warfare 2, Crysis 2, and pretty much other games.
The performance you get with the Intel i3 processor with the 10th generation is pretty amazing. Overall, it will win the hearts of many gamers who can’t afford expensive PCs themselves. They can rely on i3 systems to play most of the non-graphics oriented games as well as some with basic built-in graphic cards.
Some specifications of the i3 system are:
- Dual-Core and 4 threads.
- 4 MB Intel Cache.
- Powerful and innovative 10th generation.
- 10 GHz max clock frequency.
AMD A6 is an entry-level CPU but powerful enough to support all those games that don’t require high graphics and the software that doesn’t eat much memory from the processor. These A6 7th generation processors are the latest and fastest in them all. It was launched in 2019, and it’s still a budget-friendly processor that gamers can get for themselves to enjoy some decent amount of gaming.
A6 was actually launched to beat the i3 processors, where its base speed was set to 3.5 GHz with the latest releases over time. It is a well-optimized processor that supports well for DDR4 RAM memory making it a pretty fast computer system for performance.
With this system, gamers are able to enjoy games like Far Cry 3, Tekken Tag, Sleeping Dogs, PUBG and various other games that don’t demand high graphics to run.
These systems are pretty easy to maintain and come at a very affordable price that makes them fit for use for medium-ranged gamers.
Some specifications of AMD A6 are:
- Dual-core processor with 2 threads.
- Radeon R5 integrated graphics.
- 7th generation
- 8 GHz Max speed.
Differences Between AMD A6 vs Intel i3
As we have seen the features of both of the medium spec gaming systems, now it’s time we discuss the features of the a6 processor vs i3 head to head to see which one is good over the other one.
1.
Performance.
The core i3 performs well with the games due to more cores as compared to A6. The test was taken on the games that included GTA V, Far Cry 4, and Call of Duty Black Ops 2. Both of these systems played the games in low settings, but i3 was smoother than A6. The result of performance was quite impressive for i3, so it’s a win for the i3 system.
2.
FPS.
The A6 gave around 40-50 FPS for each of these games, and the experience was good, but there was a bit of lag in the games where action screenplay was involved or too many 3D textures were involved. The games felt even smoother on the i3 system, where the average FPS for each game was around 60 FPS, and some were going above 60 as well, providing a very smooth experience. This demonstrates that i3 even outnumbered the A6 in the case of FPS for various games.
3.
Price.
For the price, both of these systems are budget-friendly for gamers. They can decide which one they should go for based on the above-mentioned demonstration of both of the systems. For i3, you have to pay a little bit on the extra, but in return, you get a good response for the performance and smoother gameplay, whereas if you choose A6, you will get a lot cheaper computer system for less price, but the performance will be compromised too.
4.
Benchmarks.
If we compare the benchmarks for the performance of each of these systems, then here is what the stats look like.
The i3 scores 15% better at 3DMark11 physics, and it was also able to perform 16% better at Geekbench. For the A6 5400K, it went well with the integrated graphics performance of about 22%, whereas i3 needs to have an external card for gaming and better performance.
Conclusion
This was a discussion on the comparison of AMD A6 vs Intel i3 computer systems. We discussed their basic differences and their best models with the comparison that which one is better over the other. Both showed good performance, and both had a big difference in price. It’s up to the users to decide which one they want from the specifications explained here.
FAQ’s
Is AMD A6 good?
AMD A6 is a good performance system that comes for low-budget buyers with limited specs that are enough to run things just as fine.
It’s an entry-level system with an integrated graphics card to support entry-level graphics-supported games. It has a low power consumption of 15w.
Which is better, AMD or i3?
Both AMD a6 processor vs intel i3 systems are entry-level for gamers, but these processors give enough performance for the user to enjoy a good time. For the most part, i3 performs better than A6, but A6 has a pretty low price as compared.
AMD a6 equivalent to intel
AMD A6-7310 is an entry-level laptop processor with Radeon R4 Graphics. It is manufactured using a 28 nm process and has 2 cores that operate at 2.0 GHz. The A6-7310 also has a 1 MB L2 cache and 4 MB of shared L3 cache. In terms of performance, the A6-7310 is equivalent to the Intel Core i3-5005U. The A6-7310 also has a thermal design power (TDP) of 15 watts.
Can AMD A6 9220 Vs Intel i3 Compare In Performance?
Both processors have their pros and cons, but which one is the best for your needs?
The AMD A6 9220 has a clock speed of 2.
5 GHz and comes with a Radeon R5 integrated graphics card. It is a budget-friendly option that is good for basic computing tasks like browsing the internet, checking email, and watching videos. The Intel i3 has a clock speed of 3.9 GHz and comes with an HD Graphics 630 integrated graphics card. It is more expensive than the AMD A6 9220, but it is better suited for more demanding tasks like gaming and video editing. So, it depends on your priorities and needs.
AMD A6-7480 vs Intel Core i5-3470 Comparison
VS
AMD A6-7480
Buy on Amazon
Intel Core i5-3470
Buy on Amazon
- Key Differences
- Performance
- Features
- General info
- Memory
- Benchmarks
AMD A6-7480
Intel Core i5-3470
| Cores | 2 | 4 |
| CPU Threads | 2 | 4 |
| Base Clock Speed | 3. 5GHz |
3.2GHz |
| Turbo Clock Speed | 3.8GHz | 3.6GHz |
| TDP (THERMAL DESIGN POINT) | 65W | 77W |
| Has integrated graphics | Yes | Yes |
| Performance per watt | Not Known | 108. 0 |
| CPU Speed & Cores | 2 x 3.5GHz | 4 x 3. 2GHz |
| Number of CPU Threads | 2 | 4 |
| L3 Cache Size | 1MB | 6MB |
| Turbo Boost Frequency | 3. 8GHz |
3.6GHz |
| Does it have an unlocked multiplier | No | No |
| L3 Core | 0. 5MB/core |
1.5MB/core |
| Uses ARM big.LITTLE tech | No | No |
| Uses ARM HMP | Yes | No |
| Clock Multiplier | 22 | 32 |
| Turbo Core Tech Version | 3 | Not Known |
| L2 Cache Size | Not Known | 1MB |
| L1 Cache Size | Not Known | 256KB |
| L2 Core | Not Known | 0. 25MB/core |
Show more specs
| Has AES Support | Yes | Yes |
| Supports CPU Throttling | Yes | Yes |
| Supported SSE Version | 4. 2 |
4.2 |
| Has AVX Support | Yes | Yes |
| Has MMX Tech Support | Yes | Yes |
| Supports ARM TrustZone Tech | Yes | No |
| Has F16C Support | Yes | Yes |
| Has FMA4 Instructions Support | Yes | No |
| Has Multithreading Tech Support | Yes | No |
| Has NX Processor Bit Support | Yes | Yes |
| Has FMA3 Instructions Support | Yes | No |
Show more specs
| RAM Memory Speed | 2133MHz | 1600MHz |
| Max Memory Channels | 2 | 2 |
| ECC (Error-Correcting Code) Memory Support | No | No |
| DDR Type Memory Version | 3 | Not Known |
| Max Memory Bandwidth | Not Known | 25. 6GB/s |
| Supported Memory Size | Not Known | 32GB |
| Bus Bandwidth | Not Known | 5GT/s |
Show more specs
| PassMark Score | 1868 | 6606 |
| PassMark Score (Single Thread) | 1604 | 1908 |
| PassMark Score (Overclocked) | Not Known | 7464 |
| CPU Performance (Per Watt) | Not Known | 108. 0 |
| Power Consumption Under High Load | Not Known | 96. 6W |
| Standard Power Consumption | Not Known | 54. 4W |
Show more specs
Similar Comparisons
AMD A6-5400K vs Intel Core i5-4670S: What is the difference?
Smartphone-graphic wire headphones
44 BALLLA
AMD A6-5400K
38 BALLLA
Intel Core i5-4670S
Winner when comparing
9000 2 4670S
Why is AMD A6-5400K better than Intel Core i5-4670S?
- 266MHz higher RAM speed?
1866MHz vs 1600MHz - GPU frequency 410MHz higher?
760MHz vs 350MHz - Has an unlocked multiplier?
- 0.25MB/core more L2 cache per core?
0.5MB/core vs 0.25MB/core - Supports 1 more displays?
4 vs 3 - Has FMA4?
Why is Intel Core i5-4670S better than AMD A6-5400K?
- 1.
72x higher CPU speed?
4 x 3.1GHz vs 2 x 3.6GHz - 2 more CPU threads?
4 vs 2 - Smaller 10nm semiconductors?
22nm vs 32nm - 1 newer PCI Express (PCIe) version?
3 vs 2 - 160KB more L1 cache?
256KB vs 96KB - 4.6GB/s more memory bandwidth?
25.6GB/s vs 21GB/s - 200million more transistors?
1400 million vs 1200 million
Which comparisons are the most popular?
AMD A6-5400K
VS
Intel Core i3-3220
Intel Core i5-4670S
VS
Intel Core i5-4670
A6-5400K 9000) VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS
Intel Core i5-4670S
vs
AMD Pro A8-8650B
AMD A6-5400K
VS
AMD A6-7480
Intel Core i5-4670S
VS
AMD A4-4300M
AMD A6-5400K
VS 9000 VS 9000 VS 9000 VS 9000 AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD -5800k
Intel Core i5-4670s
VS
Intel Core i5-10400
AMD A6-5400K
VS
Intel Core i5-25403
Intel Core I5-46703
9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 1600
AMD A6-5400K
VS
AMD A4-5300
Intel Core i5-4670s
VS
Intel Core i5-3570
AMD A6-5400K
VS
Intel Celeeron J4005
Intel Core INTEL Core INTEL Core INTEL CORE INTEL Core INTEL Core INTEL Core INTEL Core INTEL Core INTEL CORE INTEL CORE INTL Intel Core i5-4440
AMD A6-5400K
VS
AMD RYZEN 5 1600X
Intel Core i5-4670S
VS
Intel Core i3-3220 9000
AT AT AT AT AT AT AT AT ATA AT AT AT AT ATA ATA ATA ATA ATA ATA ATA ATA ATA AMD A6-54002 AMD A6-54002 AMD A6-54002 AMD A6-54002 AMD A6-54002 AMD A6-54002 AMD A6-54002 AMD A6-54002 AMD A6-54002 AMD A6-54002 AMD Core i5-3470S
Intel Core i5-4670s
VS
Intel Core i7-3770
Complexation of prices
Users Reviews
1.
Specific central processor
9000 2 x 3.6GHZ
4 x 3.1.GHZ 9000 9000 9000 9000 9000 processor cycles shows how many processing cycles per second the processor can perform, given all its cores (processors). It is calculated by adding the clock speeds of each core or, in the case of multi-core processors, each group of cores.
2nd processor thread
More threads result in better performance and better multitasking.
3.speed turbo clock
3.8GHz
3.8GHz
When the processor is running below its limits, it can jump to a higher clock speed to increase performance.
4. Has unlocked multiplier
✔AMD A6-5400K
✖Intel Core i5-4670S
Some processors come with an unlocked multiplier and are easier to overclock, allowing for better performance in games and other applications.
5.L2 Cache
More L2 scratchpad memory results in faster results in CPU and system performance tuning.
6.L3 cache
Unknown. Help us offer a price. (AMD A6-5400K)
More L3 scratchpad memory results in faster results in CPU and system performance tuning.
7.L1 cache
More L1 cache results in faster results in CPU and system performance tuning.
8.core L2
0.5MB/core
0.25MB/core
More data can be stored in L2 scratchpad for access by each processor core.
9. L3 core
Unknown. Help us offer a price. (AMD A6-5400K)
1.5MB/core
More data can be stored in L3 scratchpad for access by each processor core.
Memory
1.RAM speed
1866MHz
1600MHz
Can support faster memory which speeds up system performance.
2.max memory bandwidth
21GB/s
25.6GB/s
This is the maximum rate at which data can be read from or stored in memory.
3rd DDR memory version
Unknown. Help us offer a price. (Intel Core i5-4670S)
DDR (Double Data Rate Synchronous Dynamic Random Access Memory) is the most common type of RAM. New versions of DDR memory support higher maximum speeds and are more energy efficient.
4.Memory channels
More memory channels increase the speed of data transfer between memory and processor.
5.max memory
Unknown. Help us offer a price. (AMD A6-5400K)
Maximum amount of memory (RAM).
6.bus baud rate
5.4GT/s
Unknown. Help us offer a price. (Intel Core i5-4670S)
The bus is responsible for transferring data between various components of a computer or device.
7.Supports memory debug code
✖AMD A6-5400K
✖Intel Core i5-4670S
Memory debug code can detect and fix data corruption.
It is used when necessary to avoid distortion, such as in scientific computing or when starting a server.
8.eMMC version
Unknown. Help us offer a price. (AMD A6-5400K)
Unknown. Help us offer a price. (Intel Core i5-4670S)
The newer version of eMMC — built-in flash memory card — speeds up the memory interface, has a positive effect on device performance, for example, when transferring files from a computer to internal memory via USB.
9.bus frequency
Unknown. Help us offer a price. (AMD A6-5400K)
Unknown. Help us offer a price. (Intel Core i5-4670S)
The bus is responsible for transferring data between various components of a computer or device
Geotagging
1. PassMark result
Unknown. Help us offer a price. (Intel Core i5-4670S)
This test measures processor performance using multithreading.
2nd PassMark result (single)
Unknown.
Help us offer a price. (Intel Core i5-4670S)
This test measures processor performance using a thread of execution.
3.Geekbench 5 result (multi-core)
Unknown. Help us offer a price. (AMD A6-5400K)
Unknown. Help us offer a price. (Intel Core i5-4670S)
Geekbench 5 is a cross-platform test that measures the performance of a multi-core processor. (Source: Primate Labs,2022)
4.Cinebench R20 result (multi-core)
Unknown. Help us offer a price. (AMD A6-5400K)
Unknown. Help us offer a price. (Intel Core i5-4670S)
Cinebench R20 is a benchmark that measures the performance of a multi-core processor by rendering a 3D scene.
5.Cinebench R20 result (single core)
Unknown. Help us offer a price. (AMD A6-5400K)
Unknown. Help us offer a price. (Intel Core i5-4670S)
Cinebench R20 is a test to evaluate the performance of a single core processor when rendering a 3D scene.
6.Geekbench 5 result (single core)
Unknown. Help us offer a price. (AMD A6-5400K)
Unknown. Help us offer a price. (Intel Core i5-4670S)
Geekbench 5 is a cross-platform test that measures the single-core performance of a processor. (Source: Primate Labs, 2022)
7. Blender test result (bmw27)
Unknown. Help us offer a price. (AMD A6-5400K)
Unknown. Help us offer a price. (Intel Core i5-4670S)
The Blender benchmark (bmw27) measures CPU performance by rendering a 3D scene. More powerful processors can render a scene in a shorter time.
8.Blender result (classroom)
Unknown. Help us offer a price. (AMD A6-5400K)
Unknown. Help us offer a price. (Intel Core i5-4670S)
The Blender (classroom) test measures CPU performance by rendering a 3D scene. More powerful processors can render a scene in a shorter time.
9.power per watt
Unknown. Help us offer a price. (Intel Core i5-4670S)
This means that the processor is more efficient, resulting in more performance per watt of power used.
Functions
1.uses multithreading
✖AMD A6-5400K
✖Intel Core i5-4670S
Multithreading technology (such as Intel’s Hyperthreading or AMD’s Simultaneous Multithreading) provides higher performance by dividing each physical processor core into logical cores, also known as flows. Thus, each core can run two instruction streams at the same time.
2. Has AES
✔AMD A6-5400K
✔Intel Core i5-4670S
AES is used to speed up encryption and decryption.
3. Has AVX
✔AMD A6-5400K
✔Intel Core i5-4670S
AVX is used to help speed up calculations in multimedia, scientific and financial applications, and to improve the performance of the Linux RAID program.
4.Version SSE
SSE is used to speed up multimedia tasks such as editing images or adjusting audio volume. Each new version contains new instructions and improvements.
5. Has F16C
✔AMD A6-5400K
✔Intel Core i5-4670S
F16C is used to speed up tasks such as image contrast adjustment or volume control.
6.bits transmitted at the same time
Unknown. Help us offer a price. (AMD A6-5400K)
Unknown. Help us offer a price. (Intel Core i5-4670S)
NEON provides faster media processing such as MP3 listening.
7. Has MMX
✔AMD A6-5400K
✔Intel Core i5-4670S
MMX is used to speed up tasks such as adjusting image contrast or adjusting volume.
8.Has TrustZone
✖AMD A6-5400K
✖Intel Core i5-4670S
The technology is integrated into the processor to ensure device security when using features such as mobile payments and streaming video using Digital Rights Management (DRM) technology ).
9.interface width
Unknown. Help us offer a price. (AMD A6-5400K)
Unknown. Help us offer a price. (Intel Core i5-4670S)
The processor can decode more instructions per clock (IPC), which means that the processor performs better
Price comparison
Cancel
Which CPUs are better?
This page is currently only available in English.
AMD A6-9225 vs Intel Core i5-8265U: What is the difference?
35 BALLLA
AMD A6-9225
54 BALLLA
Intel Core i5-8265U
Winter when comparing
VS
64 Facts compared to
AMD A6-9225
INTEL CORE AMEN Is A6-9225 better than Intel Core i5-8265U?
- 0.25MB/core more L2 cache per core?
0.5MB/core vs 0.25MB/core - Has FMA4?
Why Intel Core i5-8265U is better than AMD A6-9225?
- 23.
08% higher CPU speed?
4 x 1.6GHz vs 2 x 2.6GHz - 267MHz faster memory speed?
2400MHz vs 2133MHz - 6 more CPU threads?
8 vs 2 - 10°C higher than maximum operating temperature?
100°C vs 90°C - Semiconductor size 14nm smaller?
14nm vs 28nm - 4.59x higher PassMark score?
6130 vs 1336 - 0.8GHz higher turbo clock speed?
3.9GHz vs 3.1GHz - 96KB more L1 cache?
256KB vs 160KB
Which comparisons are the most popular?
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
ANTEL CELE CELE CELERON N4020 INTEL CELERON N4020 INTEL CELERON N4020 i5-8265u
VS
AMD Ryzen 3 5300U
AMD A6-9225
VS
AMD Ryzen 3 3200U
Intel Core I5-8265U
VS
9000 9000.
000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000
VS
Intel Core i3-1115g4
Intel Core i5-8265U
VS
AMD Ryzen 5 2500u
AMD AMD
Intel Core INTEL Core INTEL Core INTEL Core INTEL
Intel Core i5-1135g7
AMD A6-9225
VS
Intel Core i5-6200u
Intel Core i5-8265U
VS
AMD RYZEN 7 2700U
AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD AMD Intel Core i5-10210U
Intel Core i5-8265u
VS
Intel Core i3-1115G4
AMD A6-9225
VS
Intel Core i5-8250u
Intel Core I5-8265U
VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS
Comparison of prices
Users reviews
General rating
AMD A6-9225
2 Reviews of users
AMD A6-9225
8.
0 /10 9000
003
3 reviews of users
Intel Core i5-8265U
/10
3 Reviews of Users
Functions
Refract and Quality
/10
Votes
11 8. 10
3 Votes
Games
6.5 /10
2 VOTES
7.3 /10
3 VOTES
performance
8.0 /10 9 9
2 Votes
9
1 Votes
8.3 /10
3 Votes
performance
1. Ski -resistance of the central processor
2 x 2.6GHZ
4 x 1.6GHZ
The speed of the central processor shows how many processing cycles per second can be performed processor, considering all its cores (processors). It is calculated by adding the clock speeds of each core or, in the case of multi-core processors, each group of cores.
2nd processor thread
More threads result in better performance and better multitasking.
3.speed turbo clock
3.1GHz
3.9GHz
When the processor is running below its limits, it can jump to a higher clock speed to increase performance.
4. Has unlocked multiplier
✖AMD A6-9225
✖Intel Core i5-8265U
Some processors come with an unlocked multiplier and are easier to overclock, allowing for better performance in games and other applications.
5.L2 Cache
More L2 scratchpad memory results in faster results in CPU and system performance tuning.
6.L3 cache
Unknown. Help us offer a price. (AMD A6-9225)
More L3 scratchpad memory results in faster results in CPU and system performance tuning.
7.L1 cache
More L1 cache results in faster results in CPU and system performance tuning.
8.
core L2
0.5MB/core
0.25MB/core
More data can be stored in L2 scratchpad for access by each processor core.
9. L3 core
Unknown. Help us offer a price. (AMD A6-9225)
1.5MB/core
More data can be stored in L3 scratchpad for access by each processor core.
Memory
1.RAM speed
2133MHz
2400MHz
Can support faster memory which speeds up system performance.
2.max memory bandwidth
Unknown. Help us offer a price. (AMD A6-9225)
37.5GB/s
This is the maximum rate at which data can be read from or stored in memory.
3.DDR version
DDR (Double Data Rate Synchronous Dynamic Random Access Memory) is the most common type of RAM. New versions of DDR memory support higher maximum speeds and are more energy efficient.
4.
Memory channels
More memory channels increase the speed of data transfer between memory and processor.
5.Maximum memory
Maximum memory (RAM).
6.bus baud rate
Unknown. Help us offer a price. (AMD A6-9225)
The bus is responsible for transferring data between various components of a computer or device.
7.Supports memory troubleshooting code
✖AMD A6-9225
✖Intel Core i5-8265U
The memory error recovery code can detect and repair data corruption. It is used when necessary to avoid distortion, such as in scientific computing or when starting a server.
8.eMMC version
Unknown. Help us offer a price. (AMD A6-9225)
Unknown. Help us offer a price. (Intel Core i5-8265U)
Newer version of eMMC — built-in flash memory card — speeds up the memory interface, has a positive effect on device performance, for example, when transferring files from a computer to internal memory via USB.
9.bus frequency
Unknown. Help us offer a price. (AMD A6-9225)
Unknown. Help us offer a price. (Intel Core i5-8265U)
The bus is responsible for transferring data between various components of a computer or device
Geotagging
1. PassMark result
This test measures processor performance using multi-threading.
2. PassMark result (single)
This test measures processor performance using a thread of execution.
3.Geekbench 5 result (multi-core)
Geekbench 5 is a cross-platform benchmark that measures the performance of a multi-core processor. (Source: Primate Labs, 2022)
4. Cinebench R20 result (multi-core)
Unknown. Help us offer a price. (Intel Core i5-8265U)
Cinebench R20 is a test that measures the performance of a multi-core processor by rendering a 3D scene.
5.Cinebench R20 result (single core)
Unknown. Help us offer a price. (Intel Core i5-8265U)
Cinebench R20 is a test to evaluate the performance of a single core processor when rendering a 3D scene.
6.Geekbench 5 result (single core)
Geekbench 5 is a cross-platform test that measures the single core performance of a processor. (Source: Primate Labs, 2022)
7. Blender test result (bmw27)
Unknown. Help us offer a price. (AMD A6-9225)
731.93seconds
The Blender benchmark (bmw27) measures CPU performance by rendering a 3D scene. More powerful processors can render a scene in a shorter time.
8.Blender result (classroom)
Unknown. Help us offer a price. (AMD A6-9225)
1694.63seconds
The Blender (classroom) benchmark measures CPU performance by rendering a 3D scene.
More powerful processors can render a scene in a shorter time.
9.performance per watt
This means that the processor is more efficient, giving more performance per watt of power used.
Functions
1.uses multithreading
✖AMD A6-9225
✔Intel Core i5-8265U
processor cores into logical cores, also known as threads. Thus, each core can run two instruction streams at the same time.
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 applications, and to improve the performance of the Linux RAID program.
4.Version SSE
SSE is used to speed up multimedia tasks such as editing images 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 image contrast adjustment or volume control.
6.bits transmitted at the same time
Unknown. Help us offer a price. (AMD A6-9225)
Unknown. Help us offer a price. (Intel Core i5-8265U)
NEON provides faster media processing such as MP3 listening.
7. Has MMX
✔AMD A6-9225
✔Intel Core i5-8265U
MMX is used to speed up tasks such as adjusting image contrast or adjusting volume.
8.Has TrustZone
✖AMD A6-9225
✖Intel Core i5-8265U
The technology is integrated into the processor to ensure device security when using features such as mobile payments and streaming video using Digital Rights Management (DRM) technology ).
9.interface width
Unknown. Help us offer a price. (AMD A6-9225)
Unknown. Help us offer a price. (Intel Core i5-8265U)
The processor can decode more instructions per clock (IPC), which means the processor performs better
Price comparison
Cancel
Which CPUs are better?
Comparison AMD A6-9220 vs Intel Core i5-6200U which is better?
Main / Processor / AMD A6-9220 vs Intel Core i5-6200U
AMD A6-9220
22%
Devicelist
VS
Intel Core i5-6200u
48%
Devicelist
We compared the AMD A6-9220 and Intel Core i5-6200u and compiled you a list of benefits and a comparison table. Find out which one to choose in 2022.
Advantage AMD A6-9220
|
Maximum frequency |
|
2.9 GHz 0.1 GHz (3.6%) better than vs 2.8 GHz |
|
Maximum core temperature |
|
90°C -10°C (-10%) better than vs 100 °C |
|
Power Demand (TDP) |
|
10 W -5 W (-33. vs 15 W |
3%) better than Benefits of Intel Core i5-6200U
Comparison winner
|
threads |
|
4 2 (100%) better than vs 2 |
|
Technological process |
|
14 nm -14 nm (-50%) better than vs 28 nm |
|
Number of transistors |
|
1750 million 550 million (45.8%) better than vs 1200 million |
|
Passmark |
|
3041 1704 (127.4%) better than vs 1337 |
|
Cinebench 10 32-bit single-core |
|
4383 1951 (80. vs 2432 |
|
Cinebench 10 32-bit multi-core |
|
9872 5931 (150.5%) better than vs 3941 |
|
Cinebench 11.5 64-bit single-core |
|
115 46 (66.7%) better than vs 69 |
|
Cinebench 15 64-bit multi-core |
|
289 177 (158%) better than vs 112 |
|
WinRAR 4.0 |
|
2041 1271 (165.1%) better than vs 770 |
|
x264 encoding pass 1 |
|
100 53 (112.8%) better than vs 47 |
|
x264 encoding pass 2 |
|
19 10 (111. vs 9 |
|
TrueCrypt AES |
|
2 1 (100%) better than vs 1 |
|
3DMark06 CPU |
|
3787 1534 (68.1%) better than vs 2253 |
|
Geekbench 3 32-bit single-core |
|
2726 928 (51.6%) better than vs 1798 |
|
Geekbench 3 32-bit multi-core |
|
5797 2876 (98.5%) better than vs 2921 |
|
Geekbench 4.0 64-bit single-core |
|
3507 1622 (86%) better than vs 1885 |
|
Geekbench 4. |
|
6502 3697 (131.8%) better than vs 2805 |
2%) better than 
1%) better than 
0 64-bit multi-core | General | |
|
Type |
|
| For laptops | For laptops |
|
Architecture code name |
|
| Stoney Ridge | Skylake |
|
Cores A large number of cores improves performance in multi-threaded applications. |
|
| 2 | 2 |
|
Threads More threads help the cores process information more efficiently. Real performance will be noticeable in very specific tasks (video editing, databases). |
|
| 2 | 4
2 (100%) better than |
|
Process |
|
| 28 nm | 14 nm
-14 nm (-50%) better than |
|
Chip size |
|
124. 5 mm2 |
99 mm2 |
|
Number of transistors |
|
| 1200 million | 1750 million
550 million (45.8%) better than |
|
Maximum frequency Higher clock speed processors perform more calculations per second and thus provide better performance. |
|
| 2.9GHz
Better than at 0.1 GHz (3.6%) |
2.8 GHz |
|
Support 64 bit |
|
|
Max. number of processors in configuration |
|
| n/a | 1 |
|
Socket |
|
| BGA | FCBGA1356 |
|
AMD-V |
|
|
Series |
|
| Bristol Ridge | Intel Core i5 |
|
Release price |
|
| n/a | 281 $ |
|
Value for money The sum of all the advantages of the device divided by its price. |
|
| n/a | 76.4% |
|
Maximum core temperature |
|
| 90 °C
-10°C (-10%) better than |
100 °C |
|
vPro |
|
|
TXT Intel Trusted Execution Technology for hardware-based malware protection. For each protected program, the processor allocates its own isolated section of RAM. |
|
|
PCI Express revision |
|
| n/a | 3.0 |
|
Number of PCI-Express lanes |
|
| n/a | 12 |
|
Secure Key |
|
|
MPX |
|
| n/a | + |
|
Identity Protection |
|
| n/a | + |
|
SGX |
|
| n/a | Yes with Intel® ME |
|
OS Guard |
|
| n/a | + |
|
Flex Memory Access |
|
| n/a | + |
|
Quick Sync |
|
| n/a | + |
|
eDP |
|
| n/a | + |
|
HDMI |
|
| n/a | + |
|
Maximum resolution via VGA |
|
| n/a | N/A |
|
My WiFi |
|
| n/a | + |
|
Level 1 Cache The fastest level of cache that works directly with the core. |
|
| 160 Kb | 128 Kb |
|
Level 2 cache |
|
| 1 Mb | 512 Kb |
|
Level 3 cache |
|
| n/a | 3 Mb |
|
Power Demand (TDP) Calculated thermal power indicates the average heat dissipation in load operation, |
|
| 10W
-5 W (-33.3%) better than |
15W |
|
EDB |
|
| n/a | + |
|
Video memory size |
|
| n/a | 32 GB |
|
Clear Video |
|
| n/a | + |
|
InTru 3D |
|
| n/a | + |
|
4K support |
|
| n/a | + |
|
DisplayPort |
|
| n/a | + |
|
DVI |
|
| n/a | + |
|
Smart Response |
|
| n/a | + |
The more%, the better the quality per unit price in comparison with all analogues. 
The larger the cache, the better the performance. | 3041
1704 (127. |
||
|
Cinebench 10 32-bit single-core |
||
| 2432 | 4383
1951 (80.2%) better than |
|
|
Cinebench 10 32-bit multi-core |
||
| 3941 | 9872
5931 (150.5%) better than |
|
|
Cinebench 11.5 64-bit single-core |
||
| 69 | 115
46 (66.7%) better than |
|
|
Cinebench 15 64-bit multi-core |
||
| 112 | 289
177 (158%) better than |
|
|
WinRAR 4.0 |
||
| 770 | 2041
1271 (165.1%) better than |
|
|
x264 encoding pass 1 |
||
| 47 | 100
53 (112.8%) better than |
|
|
x264 encoding pass 2 |
||
| 9 | 19
10 (111. |
|
|
TrueCrypt AES |
||
| 1 | 2
1 (100%) better than |
|
|
3DMark06 CPU |
||
| 2253 | 3787
1534 (68.1%) better than |
|
|
Geekbench 2 |
||
| 3461 | n/a | |
|
Geekbench 3 32-bit single-core |
||
| 1798 | 2726
928 (51.6%) better than |
|
|
Geekbench 3 32-bit multi-core |
||
| 2921 | 5797
2876 (98.5%) better than |
|
|
Geekbench 4.0 64-bit single-core |
||
| 1885 | 3507
1622 (86%) better than |
|
|
Geekbench 4.0 64-bit multi-core |
||
| 2805 | 6502
3697 (131.8%) better than |
|
|
3DMark Fire Strike Physics |
||
| n/a | 3700 | |
4%) better than 
1%) better than | Technology and additional instructions | |
|
Extended instructions |
|
| n/a | Intel® SSE4. 1, Intel® SSE4.2, Intel® AVX2 |
|
Turbo Boost |
|
| n/a | 2.0 |
|
Idle States |
|
|
Enhanced SpeedStep (EIST) Technology from Intel that allows the processor to slow down to its lowest frequency to conserve power when the processor is idle. |
|
|
Thermal Monitoring |
|
|
Hyper-Threading Intel hardware technology that allows multiple threads to be processed on each processor core. For server applications, the performance improvement is up to 30%. |
|
|
AES-NI Technology from Intel that speeds up the AES encryption process. |
|
| n/a | + |
|
AVX The presence of AVX instructions improves performance in floating point and processor-intensive operations |
|
| RAM parameters | |
|
RAM types |
|
| n/a | DDR4-2133, LPDDR3-1866, DDR3L-1600 |
|
Allowable memory The maximum amount of RAM that can be used with this processor. |
|
| n/a | 32 GB |
|
Number of memory channels |
|
| n/a | 2 |
| Virtualization Technologies | |
|
VT-x |
|
|
EPT |
|
|
VT-d Intel virtualization technology allows you to forward devices on the PCI bus to the guest operating system so that it can work with them using its standard tools. |
|
| Integrated graphics | ||
1. 00 GHz |
||
|
Maximum number of monitors |
||
| n/a | 3 | |
|
Clear Video HD |
||
|
Video core The presence of the video core allows you to use your computer without using a video card. |
||
| AMD Radeon R4 (Stoney Ridge) (- 655 MHz) | + | |
|
Maximum resolution via HDMI 1.4 |
||
| n/a | 4096×2304@24Hz | |
|
Maximum resolution via eDP |
||
| n/a | 4096×2304@60Hz | |
|
Maximum resolution via DisplayPort |
||
| n/a | 4096×2304@60Hz | |
|
DirectX |
||
| n/a | 12 | |
|
OpenGL |
||
| n/a | 4. 5 |
|
Intel Core i3 vs. AMD A8 and A6 / Processors and Memory
The reason for writing this article was the arrival of the new Intel Core i3-2125 processor in our laboratory. This processor itself is not so hot what a novelty. Not only is it based on the well-known Sandy Bridge microarchitecture, but it doesn’t even offer increased clock speeds. Everything that Intel has done to release this processor is described in one phrase: in the long-sold Core i3-2120, the Intel HD Graphics 2000 graphics core is replaced by a more powerful modification — Intel HD Graphics 3000.
The Core i3-2125 is so similar to the Core i3-2120 that even the latest version of CPU-Z has difficulty identifying it correctly
Actually, there is nothing new in the HD Graphics 3000 graphics core either. generations where such graphics are used everywhere. In the bulk of desktop LGA1155 products, Intel preferred to use the simpler and slower HD Graphics 2000 core, in which the number of execution units was halved — from 12 to 6.
But recently, the HD Graphics 3000 core began to penetrate into inexpensive processors for desktop systems of the Core i3 series, which led to the appearance first of the Core i3-2105, and now the Core i3-2125.
The integrated Intel HD Graphics 3000 graphics core in the Core i3-2125 is distinguished by the presence of 12 executive units
It turns out that there is not much interesting in the new processor. But the reasons for the beginning of the penetration of HD Graphics 3000 graphics into desktop products is a much more interesting question. The answer to which, obviously, should be sought in the trends of the processor market as a whole. The fact is that this market is currently experiencing a kind of «velvet» revolution, during which power is transferred from traditional CPUs to hybrid processors — APUs. According to the results of the second quarter, the share of processors with an integrated graphics core was already about 60%, which gives manufacturers an unambiguous signal that the future belongs to such processors.
In the meantime, Intel has prepared for the changing market conditions not in the best way. And at this sudden turn in the interests of consumers, AMD turned out to be the leader, not only investing in one of the leading developers of graphics solutions in a timely manner, but also starting to implement these solutions in its processors at a very timely manner. The resulting processors of the Llano series were so powerful that they immediately achieved the title of the standard of modern APU, which the representatives of the Core i3 family that compete with them clearly fell short of. The situation is especially unpleasant for Intel in terms of graphics performance. A few months ago, we spoke with admiration of the Sandy Bridge graphics core, which at the time of its release not only set a new and fairly high performance standard for integrated graphics, but also showed that integration is not a diagnosis at all. However, after the release of AMD A-series processors, it became clear that hybrid solutions are capable of much more.
Against this background, the Intel HD Graphics 2000 core in Sandy Bridge desktop processors began to look very pale, and Intel began to hastily replace it with a faster version. Which, according to the company, should improve the impression of the Core i3 family as competitors to AMD Llano.
So, it would seem that a completely ordinary announcement of an ordinary product, Core i3-2125, led us to a global problem — the search for the best APU of today.
⇡#What is APU?
Deciphering the abbreviation APU — Accelerated Processing Unit (accelerated processing unit) does not even suggest why this class of processors is better than traditional CPU — Central Processing Unit (central processing units). Therefore, detailed explanations should be consulted.
From a hardware point of view, which is followed by the vast majority, the APU is a hybrid device that combines traditional general-purpose computing cores with a graphics core on a single semiconductor chip. At the same time, AMD insists that the graphics core should have an architecture in the form of an array of parallel stream processors capable of taking on a countable load.
Which, however, is easily explained by the fact that AMD cores are exactly like that.
However, the definition of APU can also be approached from a software point of view, taking into account the possibility of transferring calculations from general-purpose processor cores to parallel graphics pipelines. And from this position, the main idea of introducing hybrid processors becomes clear, which is that this is another way to increase the performance of modern systems. Since software is clearly evolving towards parallel computing, adding an array of parallel GPU pipelines to traditional computing resources can be a very beneficial step. This is precisely what AMD stands up for, which offers to add stream processors of its Radeon HD graphics family to x86-cores, not only in graphic programs, but also in commonly used applications.
The fact that Radeon HD series graphics are quite capable of working on computing tasks has long been known, for this purpose ATI Stream technology was developed several years ago.
However, now we are talking about the fact that modern programs for hybrid processors should use x86 and graphics cores together, extracting maximum performance from this symbiosis. The OpenCL programming interface is best suited for this purpose, support for which can also be considered one of the key features of the APU.
The formula is simple: CPU+GPU=APU
AMD is the main ideologist of hybrid processors, so it’s only natural that its Llano family products fit perfectly into the above concept at any level. With Intel, the situation is more complicated. On the one hand, Sandy Bridge can be considered an APU, since these processors really combine x86 cores and graphics on a single semiconductor chip. However, on the other hand, Intel Bromolow graphics cores (HD Graphics 2000/3000) are only graphics, they cannot count. Therefore, if the ability to compute on the graphics core is meant to be a mandatory attribute of the APU, Sandy Bridge does not fall under this definition.
However, the OpenCL API is still supported by Intel processors. That is, programs written for APUs and using OpenCL will work on systems based on second-generation Core processors, but they will be executed exclusively by means of x86 kernels.
The classification of modern APUs is additionally complicated by the fact that one of the most popular tasks solved by the parallel stream processors of the graphics core, HD video encoding, in Sandy Bridge processors can be executed on the Quick Sync block included in the graphics. In other words, despite the fact that modern Intel graphics do not allow you to take on parallel computing in a general sense, it can solve highly specialized tasks related to HD video encoding.
In this somewhat confusing situation, we tend to define APUs precisely by hardware architecture, and therefore our comparison of hybrid processors will include not only AMD A-series representatives, but also Intel Core i3 processors that fall into the same price category with them.
Moreover, the distribution of programs optimized for the APU hybrid architecture is at an embryonic level, and at this stage it is a very difficult task to find common applications that are different from synthetic tests, accelerated by Llano GPUs and not accelerated by Sandy Bridge.
⇡#Description of test systems
So, the circle of potential contenders for the title of the best APU is outlined. These are processors of the AMD Llano family in modifications A8 and A6 and falling into the same price category and competing Core i3 processors, especially their variants with the fastest graphics core Intel HD Graphics 3000.
We did not include more than fast quad-core Sandy Bridge, because not only do they not fall into the category of 100-dollar APUs, but also do not come with fast graphics. In other words, these are under-APUs, in which a clear bias is made towards general-purpose x86 cores, and therefore they can be considered representatives of a slightly different class of processors.
On the other hand, we additionally tested the Core i3 processor with slow Intel HD Graphics 2000, the results of which will help determine the gain that Sandy Bridge desktop processors get when they are equipped with a more advanced graphics core.
As a result, two platforms took part in the tests — Intel’s LGA1155 and AMD’s Socket FM1 platform.
LGA1155 platform :
- Core i3-2125, Core i3-2120, and Core i3-2105 processors;
- Motherboard ASUS P8Z68-V PRO;
- Memory 4 GB DDR3-1600 9-9-9-27 (Kingston KHX1600C8D3K2/4GX).
Platform Socket FM1:
- AMD A8-3850 and AMD A6-3650 processors;
- Motherboard Gigabyte GA-A75M-UD2H;
- Memory 4 GB DDR3-1600 9-9-9-27 (Kingston KHX1600C8D3K2/4GX).
In all these platforms, the Western Digital VelociRaptor WD3000HLFS hard drive remained constant. Testing was carried out in the operating system Microsoft Windows 7 SP1 Ultimate x64.
All tests were carried out exclusively with integrated graphics processors. The following graphics driver versions were used:
- AMD Vision Engine Control Center 11.8;
- Intel Graphics Media Accelerator Driver 15.22.1.64.2361.
Software used:
- CPU-Z 1.58;
- GPU-Z 0.5.4;
- Futuremark PCMark 7 1.0.4;
- Futuremark 3DMark Vantage 1.1.0;
- SuperPi mod 1.5 XS;
- wPrime 2.05;
- WinRAR 4.01 x64;
- 7-zip 9.20 x64;
- Fritz Chess Benchmark 4.2;
- MAXON Cinebench Release 11.5 x64;
- TechARP x264 HD Benchmark 4.0.
And games:
- Crysis 2 1.9;
- Far Cry 2 1.0.3;
- Metro 2033: The Last Refuge 1.2;
- DiRT 3 1.1;
- Mafia 2 1.02;
- Metro 2033: The Last Refuge 1.2;
- Tom Clancy’s H.A.W.X. 2 1.04.
It should be noted that, due to the lack of DirectX 11 support in Intel graphics cores, testing in all games was carried out in DirectX 9/DirectX 10 modes.
At the same time, we used settings corresponding to medium image quality and a resolution of 1280×800 with x16 anisotropic filtering and disabled full-screen smoothing. Vertical synchronization was disabled, no changes were made to the driver settings.
⇡#Characteristics of tested APU
Although we selected only five processors for testing, the differences in their characteristics are so significant that they deserve a separate section. And, oddly enough, a particularly strong difference can be traced in the specifications of the graphics cores, which are especially emphasized in the case of the APU. The accelerators of the HD Graphics 2000 and HD Graphics 3000 series used by Intel in their processors, as well as the graphics cores Radeon HD 6550D and Radeon HD 6530D embedded in the A8 and A6 processors, differ in clock speeds and in the number of shader pipelines. Therefore, additional parameters are added to the usual CPU specifications such as the number of cores, clock speed and cache size.
|
AMD Radeon HD 6530D |
Intel HD Graphics 2000 |
|
AMD Radeon HD 6550D |
Intel HD Graphics 3000 |
The GPU-Z diagnostic utility, which we usually rely on to determine the GPU configuration, in the case of APU graphics cores, gives limited and sometimes even incorrect information. For example, its readings cannot be relied upon in terms of frequencies and support for the OpenCL interface, and for Intel HD Graphics 2000 it even reports the wrong number of shader pipelines.
The matter is complicated by the fact that the approaches of APU manufacturers to differentiation of the model range are not unanimous. Intel inserts various graphics modifications in both older and lower Core i3 models, while AMD uses a faster version of its graphics core only in more expensive Socket FM1 processors.
Therefore, in order to get a complete impression of the formal properties of the tested hybrid processors, we have compiled the following table of specifications. 9Core i3-2105
*Preliminary information
Be aware that AMD and Intel processors have a completely different microarchitecture, which is why a direct comparison of their clock frequencies and other numerical parameters does not make it possible to form a correct opinion about relative performance .
The same applies to the characteristics of graphics cores.
So it’s time to move on to the results of practical tests, which will certainly put everything in its place.
⇡#Computational test results
First of all, APUs were tested on our standard set of benchmarks for classic processors. Naturally, in this case, we are not talking about any use of the capacities of the graphics cores, except for the fact that the graphics built into the APU were engaged in displaying the operating system interface.
There is some parity between the Intel Core i3 APUs and the AMD A-series. Intel processors perform better in SuperPi and in Futuremark’s benchmarks, but slightly lose out to competitors under severe multi-threaded load created when video is transcoded with the x264 codec, during the final rendering in Cinebench, or during arithmetic calculations aimed at finding prime numbers in wPrime.
The observed ratio of results is largely explained by the structure of AMD and Intel processors.
A-series processors are quad-core, while alternative Core i3 are dual-core CPUs with support for Hyper-Threading technology, which adds two more “virtual” cores to an honest pair of cores. The fact that the performance of such different processors is on the same level is the result of the advancement of the new Sandy Bridge microarchitecture and the simultaneous wretchedness of the four-year-old Stars microarchitecture, which, for lack of anything better from AMD, penetrated into the new Llano processors. It turns out that in terms of performance, one Sandy Bridge core is equivalent to a pair of Llano processor cores. And this can be considered both the success of the AMD marketing department, which managed to masterfully tune the characteristics of the A-series processors so that they do not look like hopelessly outdated products, and the success of the Intel engineering team, which has significantly increased the specific performance of its microarchitecture over the past few years.
⇡#Graphic test results
The second part of the tests is gaming applications.
Here, the APU’s power is fully utilized, since the graphics core is loaded with processing and output of 3D graphics.
In addition to the results of gaming tests, we also conducted an OpenGL benchmark from the Cinebench package, which characterizes APU performance when working with professional graphics.
In graphical tests, the picture is changing — we are no longer talking about any equality. The HD Graphics 3000 graphics core, which Intel has taken care of introducing into desktop processors, certainly seriously improves performance. On the example of our tests, we can state about a 50% advantage of the Core i3-2125 over the Core i3-2120 with a slow two thousandth graphics modification. However, for the Core i3-2125 to be able to compete at least with the cheaper AMD A6-3650, this is clearly not enough. The advantage of AMD’s APUs in 3D graphics workloads is overwhelming, and Intel has obviously lost this round of competition.
And if we add the lack of support for DirectX 11 in Intel’s APUs to the results shown in the diagrams, then the situation for the current solutions of this manufacturer seems even more hopeless.
Only the next generation of the Ivy Bridge microarchitecture can fix it, the Carlow graphics core in which will receive additional execution units, OpenCL support, and DirectX 11 compatibility. parts of the screen resolution and image quality settings allow you to play almost any modern game without resorting to the services of an external video card. Intel’s APU options, on the other hand, deliberately put an end to the most demanding games, so using them as the basis of a budget gaming system is not the most reasonable choice.
⇡#Overclocking
Overclocking processors and graphics cards is a commonly used technique to increase system performance. Let’s take a look at how the APU overclocking is, where computing and graphics resources are brought together.
Intel Core i3, like other processors of the Sandy Bridge family, not related to the overclocking K-series, have a locked multiplier. Increasing the frequency of the base oscillator in LGA1155 systems is greatly hindered by its unification and use not only for the needs of the processor, but also for clocking the chipset and the controllers built into it.
As a result, the maximum overclocking of the Core i3, which owners of systems with this APU can hope for, does not exceed 5%.
However, this only applies to general purpose x86 kernels. The graphics core of the Core i3 processors uses an independent and changeable multiplier to form its own frequency. This is what allows you to seriously increase the frequency of the Intel HD Graphics 2000/3000 above the nominal 1.1 GHz.
So, in the course of our experiments on the Core i3-2105 and Core i3-2125, we managed to increase the frequency of the base clock generator by only 4% — up to 104 MHz. On the other hand, the maximum multipliers for the graphics frequency increased without problems to x16 and x18, respectively, and at the same time there was no talk of any problems with stable performance! That is, Intel APUs, although they limit the overclocking of their “processor” part to rigid frames, can significantly increase the speed of the built-in video core, whose frequency in overclocking mode can reach an impressive 1.
6-1.8 GHz.
AMD A-series processors, like Core i3, also have a fixed multiplier, and the clock generator in Socket FM1 systems is also tied not only to all processor frequencies, but also to adjacent I / O binding frequencies of the system logic set. Moreover, the multiplier responsible for the frequency of the graphics core is also blocked in Llano processors. But, fortunately, the situation with overclocking is still not hopeless. Motherboard manufacturers have found a way to switch dividers for the frequency of the chipset controllers. So, if you do not pay attention to certain shortcomings, such as the inoperability during overclocking of the D-Sub analog monitor output and the AHCI mode of the SATA controller, the clock generator frequency can be seriously increased without losing the overall stability of the system.
In practice, having made the indicated sacrifices, we managed to overclock the base clock generator from the nominal 100 MHz to 140 MHz on the A8-3850 processor and to 144 MHz on the A6-3650 processor.
This increase in the base frequency provided an increase in the speed of the graphics core of the A6-3650 processor to 640 MHz, and the graphics in the A8-3850 to 840 MHz. As for general-purpose x86 cores, to ensure stable operation of the APU during overclocking, the main processor multiplier had to be reduced to 25x for the A6-3650 processor and to 26x for the A8-3850 processor. Nevertheless, the resulting processor frequency was still significantly higher than the nominal and amounted to 3.6 and 3.64 GHz, respectively.
All overclocking twists and turns are well described by the following table, which summarizes the information about the frequencies that were obtained as a result of overclocking experiments on the APUs that participated in the tests. Core i3-2105
The results of the 3DMark Vantage test illustrate the increase in performance obtained with such overclocking.
AMD’s APUs overclock significantly better than competing Intel offerings. Therefore, while in the CPU benchmark in the non-overclocked mode, the Core i3 were in the lead, after the overclocking procedure, the A6 and A8 are already in the lead.
Overclocking the graphics core allows you to increase the «graphic» results in 3DMark Vantage much more noticeably. For example, increasing the frequency of the Intel HD Graphics 3000 core can bring its performance almost to the speed of the Radeon HD 6530D core from AMD A6. However, the increase in the number of points that gives graphics overclocking in AMD’s APUs is no less impressive and leaves no hope of competing solutions for competing solutions.
It turns out that, in general, overclocking has a more beneficial effect on the performance of Llano processors, allowing them to significantly increase not only graphics, but also computational performance. And this means that if you consider yourself one of those enthusiasts who have only a hard drive working in normal mode from the components of the system unit, the choice should clearly be stopped on AMD processors.
⇡#Conclusions
The tests carried out leave no doubt that the best APUs at the moment are offered by the founder of this direction — AMD. Having developed a new concept, the manufacturer meticulously thought out its implementation in hardware, so if you are looking for a basis for an inexpensive gaming system, and the performance provided by modern integrated graphics does not disgust you, you need to stop the choice on the Socket FM1 platform and processors of the family Llano. Although these hybrid processors are based on a fairly old microarchitecture, they look very confident in real applications and are in no way inferior to the newfangled Sandy Bridge of similar price even with a purely computing load. When the graphics core comes into play, representatives of the Llano family leave the Core i3 no chance of revenge at all.
Intel’s attempts to somehow raise the graphics performance of its own processors to a competitive level by introducing a faster version of the graphics core into them turned out to be doomed to failure.
The difference in performance between AMD and Intel integrated graphics processors is so great that the best Intel HD Graphics 3000 core is almost 40% behind even the simplified Radeon HD 6530D core, not to mention the full-fledged Radeon HD 6550D. In addition, the graphics offered by Intel do not provide the proper level of functionality, since it does not support modern DirectX 11 and OpenCL programming interfaces.
Unfortunately, Intel will not be able to change the current situation with some cosmetic measures. And announcements of products like the Core i3-2125 have no effect on the balance of power in the hybrid processor market. Really serious changes can happen only with the release of fundamentally new products, for example, promising Intel Ivy Bridge processors. They will implement both a faster graphics core and support for all the necessary APIs. And just then, perhaps, we will be able to write an article about real competition in the APU market.
Compare AMD A6 7400K and Intel Core i5 4258U
AMD A6 7400K
3.
5GHz | 2 cores | FM2+
VS
Intel Core i5 4258U
2.4GHz | 2 nuclei
Benchmark
General result
Based on 9 tests:
Intel Core i5 4258U faster than 23.85%
AMD A6 7400K
Intel Core I5 4258U
123.81 GEEKH 9000. core)
3420
Intel Core i5 4258U
5341
Reasons to choose AMD A6 7400K
- High frequency (3.5 GHz vs 2.4 GHz) means more operations that the processor performs in 1 second
Unlocked multiplier allows easier to overclock
Reasons to choose Intel Core i5 4258U
- Smaller CPU (22nm vs 28nm) allows you to get more performance with less heat
- More threads (4 vs. 2) allows more processes to run simultaneously
- Higher critical temperature (100°C vs. 70°C) allows the processor to operate in harsher temperatures
Specifications
| AMD A6 7400K | Intel Core i5 4258U | |
| Frequency | 3.
|