AMD 7th Gen Bristol Ridge A10-9700 4 Core 3.5 GHz Socket AM4 65W Desktop Processor w/ Radeon R7 Graphics up to 3.5 GHz
-
Product
-
Description
-
Reviews (0)
-
What’s in the box
Description
Highlight
- Superior Power efficiency with Thermal Design Power: 65W
- Enhanced HD video streaming and superb online gaming
- System Memory Speed: 2400MHz
- System Memory Type: DDR4
- 7th Gen Processor
- Graphics Model: Radeon™ R7 Series
- 2MB L2 Cahce
AMD A-SERIES 7TH GEN A10-9700 PROCESSOR
|
|
Specifications
|
|
CPU Cores
|
|
GPU Cores
|
|
Compute Cores
|
|
Base Clock
|
|
Max Boost Clock
|
|
Total L2 Cache
|
|
Unlocked
|
|
CMOS
|
|
Package
|
|
PCI Express Version
|
|
Default TDP / TDP
|
|
cTDP
|
|
Max Temps
|
|
SYSTEM MEMORY
|
|
Max System Memory Speed
|
|
System Memory Type
|
|
Memory Channels
|
|
Graphics Specifications
|
|
Graphics Frequency
|
|
Graphics Model
|
|
Key Features
|
|
Display Port
|
|
HDMI™
|
|
Foundation
|
|
Product Family
|
|
Product Line
|
|
Platform
|
|
OPN Tray
|
|
OPN PIB
|
|
Launch Date
|
|
Codename
|
Reviews (0)
view all
back
0 reviews
What’s in the box
1 x AMD 7th Gen Bristol Ridge A10-9700 4 Core 3.
5 GHz Socket AM4 65W Desktop Processor w/ Radeon R7 Graphics up to 3.5 GHz
Tags:
A10-9700
AMD A-SERIES
Socket AM4
Customer Reviews
musliazhan_mustafa
13 October 2021
izwandy_yusof
12 October 2021
lee_lai_kuan
9 October 2021
wei_giap
9 October 2021
AMD A10-9700 vs Intel Core i5-7200U: What is the difference?
48points
AMD A10-9700
43points
Intel Core i5-7200U
vs
64 facts in comparison
AMD A10-9700
Intel Core i5-7200U
Why is AMD A10-9700 better than Intel Core i5-7200U?
- 2.8x faster CPU speed?
4 x 3.5GHzvs2 x 2.5GHz - 267MHz higher ram speed?
2400MHzvs2133MHz - 729MHz faster GPU clock speed?
1029MHzvs300MHz - 3.6MB bigger L2 cache?
4.1MBvs0.5MB - 0.
7GHz higher turbo clock speed?
3.8GHzvs3.1GHz - 448KB bigger L1 cache?
512KBvs64KB - Has an unlocked multiplier?
- 0.77MB/core more L2 cache per core?
1.02MB/corevs0.25MB/core
Why is Intel Core i5-7200U better than AMD A10-9700?
- 10°C higher maximum operating temperature?
100°Cvs90°C - 14nm smaller semiconductor size?
14nmvs28nm - 50W lower TDP?
15Wvs65W - 12.12% higher PassMark result (single)?
1785vs1592 - Uses multithreading?
- 79.3 more performance per watt?
101.9vs22.6 - 18 more GPU execution units?
24vs6 - Has NX bit?
Which are the most popular comparisons?
AMD Ryzen 5 5500U
vs
Intel Core i5-1135G7
AMD Ryzen 3 3250U
vs
Intel Core i3-1115G4
AMD Ryzen 3 5300U
vs
Intel Core i3-1115G4
AMD Ryzen 5 3500U
vs
Intel Core i5-10210U
AMD Ryzen 7 3700U
vs
Intel Core i5-10210U
AMD Ryzen 7 5800H
vs
Intel Core i7-11800H
AMD Ryzen 5 3500U
vs
Intel Core i3-1115G4
AMD Ryzen 5 4600H
vs
Intel Core i5-10300H
Intel Core i3-1115G4
vs
Intel Core i5-1135G7
AMD Ryzen 5 5500U
vs
Intel Core i3-1115G4
Price comparison
User reviews
Overall Rating
AMD A10-9700
5 User reviews
AMD A10-9700
9.
2/10
5 User reviews
Intel Core i5-7200U
4 User reviews
Intel Core i5-7200U
9.0/10
4 User reviews
Features
Value for money
9.0/10
4 votes
9.8/10
4 votes
Gaming
9.0/10
4 votes
8.0/10
4 votes
Performance
8.8/10
4 votes
9.3/10
4 votes
Reliability
9.8/10
4 votes
9.5/10
4 votes
Energy efficiency
10.0/10
4 votes
7.3/10
4 votes
Performance
1.CPU speed
4 x 3.5GHz
2 x 2.5GHz
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.8GHz
3.1GHz
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 A10-9700
✖Intel Core i5-7200U
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 A10-9700)
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
1.02MB/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 A10-9700)
1.5MB/core
More data can be stored in the L3 cache for access by each core of the CPU.
Memory
1.RAM speed
2400MHz
2133MHz
It can support faster memory, which will give quicker system performance.
2.maximum memory bandwidth
38.4GB/s
34.1GB/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 A10-9700)
The bus is responsible for transferring data between different components of a computer or device.
7.Supports ECC memory
✖AMD A10-9700
✖Intel Core i5-7200U
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 A10-9700)
Unknown. Help us by suggesting a value. (Intel Core i5-7200U)
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 A10-9700)
The bus is responsible for transferring data between different components of a computer or device.
Benchmarks
1.PassMark result
This benchmark measures the performance of the CPU using multiple threads.
2.PassMark result (single)
This benchmark measures the performance of the CPU using a single thread.
3.Geekbench 5 result (multi)
Geekbench 5 is a cross-platform benchmark that measures a processor’s multi-core performance. (Source: Primate Labs, 2022)
4.Cinebench R20 (multi) result
Unknown. Help us by suggesting a value. (AMD A10-9700)
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 A10-9700)
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 A10-9700)
1276.39seconds
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 A10-9700)
3469.69seconds
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 A10-9700
✔Intel Core i5-7200U
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 A10-9700
✔Intel Core i5-7200U
AES is used to speed up encryption and decryption.
3.Has AVX
✔AMD A10-9700
✔Intel Core i5-7200U
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 A10-9700
✔Intel Core i5-7200U
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 A10-9700)
Unknown. Help us by suggesting a value. (Intel Core i5-7200U)
NEON provides acceleration for media processing, such as listening to MP3s.
7.Has MMX
✔AMD A10-9700
✔Intel Core i5-7200U
MMX is used to speed up tasks such as adjusting the contrast of an image or adjusting volume.
8.Has TrustZone
✖AMD A10-9700
✖Intel Core i5-7200U
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 A10-9700)
Unknown. Help us by suggesting a value. (Intel Core i5-7200U)
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-7200U vs AMD A10-9600P vs AMD A10-9620P
log 04. 22:03:37
#0 checking url part for id 8152 +0s … 0s
#1 checking url part for id 8094 +0s … 0s
#2 checking url part for id 9188 +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 Fri, 30 Sep 2022 13:14:19 +0200 +0s … 0s
#5 linkCache_getLink no uid found +0.048s … 0.049s
#6 linkCache_getLink no uid found +0.008s … 0.057s
#7 linkCache_getLink no uid found +0.
003s … 0.06s
#8 linkCache_getLink using $NBC_LINKCACHE +0s … 0.06s
#9 linkCache_getLink using $NBC_LINKCACHE +0s … 0.06s
#10 linkCache_getLink using $NBC_LINKCACHE +0s … 0.06s
#11 linkCache_getLink using $NBC_LINKCACHE +0s … 0.06s
#12 linkCache_getLink using $NBC_LINKCACHE +0s … 0.06s
#13 linkCache_getLink using $NBC_LINKCACHE +0s … 0.06s
#14 linkCache_getLink using $NBC_LINKCACHE +0s … 0.06s
#15 linkCache_getLink using $NBC_LINKCACHE +0s … 0.06s
#16 composed specs +0s … 0.06s
#17 did output specs +0s … 0.06s
#18 getting avg benchmarks for device 8152 +0.001s … 0.061s
#19 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.064s
#20 linkCache_getLink no uid found +0.11s … 0.174s
#21 got single benchmarks 8152 +0.088s … 0.262s
#22 getting avg benchmarks for device 8094 +0.
001s … 0.264s
#23 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s
#24 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.265s
#25 got single benchmarks 8094 +0.004s … 0.269s
#26 getting avg benchmarks for device 9188 +0s … 0.269s
#27 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s
#28 got single benchmarks 9188 +0s … 0.27s
#29 got avg benchmarks for devices +0s … 0.27s
#30 linkCache_getLink no uid found +0.002s … 0.272s
#31 linkCache_getLink no uid found +0s … 0.272s
#32 linkCache_getLink no uid found +0s … 0.272s
#33 linkCache_getLink no uid found +0s … 0.272s
#34 linkCache_getLink no uid found +0s … 0.272s
#35 linkCache_getLink no uid found +0.001s … 0.273s
#36 linkCache_getLink no uid found +0s … 0.273s
#37 linkCache_getLink no uid found +0s … 0.273s
#38 linkCache_getLink no uid found +0s .
.. 0.273s
#39 linkCache_getLink no uid found +0.001s … 0.274s
#40 linkCache_getLink no uid found +0s … 0.274s
#41 linkCache_getLink no uid found +0s … 0.274s
#42 linkCache_getLink no uid found +0s … 0.274s
#43 linkCache_getLink no uid found +0.001s … 0.275s
#44 linkCache_getLink no uid found +0.001s … 0.276s
#45 linkCache_getLink no uid found +0s … 0.276s
#46 linkCache_getLink no uid found +0.251s … 0.527s
#47 linkCache_getLink no uid found +0.003s … 0.53s
#48 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#49 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#50 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#51 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#52 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#53 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.53s
#54 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#55 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#56 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#57 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#58 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#59 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#60 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#61 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#62 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#63 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#64 linkCache_getLink no uid found +0s … 0.53s
#65 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#66 linkCache_getLink no uid found +0s … 0.53s
#67 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#68 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.53s
#69 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#70 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#71 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#72 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#73 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#74 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#75 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#76 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#77 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#78 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#79 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#80 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#81 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#82 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#83 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.53s
#84 linkCache_getLink no uid found +0s … 0.53s
#85 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#86 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#87 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#88 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#89 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#90 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#91 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#92 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#93 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#94 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#95 linkCache_getLink no uid found +0s … 0.53s
#96 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#97 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#98 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.53s
#99 linkCache_getLink no uid found +0s … 0.53s
#100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#102 linkCache_getLink no uid found +0s … 0.53s
#103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#105 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#107 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#110 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.53s
#113 linkCache_getLink no uid found +0s .
.. 0.531s
#114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#116 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#123 linkCache_getLink no uid found +0s … 0.531s
#124 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#125 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#126 linkCache_getLink no uid found +0s … 0.531s
#127 linkCache_getLink no uid found +0s … 0.531s
#128 linkCache_getLink no uid found +0s .
.. 0.531s
#129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#130 linkCache_getLink no uid found +0s … 0.531s
#131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#133 linkCache_getLink no uid found +0s … 0.531s
#134 linkCache_getLink no uid found +0s … 0.531s
#135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#137 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#138 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#139 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#140 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#141 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#143 linkCache_getLink no uid found +0s .
.. 0.531s
#144 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#147 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#148 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.531s
#149 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#150 linkCache_getLink no uid found +0s … 0.531s
#151 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.531s
#153 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#154 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#155 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#157 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.532s
#158 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#160 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#161 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#162 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#164 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#165 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#166 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#167 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#169 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#171 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.532s
#172 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#174 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#175 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#176 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#179 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#180 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#181 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#182 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#183 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#184 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#185 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.532s
#186 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#187 linkCache_getLink no uid found +0s … 0.532s
#188 linkCache_getLink using $NBC_LINKCACHE +0s … 0.532s
#189 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#191 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#192 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#193 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#194 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#195 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#196 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#197 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#198 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#199 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.533s
#200 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#201 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#202 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#203 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#205 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#206 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#207 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#208 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#209 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#210 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#211 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#212 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#213 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.533s
#214 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#215 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#217 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#218 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#219 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#220 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#221 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#222 linkCache_getLink using $NBC_LINKCACHE +0s … 0.533s
#223 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.534s
#224 linkCache_getLink no uid found +0s … 0.534s
#225 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#226 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#227 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.534s
#228 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#229 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#230 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#231 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#232 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#233 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#234 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#235 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#236 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#237 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#238 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#239 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#240 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#241 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.534s
#242 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#243 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#244 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#245 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#246 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#247 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#248 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#249 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#250 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#251 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#252 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#253 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#254 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#255 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.534s
#256 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#257 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#258 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#259 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#260 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#261 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#262 linkCache_getLink using $NBC_LINKCACHE +0s … 0.534s
#263 linkCache_getLink using $NBC_LINKCACHE +0s … 0.535s
#264 linkCache_getLink using $NBC_LINKCACHE +0s … 0.535s
#265 linkCache_getLink using $NBC_LINKCACHE +0s … 0.535s
#266 linkCache_getLink using $NBC_LINKCACHE +0s … 0.535s
#267 linkCache_getLink using $NBC_LINKCACHE +0s … 0.535s
#268 linkCache_getLink using $NBC_LINKCACHE +0s … 0.535s
#269 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.535s
#270 linkCache_getLink using $NBC_LINKCACHE +0s … 0.535s
#271 linkCache_getLink using $NBC_LINKCACHE +0s … 0.535s
#272 linkCache_getLink using $NBC_LINKCACHE +0s … 0.535s
#273 linkCache_getLink using $NBC_LINKCACHE +0s … 0.535s
#274 linkCache_getLink using $NBC_LINKCACHE +0s … 0.535s
#275 linkCache_getLink no uid found +0s … 0.535s
#276 linkCache_getLink using $NBC_LINKCACHE +0s … 0.535s
#277 linkCache_getLink using $NBC_LINKCACHE +0s … 0.535s
#278 linkCache_getLink using $NBC_LINKCACHE +0s … 0.535s
#279 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#280 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#281 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#282 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#283 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.536s
#284 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#285 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#286 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#287 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#288 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#289 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#290 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#291 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#292 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#293 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#294 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#295 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#296 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#297 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.536s
#298 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#299 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#300 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#301 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#302 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#303 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#304 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#305 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#306 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#307 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#308 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#309 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#310 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#311 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.536s
#312 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#313 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#314 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#315 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#316 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#317 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#318 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#319 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#320 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#321 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#322 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#323 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#324 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#325 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.536s
#326 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#327 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#328 linkCache_getLink no uid found +0s … 0.536s
#329 linkCache_getLink using $NBC_LINKCACHE +0s … 0.536s
#330 linkCache_getLink using $NBC_LINKCACHE +0s … 0.537s
#331 linkCache_getLink using $NBC_LINKCACHE +0s … 0.537s
#332 linkCache_getLink using $NBC_LINKCACHE +0s … 0.537s
#333 linkCache_getLink using $NBC_LINKCACHE +0s … 0.537s
#334 linkCache_getLink using $NBC_LINKCACHE +0s … 0.537s
#335 linkCache_getLink using $NBC_LINKCACHE +0s … 0.537s
#336 linkCache_getLink using $NBC_LINKCACHE +0s … 0.537s
#337 linkCache_getLink using $NBC_LINKCACHE +0s … 0.537s
#338 linkCache_getLink using $NBC_LINKCACHE +0s … 0.537s
#339 linkCache_getLink using $NBC_LINKCACHE +0.001s .
.. 0.538s
#340 linkCache_getLink using $NBC_LINKCACHE +0s … 0.538s
#341 linkCache_getLink using $NBC_LINKCACHE +0s … 0.538s
#342 linkCache_getLink using $NBC_LINKCACHE +0s … 0.538s
#343 linkCache_getLink using $NBC_LINKCACHE +0s … 0.538s
#344 linkCache_getLink using $NBC_LINKCACHE +0s … 0.538s
#345 linkCache_getLink using $NBC_LINKCACHE +0s … 0.538s
#346 linkCache_getLink using $NBC_LINKCACHE +0s … 0.538s
#347 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.538s
#348 linkCache_getLink using $NBC_LINKCACHE +0s … 0.538s
#349 linkCache_getLink using $NBC_LINKCACHE +0s … 0.538s
#350 linkCache_getLink using $NBC_LINKCACHE +0s … 0.538s
#351 linkCache_getLink using $NBC_LINKCACHE +0s … 0.538s
#352 linkCache_getLink using $NBC_LINKCACHE +0s … 0.538s
#353 linkCache_getLink no uid found +0s .
.. 0.538s
#354 linkCache_getLink no uid found +0s … 0.539s
#355 linkCache_getLink using $NBC_LINKCACHE +0s … 0.539s
#356 linkCache_getLink using $NBC_LINKCACHE +0s … 0.539s
#357 linkCache_getLink no uid found +0s … 0.539s
#358 linkCache_getLink using $NBC_LINKCACHE +0s … 0.539s
#359 linkCache_getLink no uid found +0s … 0.539s
#360 linkCache_getLink no uid found +0s … 0.539s
#361 linkCache_getLink no uid found +0s … 0.539s
#362 linkCache_getLink using $NBC_LINKCACHE +0s … 0.539s
#363 linkCache_getLink no uid found +0s … 0.539s
#364 linkCache_getLink no uid found +0s … 0.539s
#365 linkCache_getLink no uid found +0s … 0.539s
#366 linkCache_getLink no uid found +0s … 0.539s
#367 linkCache_getLink no uid found +0s … 0.539s
#368 linkCache_getLink no uid found +0s … 0.539s
#369 linkCache_getLink no uid found +0s .
.. 0.539s
#370 linkCache_getLink no uid found +0s … 0.539s
#371 linkCache_getLink using $NBC_LINKCACHE +0s … 0.539s
#372 linkCache_getLink no uid found +0s … 0.539s
#373 linkCache_getLink using $NBC_LINKCACHE +0s … 0.539s
#374 linkCache_getLink using $NBC_LINKCACHE +0s … 0.539s
#375 linkCache_getLink using $NBC_LINKCACHE +0s … 0.54s
#376 linkCache_getLink using $NBC_LINKCACHE +0s … 0.54s
#377 linkCache_getLink using $NBC_LINKCACHE +0s … 0.54s
#378 linkCache_getLink using $NBC_LINKCACHE +0s … 0.54s
#379 linkCache_getLink using $NBC_LINKCACHE +0s … 0.54s
#380 linkCache_getLink using $NBC_LINKCACHE +0s … 0.54s
#381 linkCache_getLink no uid found +0s … 0.54s
#382 linkCache_getLink using $NBC_LINKCACHE +0s … 0.54s
#383 linkCache_getLink no uid found +0s … 0.54s
#384 linkCache_getLink no uid found +0s .
.. 0.54s
#385 linkCache_getLink no uid found +0s … 0.54s
#386 linkCache_getLink no uid found +0s … 0.54s
#387 linkCache_getLink no uid found +0s … 0.54s
#388 linkCache_getLink no uid found +0s … 0.54s
#389 linkCache_getLink using $NBC_LINKCACHE +0s … 0.54s
#390 linkCache_getLink no uid found +0s … 0.54s
#391 linkCache_getLink no uid found +0s … 0.54s
#392 linkCache_getLink using $NBC_LINKCACHE +0s … 0.54s
#393 linkCache_getLink no uid found +0s … 0.54s
#394 linkCache_getLink no uid found +0s … 0.54s
#395 linkCache_getLink using $NBC_LINKCACHE +0s … 0.54s
#396 linkCache_getLink using $NBC_LINKCACHE +0s … 0.54s
#397 linkCache_getLink no uid found +0s … 0.54s
#398 linkCache_getLink using $NBC_LINKCACHE +0s … 0.54s
#399 linkCache_getLink no uid found +0s … 0.54s
#400 linkCache_getLink no uid found +0s .
.. 0.54s
#401 linkCache_getLink no uid found +0s … 0.54s
#402 linkCache_getLink using $NBC_LINKCACHE +0s … 0.54s
#403 linkCache_getLink using $NBC_LINKCACHE +0s … 0.54s
#404 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.541s
#405 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.542s
#406 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.543s
#407 linkCache_getLink using $NBC_LINKCACHE +0s … 0.543s
#408 linkCache_getLink using $NBC_LINKCACHE +0s … 0.543s
#409 linkCache_getLink using $NBC_LINKCACHE +0s … 0.543s
#410 linkCache_getLink using $NBC_LINKCACHE +0s … 0.543s
#411 linkCache_getLink using $NBC_LINKCACHE +0s … 0.543s
#412 linkCache_getLink using $NBC_LINKCACHE +0s … 0.543s
#413 linkCache_getLink no uid found +0.002s … 0.545s
#414 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.545s
#415 linkCache_getLink using $NBC_LINKCACHE +0s … 0.545s
#416 linkCache_getLink using $NBC_LINKCACHE +0s … 0.545s
#417 linkCache_getLink using $NBC_LINKCACHE +0s … 0.546s
#418 linkCache_getLink using $NBC_LINKCACHE +0s … 0.546s
#419 linkCache_getLink no uid found +0s … 0.546s
#420 linkCache_getLink no uid found +0s … 0.546s
#421 linkCache_getLink no uid found +0s … 0.546s
#422 linkCache_getLink no uid found +0s … 0.546s
#423 linkCache_getLink no uid found +0s … 0.546s
#424 linkCache_getLink no uid found +0s … 0.546s
#425 linkCache_getLink no uid found +0s … 0.546s
#426 linkCache_getLink using $NBC_LINKCACHE +0s … 0.546s
#427 linkCache_getLink using $NBC_LINKCACHE +0s … 0.546s
#428 linkCache_getLink using $NBC_LINKCACHE +0s … 0.546s
#429 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.546s
#430 linkCache_getLink no uid found +0s … 0.546s
#431 linkCache_getLink using $NBC_LINKCACHE +0s … 0.546s
#432 linkCache_getLink no uid found +0s … 0.546s
#433 linkCache_getLink no uid found +0s … 0.546s
#434 linkCache_getLink no uid found +0s … 0.546s
#435 linkCache_getLink no uid found +0s … 0.546s
#436 linkCache_getLink using $NBC_LINKCACHE +0s … 0.546s
#437 linkCache_getLink no uid found +0s … 0.546s
#438 linkCache_getLink using $NBC_LINKCACHE +0s … 0.546s
#439 linkCache_getLink using $NBC_LINKCACHE +0s … 0.546s
#440 linkCache_getLink using $NBC_LINKCACHE +0s … 0.547s
#441 linkCache_getLink using $NBC_LINKCACHE +0s … 0.547s
#442 linkCache_getLink no uid found +0s … 0.547s
#443 linkCache_getLink no uid found +0s … 0.547s
#444 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.547s
#445 linkCache_getLink no uid found +0s … 0.547s
#446 linkCache_getLink no uid found +0s … 0.547s
#447 linkCache_getLink using $NBC_LINKCACHE +0s … 0.547s
#448 linkCache_getLink using $NBC_LINKCACHE +0s … 0.547s
#449 linkCache_getLink using $NBC_LINKCACHE +0s … 0.547s
#450 linkCache_getLink using $NBC_LINKCACHE +0s … 0.547s
#451 linkCache_getLink using $NBC_LINKCACHE +0s … 0.547s
#452 linkCache_getLink no uid found +0s … 0.547s
#453 linkCache_getLink no uid found +0s … 0.547s
#454 linkCache_getLink no uid found +0s … 0.547s
#455 linkCache_getLink no uid found +0s … 0.547s
#456 linkCache_getLink no uid found +0s … 0.547s
#457 linkCache_getLink no uid found +0s … 0.547s
#458 linkCache_getLink no uid found +0s … 0.547s
#459 linkCache_getLink no uid found +0s ..
. 0.547s
#460 linkCache_getLink no uid found +0s … 0.547s
#461 linkCache_getLink using $NBC_LINKCACHE +0s … 0.547s
#462 linkCache_getLink using $NBC_LINKCACHE +0s … 0.548s
#463 linkCache_getLink using $NBC_LINKCACHE +0s … 0.548s
#464 linkCache_getLink using $NBC_LINKCACHE +0s … 0.548s
#465 linkCache_getLink using $NBC_LINKCACHE +0s … 0.548s
#466 linkCache_getLink using $NBC_LINKCACHE +0s … 0.548s
#467 linkCache_getLink using $NBC_LINKCACHE +0s … 0.548s
#468 linkCache_getLink using $NBC_LINKCACHE +0s … 0.548s
#469 linkCache_getLink using $NBC_LINKCACHE +0s … 0.548s
#470 linkCache_getLink using $NBC_LINKCACHE +0s … 0.548s
#471 linkCache_getLink using $NBC_LINKCACHE +0s … 0.548s
#472 linkCache_getLink using $NBC_LINKCACHE +0s … 0.548s
#473 linkCache_getLink using $NBC_LINKCACHE +0s …
0.548s
#474 linkCache_getLink using $NBC_LINKCACHE +0s … 0.548s
#475 linkCache_getLink using $NBC_LINKCACHE +0s … 0.548s
#476 linkCache_getLink no uid found +0s … 0.549s
#477 linkCache_getLink using $NBC_LINKCACHE +0s … 0.549s
#478 linkCache_getLink using $NBC_LINKCACHE +0s … 0.549s
#479 linkCache_getLink using $NBC_LINKCACHE +0s … 0.549s
#480 linkCache_getLink using $NBC_LINKCACHE +0s … 0.549s
#481 linkCache_getLink using $NBC_LINKCACHE +0s … 0.549s
#482 linkCache_getLink using $NBC_LINKCACHE +0s … 0.549s
#483 linkCache_getLink using $NBC_LINKCACHE +0s … 0.549s
#484 linkCache_getLink using $NBC_LINKCACHE +0s … 0.549s
#485 linkCache_getLink using $NBC_LINKCACHE +0s … 0.549s
#486 linkCache_getLink using $NBC_LINKCACHE +0s … 0.549s
#487 linkCache_getLink using $NBC_LINKCACHE +0s … 0.
549s
#488 linkCache_getLink using $NBC_LINKCACHE +0s … 0.549s
#489 linkCache_getLink using $NBC_LINKCACHE +0s … 0.549s
#490 linkCache_getLink using $NBC_LINKCACHE +0s … 0.549s
#491 linkCache_getLink no uid found +0s … 0.549s
#492 linkCache_getLink using $NBC_LINKCACHE +0s … 0.549s
#493 linkCache_getLink using $NBC_LINKCACHE +0s … 0.55s
#494 linkCache_getLink using $NBC_LINKCACHE +0s … 0.55s
#495 linkCache_getLink using $NBC_LINKCACHE +0s … 0.55s
#496 linkCache_getLink using $NBC_LINKCACHE +0s … 0.55s
#497 linkCache_getLink using $NBC_LINKCACHE +0s … 0.55s
#498 linkCache_getLink using $NBC_LINKCACHE +0s … 0.55s
#499 linkCache_getLink using $NBC_LINKCACHE +0s … 0.55s
#500 linkCache_getLink using $NBC_LINKCACHE +0s … 0.55s
#501 linkCache_getLink using $NBC_LINKCACHE +0s … 0.55s
#502 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.55s
#503 linkCache_getLink using $NBC_LINKCACHE +0s … 0.55s
#504 linkCache_getLink using $NBC_LINKCACHE +0s … 0.55s
#505 linkCache_getLink using $NBC_LINKCACHE +0s … 0.55s
#506 linkCache_getLink no uid found +0s … 0.55s
#507 linkCache_getLink using $NBC_LINKCACHE +0s … 0.55s
#508 linkCache_getLink using $NBC_LINKCACHE +0s … 0.551s
#509 linkCache_getLink using $NBC_LINKCACHE +0s … 0.551s
#510 linkCache_getLink using $NBC_LINKCACHE +0s … 0.551s
#511 linkCache_getLink using $NBC_LINKCACHE +0s … 0.551s
#512 linkCache_getLink using $NBC_LINKCACHE +0s … 0.551s
#513 linkCache_getLink using $NBC_LINKCACHE +0s … 0.551s
#514 linkCache_getLink using $NBC_LINKCACHE +0s … 0.551s
#515 linkCache_getLink using $NBC_LINKCACHE +0s … 0.551s
#516 linkCache_getLink using $NBC_LINKCACHE +0s … 0.551s
#517 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.551s
#518 linkCache_getLink using $NBC_LINKCACHE +0s … 0.551s
#519 linkCache_getLink using $NBC_LINKCACHE +0s … 0.551s
#520 linkCache_getLink using $NBC_LINKCACHE +0s … 0.551s
#521 linkCache_getLink using $NBC_LINKCACHE +0s … 0.551s
#522 linkCache_getLink no uid found +0.001s … 0.552s
#523 linkCache_getLink no uid found +0s … 0.552s
#524 linkCache_getLink using $NBC_LINKCACHE +0s … 0.552s
#525 linkCache_getLink using $NBC_LINKCACHE +0s … 0.552s
#526 linkCache_getLink using $NBC_LINKCACHE +0s … 0.552s
#527 linkCache_getLink no uid found +0s … 0.552s
#528 linkCache_getLink no uid found +0s … 0.552s
#529 linkCache_getLink no uid found +0s … 0.552s
#530 linkCache_getLink no uid found +0s … 0.552s
#531 linkCache_getLink using $NBC_LINKCACHE +0s … 0.552s
#532 linkCache_getLink no uid found +0s .
.. 0.552s
#533 linkCache_getLink no uid found +0s … 0.552s
#534 linkCache_getLink no uid found +0s … 0.552s
#535 linkCache_getLink no uid found +0s … 0.552s
#536 linkCache_getLink using $NBC_LINKCACHE +0s … 0.552s
#537 linkCache_getLink using $NBC_LINKCACHE +0s … 0.552s
#538 linkCache_getLink no uid found +0s … 0.552s
#539 linkCache_getLink using $NBC_LINKCACHE +0s … 0.552s
#540 linkCache_getLink using $NBC_LINKCACHE +0s … 0.552s
#541 linkCache_getLink using $NBC_LINKCACHE +0s … 0.552s
#542 linkCache_getLink no uid found +0s … 0.552s
#543 linkCache_getLink no uid found +0s … 0.552s
#544 linkCache_getLink no uid found +0s … 0.552s
#545 linkCache_getLink using $NBC_LINKCACHE +0s … 0.552s
#546 linkCache_getLink using $NBC_LINKCACHE +0s … 0.552s
#547 linkCache_getLink no uid found +0s .
.. 0.552s
#548 linkCache_getLink using $NBC_LINKCACHE +0s … 0.552s
#549 linkCache_getLink no uid found +0s … 0.552s
#550 linkCache_getLink no uid found +0.001s … 0.553s
#551 linkCache_getLink using $NBC_LINKCACHE +0s … 0.553s
#552 linkCache_getLink using $NBC_LINKCACHE +0s … 0.553s
#553 linkCache_getLink no uid found +0s … 0.553s
#554 linkCache_getLink using $NBC_LINKCACHE +0s … 0.553s
#555 linkCache_getLink no uid found +0s … 0.553s
#556 linkCache_getLink no uid found +0s … 0.553s
#557 linkCache_getLink no uid found +0s … 0.553s
#558 linkCache_getLink no uid found +0s … 0.553s
#559 linkCache_getLink no uid found +0s … 0.553s
#560 linkCache_getLink no uid found +0s … 0.553s
#561 linkCache_getLink using $NBC_LINKCACHE +0s … 0.553s
#562 linkCache_getLink no uid found +0s .
.. 0.553s
#563 linkCache_getLink no uid found +0s … 0.553s
#564 linkCache_getLink using $NBC_LINKCACHE +0s … 0.553s
#565 linkCache_getLink no uid found +0s … 0.553s
#566 linkCache_getLink using $NBC_LINKCACHE +0s … 0.553s
#567 linkCache_getLink no uid found +0s … 0.553s
#568 linkCache_getLink no uid found +0s … 0.553s
#569 linkCache_getLink using $NBC_LINKCACHE +0s … 0.553s
#570 linkCache_getLink using $NBC_LINKCACHE +0s … 0.553s
#571 linkCache_getLink using $NBC_LINKCACHE +0s … 0.553s
#572 linkCache_getLink using $NBC_LINKCACHE +0s … 0.553s
#573 linkCache_getLink using $NBC_LINKCACHE +0s … 0.553s
#574 linkCache_getLink using $NBC_LINKCACHE +0s … 0.553s
#575 linkCache_getLink no uid found +0s … 0.553s
#576 linkCache_getLink no uid found +0s … 0.553s
#577 linkCache_getLink no uid found +0.
001s … 0.554s
#578 linkCache_getLink using $NBC_LINKCACHE +0s … 0.554s
#579 linkCache_getLink using $NBC_LINKCACHE +0s … 0.554s
#580 linkCache_getLink no uid found +0s … 0.555s
#581 linkCache_getLink using $NBC_LINKCACHE +0s … 0.555s
#582 linkCache_getLink no uid found +0s … 0.555s
#583 linkCache_getLink no uid found +0s … 0.555s
#584 linkCache_getLink no uid found +0s … 0.555s
#585 linkCache_getLink no uid found +0s … 0.555s
#586 linkCache_getLink using $NBC_LINKCACHE +0s … 0.555s
#587 linkCache_getLink no uid found +0s … 0.555s
#588 linkCache_getLink no uid found +0s … 0.555s
#589 linkCache_getLink using $NBC_LINKCACHE +0s … 0.555s
#590 linkCache_getLink using $NBC_LINKCACHE +0s … 0.555s
#591 linkCache_getLink using $NBC_LINKCACHE +0s … 0.555s
#592 linkCache_getLink no uid found +0s .
.. 0.555s
#593 linkCache_getLink no uid found +0s … 0.555s
#594 linkCache_getLink no uid found +0s … 0.555s
#595 linkCache_getLink no uid found +0s … 0.555s
#596 linkCache_getLink no uid found +0s … 0.555s
#597 linkCache_getLink no uid found +0s … 0.555s
#598 linkCache_getLink using $NBC_LINKCACHE +0s … 0.555s
#599 linkCache_getLink using $NBC_LINKCACHE +0s … 0.555s
#600 linkCache_getLink using $NBC_LINKCACHE +0s … 0.555s
#601 linkCache_getLink no uid found +0s … 0.555s
#602 linkCache_getLink using $NBC_LINKCACHE +0s … 0.555s
#603 linkCache_getLink using $NBC_LINKCACHE +0s … 0.555s
#604 linkCache_getLink no uid found +0.001s … 0.555s
#605 linkCache_getLink using $NBC_LINKCACHE +0s … 0.555s
#606 linkCache_getLink using $NBC_LINKCACHE +0s … 0.555s
#607 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.556s
#608 linkCache_getLink using $NBC_LINKCACHE +0s … 0.556s
#609 linkCache_getLink using $NBC_LINKCACHE +0s … 0.556s
#610 linkCache_getLink using $NBC_LINKCACHE +0s … 0.556s
#611 linkCache_getLink using $NBC_LINKCACHE +0s … 0.556s
#612 linkCache_getLink using $NBC_LINKCACHE +0s … 0.556s
#613 linkCache_getLink using $NBC_LINKCACHE +0s … 0.556s
#614 linkCache_getLink using $NBC_LINKCACHE +0s … 0.556s
#615 linkCache_getLink no uid found +0s … 0.556s
#616 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.557s
#617 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#618 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#619 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#620 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#621 linkCache_getLink no uid found +0s .
.. 0.557s
#622 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#623 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#624 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#625 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#626 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#627 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#628 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#629 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#630 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#631 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#632 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#633 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#634 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#635 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.557s
#636 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#637 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#638 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#639 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#640 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#641 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#642 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#643 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#644 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#645 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#646 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#647 linkCache_getLink no uid found +0s … 0.557s
#648 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#649 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.557s
#650 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#651 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#652 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#653 linkCache_getLink no uid found +0s … 0.557s
#654 linkCache_getLink no uid found +0s … 0.557s
#655 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#656 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#657 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#658 linkCache_getLink no uid found +0s … 0.557s
#659 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#660 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#661 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#662 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#663 linkCache_getLink no uid found +0s … 0.557s
#664 linkCache_getLink no uid found +0s .
.. 0.557s
#665 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#666 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#667 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#668 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#669 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#670 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#671 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#672 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#673 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#674 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#675 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#676 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#677 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#678 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.557s
#679 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#680 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#681 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#682 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#683 linkCache_getLink using $NBC_LINKCACHE +0s … 0.557s
#684 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#685 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#686 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#687 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#688 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#689 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#690 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#691 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#692 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.558s
#693 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#694 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#695 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#696 linkCache_getLink no uid found +0s … 0.558s
#697 linkCache_getLink no uid found +0s … 0.558s
#698 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#699 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#700 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#701 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#702 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#703 linkCache_getLink no uid found +0s … 0.558s
#704 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#705 linkCache_getLink no uid found +0s … 0.558s
#706 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#707 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.558s
#708 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#709 linkCache_getLink no uid found +0s … 0.558s
#710 linkCache_getLink no uid found +0s … 0.558s
#711 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#712 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#713 linkCache_getLink no uid found +0s … 0.558s
#714 linkCache_getLink no uid found +0s … 0.558s
#715 linkCache_getLink no uid found +0s … 0.558s
#716 linkCache_getLink no uid found +0s … 0.558s
#717 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#718 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#719 linkCache_getLink no uid found +0s … 0.558s
#720 linkCache_getLink using $NBC_LINKCACHE +0s … 0.558s
#721 linkCache_getLink no uid found +0s … 0.558s
#722 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.558s
#723 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.559s
#724 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#725 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#726 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#727 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#728 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#729 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#730 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#731 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#732 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#733 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#734 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#735 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#736 linkCache_getLink no uid found +0s .
.. 0.559s
#737 linkCache_getLink no uid found +0s … 0.559s
#738 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#739 linkCache_getLink no uid found +0s … 0.559s
#740 linkCache_getLink no uid found +0s … 0.559s
#741 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#742 linkCache_getLink no uid found +0s … 0.559s
#743 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#744 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#745 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#746 linkCache_getLink no uid found +0s … 0.559s
#747 linkCache_getLink no uid found +0s … 0.559s
#748 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#749 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#750 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#751 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.559s
#752 linkCache_getLink no uid found +0s … 0.559s
#753 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#754 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#755 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#756 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#757 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#758 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#759 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#760 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#761 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#762 linkCache_getLink no uid found +0s … 0.559s
#763 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#764 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#765 linkCache_getLink no uid found +0s … 0.559s
#766 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.559s
#767 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#768 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#769 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#770 linkCache_getLink no uid found +0s … 0.559s
#771 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#772 linkCache_getLink no uid found +0s … 0.559s
#773 linkCache_getLink no uid found +0s … 0.559s
#774 linkCache_getLink no uid found +0s … 0.559s
#775 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#776 linkCache_getLink no uid found +0s … 0.559s
#777 linkCache_getLink using $NBC_LINKCACHE +0s … 0.559s
#778 linkCache_getLink using $NBC_LINKCACHE +0s … 0.56s
#779 linkCache_getLink using $NBC_LINKCACHE +0s … 0.56s
#780 linkCache_getLink no uid found +0s … 0.56s
#781 linkCache_getLink no uid found +0s .
.. 0.56s
#782 linkCache_getLink using $NBC_LINKCACHE +0s … 0.56s
#783 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.56s
#784 linkCache_getLink no uid found +0s … 0.56s
#785 linkCache_getLink using $NBC_LINKCACHE +0s … 0.56s
#786 linkCache_getLink using $NBC_LINKCACHE +0s … 0.56s
#787 linkCache_getLink using $NBC_LINKCACHE +0s … 0.56s
#788 linkCache_getLink using $NBC_LINKCACHE +0s … 0.56s
#789 linkCache_getLink using $NBC_LINKCACHE +0s … 0.56s
#790 linkCache_getLink using $NBC_LINKCACHE +0s … 0.56s
#791 linkCache_getLink using $NBC_LINKCACHE +0s … 0.56s
#792 linkCache_getLink no uid found +0s … 0.56s
#793 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#794 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#795 linkCache_getLink no uid found +0s … 0.561s
#796 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.561s
#797 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#798 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#799 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#800 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#801 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#802 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#803 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#804 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#805 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#806 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#807 linkCache_getLink no uid found +0s … 0.561s
#808 linkCache_getLink no uid found +0s … 0.561s
#809 linkCache_getLink no uid found +0s … 0.561s
#810 linkCache_getLink no uid found +0s … 0.561s
#811 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.561s
#812 linkCache_getLink no uid found +0s … 0.561s
#813 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#814 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#815 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#816 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#817 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#818 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#819 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#820 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#821 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#822 linkCache_getLink no uid found +0s … 0.561s
#823 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#824 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#825 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#826 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.561s
#827 linkCache_getLink no uid found +0s … 0.561s
#828 linkCache_getLink no uid found +0s … 0.561s
#829 linkCache_getLink no uid found +0s … 0.561s
#830 linkCache_getLink no uid found +0s … 0.561s
#831 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#832 linkCache_getLink no uid found +0s … 0.561s
#833 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#834 linkCache_getLink no uid found +0s … 0.561s
#835 linkCache_getLink using $NBC_LINKCACHE +0s … 0.561s
#836 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.562s
#837 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#838 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#839 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#840 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#841 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.562s
#842 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#843 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#844 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#845 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#846 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#847 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#848 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#849 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#850 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#851 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#852 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#853 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#854 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#855 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.562s
#856 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#857 linkCache_getLink no uid found +0s … 0.562s
#858 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#859 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#860 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#861 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#862 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#863 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#864 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#865 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#866 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#867 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#868 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#869 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.562s
#870 linkCache_getLink using $NBC_LINKCACHE +0s … 0.562s
#871 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#872 linkCache_getLink no uid found +0s … 0.563s
#873 linkCache_getLink no uid found +0s … 0.563s
#874 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#875 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.563s
#876 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#877 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#878 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#879 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#880 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#881 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#882 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#883 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#884 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.563s
#885 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#886 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#887 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#888 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#889 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#890 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#891 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#892 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#893 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#894 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#895 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#896 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#897 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#898 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.563s
#899 linkCache_getLink no uid found +0s … 0.563s
#900 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#901 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#902 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#903 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#904 linkCache_getLink no uid found +0s … 0.563s
#905 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#906 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#907 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#908 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#909 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#910 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#911 linkCache_getLink using $NBC_LINKCACHE +0s … 0.563s
#912 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#913 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.564s
#914 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#915 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#916 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#917 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#918 linkCache_getLink no uid found +0s … 0.564s
#919 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#920 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#921 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#922 linkCache_getLink no uid found +0s … 0.564s
#923 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#924 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#925 linkCache_getLink no uid found +0s … 0.564s
#926 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#927 linkCache_getLink no uid found +0s … 0.564s
#928 linkCache_getLink no uid found +0s .
.. 0.564s
#929 linkCache_getLink no uid found +0s … 0.564s
#930 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#931 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#932 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#933 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#934 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#935 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#936 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#937 linkCache_getLink no uid found +0s … 0.564s
#938 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#939 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#940 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#941 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#942 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#943 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.564s
#944 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#945 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#946 linkCache_getLink no uid found +0s … 0.564s
#947 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#948 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#949 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#950 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#951 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#952 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#953 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#954 linkCache_getLink no uid found +0s … 0.564s
#955 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#956 linkCache_getLink no uid found +0s … 0.564s
#957 linkCache_getLink no uid found +0s … 0.564s
#958 linkCache_getLink no uid found +0s .
.. 0.564s
#959 linkCache_getLink no uid found +0s … 0.564s
#960 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#961 linkCache_getLink no uid found +0s … 0.564s
#962 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#963 linkCache_getLink no uid found +0s … 0.564s
#964 linkCache_getLink using $NBC_LINKCACHE +0s … 0.564s
#965 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.565s
#966 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#967 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#968 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#969 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#970 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#971 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#972 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#973 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.565s
#974 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#975 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#976 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#977 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#978 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#979 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#980 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#981 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#982 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#983 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#984 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#985 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#986 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#987 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.565s
#988 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#989 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#990 linkCache_getLink no uid found +0s … 0.565s
#991 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#992 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#993 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#994 linkCache_getLink no uid found +0s … 0.565s
#995 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#996 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#997 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#998 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#999 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1000 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1001 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1002 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.565s
#1003 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1004 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1005 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1006 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1007 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1008 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1009 linkCache_getLink no uid found +0s … 0.565s
#1010 linkCache_getLink no uid found +0s … 0.565s
#1011 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1012 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1013 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1014 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1015 linkCache_getLink no uid found +0s … 0.565s
#1016 linkCache_getLink using $NBC_LINKCACHE +0s … 0.
565s
#1017 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1018 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1019 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1020 linkCache_getLink no uid found +0s … 0.565s
#1021 linkCache_getLink no uid found +0s … 0.565s
#1022 linkCache_getLink using $NBC_LINKCACHE +0s … 0.565s
#1023 linkCache_getLink using $NBC_LINKCACHE +0s … 0.566s
#1024 linkCache_getLink using $NBC_LINKCACHE +0s … 0.566s
#1025 linkCache_getLink using $NBC_LINKCACHE +0s … 0.566s
#1026 linkCache_getLink using $NBC_LINKCACHE +0s … 0.566s
#1027 linkCache_getLink using $NBC_LINKCACHE +0s … 0.566s
#1028 linkCache_getLink using $NBC_LINKCACHE +0s … 0.566s
#1029 linkCache_getLink no uid found +0s … 0.566s
#1030 linkCache_getLink using $NBC_LINKCACHE +0s … 0.566s
#1031 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.566s
#1032 linkCache_getLink using $NBC_LINKCACHE +0s … 0.566s
#1033 linkCache_getLink using $NBC_LINKCACHE +0s … 0.566s
#1034 linkCache_getLink no uid found +0s … 0.566s
#1035 linkCache_getLink no uid found +0s … 0.566s
#1036 linkCache_getLink no uid found +0s … 0.566s
#1037 linkCache_getLink using $NBC_LINKCACHE +0s … 0.566s
#1038 linkCache_getLink using $NBC_LINKCACHE +0s … 0.566s
#1039 linkCache_getLink using $NBC_LINKCACHE +0s … 0.566s
#1040 linkCache_getLink no uid found +0s … 0.566s
#1041 linkCache_getLink no uid found +0s … 0.566s
#1042 linkCache_getLink no uid found +0s … 0.566s
#1043 linkCache_getLink using $NBC_LINKCACHE +0s … 0.566s
#1044 linkCache_getLink using $NBC_LINKCACHE +0s … 0.566s
#1045 linkCache_getLink no uid found +0s … 0.566s
#1046 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.566s
#1047 linkCache_getLink using $NBC_LINKCACHE +0s … 0.566s
#1048 linkCache_getLink no uid found +0s … 0.566s
#1049 linkCache_getLink no uid found +0s … 0.566s
#1050 linkCache_getLink using $NBC_LINKCACHE +0s … 0.566s
#1051 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.567s
#1052 linkCache_getLink using $NBC_LINKCACHE +0s … 0.567s
#1053 linkCache_getLink using $NBC_LINKCACHE +0s … 0.567s
#1054 linkCache_getLink using $NBC_LINKCACHE +0s … 0.567s
#1055 linkCache_getLink using $NBC_LINKCACHE +0s … 0.567s
#1056 linkCache_getLink using $NBC_LINKCACHE +0s … 0.567s
#1057 linkCache_getLink using $NBC_LINKCACHE +0s … 0.567s
#1058 linkCache_getLink using $NBC_LINKCACHE +0s … 0.567s
#1059 linkCache_getLink using $NBC_LINKCACHE +0s … 0.567s
#1060 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.567s
#1061 linkCache_getLink using $NBC_LINKCACHE +0s … 0.567s
#1062 linkCache_getLink using $NBC_LINKCACHE +0s … 0.567s
#1063 linkCache_getLink using $NBC_LINKCACHE +0s … 0.567s
#1064 linkCache_getLink using $NBC_LINKCACHE +0s … 0.568s
#1065 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.569s
#1066 linkCache_getLink using $NBC_LINKCACHE +0s … 0.569s
#1067 linkCache_getLink using $NBC_LINKCACHE +0s … 0.569s
#1068 linkCache_getLink using $NBC_LINKCACHE +0s … 0.569s
#1069 linkCache_getLink using $NBC_LINKCACHE +0s … 0.569s
#1070 linkCache_getLink using $NBC_LINKCACHE +0s … 0.569s
#1071 linkCache_getLink using $NBC_LINKCACHE +0s … 0.569s
#1072 linkCache_getLink using $NBC_LINKCACHE +0s … 0.569s
#1073 linkCache_getLink using $NBC_LINKCACHE +0s … 0.569s
#1074 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.569s
#1075 linkCache_getLink using $NBC_LINKCACHE +0s … 0.569s
#1076 linkCache_getLink using $NBC_LINKCACHE +0s … 0.569s
#1077 linkCache_getLink using $NBC_LINKCACHE +0s … 0.569s
#1078 linkCache_getLink using $NBC_LINKCACHE +0s … 0.569s
#1079 linkCache_getLink using $NBC_LINKCACHE +0s … 0.569s
#1080 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.57s
#1081 linkCache_getLink using $NBC_LINKCACHE +0s … 0.57s
#1082 linkCache_getLink using $NBC_LINKCACHE +0s … 0.57s
#1083 linkCache_getLink using $NBC_LINKCACHE +0s … 0.57s
#1084 linkCache_getLink using $NBC_LINKCACHE +0s … 0.57s
#1085 linkCache_getLink using $NBC_LINKCACHE +0s … 0.57s
#1086 linkCache_getLink using $NBC_LINKCACHE +0s … 0.57s
#1087 linkCache_getLink using $NBC_LINKCACHE +0s … 0.57s
#1088 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.57s
#1089 linkCache_getLink using $NBC_LINKCACHE +0s … 0.57s
#1090 linkCache_getLink using $NBC_LINKCACHE +0s … 0.57s
#1091 linkCache_getLink using $NBC_LINKCACHE +0s … 0.57s
#1092 linkCache_getLink using $NBC_LINKCACHE +0s … 0.57s
#1093 linkCache_getLink using $NBC_LINKCACHE +0s … 0.57s
#1094 linkCache_getLink using $NBC_LINKCACHE +0s … 0.57s
#1095 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.571s
#1096 linkCache_getLink using $NBC_LINKCACHE +0s … 0.571s
#1097 linkCache_getLink using $NBC_LINKCACHE +0s … 0.571s
#1098 linkCache_getLink using $NBC_LINKCACHE +0s … 0.571s
#1099 linkCache_getLink using $NBC_LINKCACHE +0s … 0.571s
#1100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.571s
#1101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.571s
#1102 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.571s
#1103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.571s
#1104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.571s
#1105 linkCache_getLink using $NBC_LINKCACHE +0s … 0.571s
#1106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.571s
#1107 linkCache_getLink using $NBC_LINKCACHE +0s … 0.571s
#1108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.571s
#1109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.571s
#1110 linkCache_getLink using $NBC_LINKCACHE +0s … 0.571s
#1111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.571s
#1112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.571s
#1113 linkCache_getLink using $NBC_LINKCACHE +0s … 0.572s
#1114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.572s
#1115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.572s
#1116 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.572s
#1117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.572s
#1118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.572s
#1119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.572s
#1120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.572s
#1121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.572s
#1122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.572s
#1123 linkCache_getLink using $NBC_LINKCACHE +0s … 0.572s
#1124 linkCache_getLink using $NBC_LINKCACHE +0s … 0.572s
#1125 linkCache_getLink using $NBC_LINKCACHE +0s … 0.572s
#1126 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.573s
#1127 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1128 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1130 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.573s
#1131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1133 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1137 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1138 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1139 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1140 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1141 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1143 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1144 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.573s
#1145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1147 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1148 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1149 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1150 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1151 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1153 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1154 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1155 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.573s
#1157 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.574s
#1158 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.574s
#1159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1160 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1161 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1162 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1164 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1165 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1166 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1167 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1169 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1171 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1172 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.574s
#1173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1174 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1175 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1176 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1179 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1180 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1181 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1182 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1183 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1184 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1185 linkCache_getLink using $NBC_LINKCACHE +0s … 0.574s
#1186 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.574s
#1187 linkCache_getLink using $NBC_LINKCACHE +0s … 0.575s
#1188 linkCache_getLink no uid found +0s … 0.575s
#1189 linkCache_getLink using $NBC_LINKCACHE +0s … 0.575s
#1190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.575s
#1191 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.576s
#1192 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1193 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1194 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1195 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1196 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1197 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1198 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1199 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1200 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.576s
#1201 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1202 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1203 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1205 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1206 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1207 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1208 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1209 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1210 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1211 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1212 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1213 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1214 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.576s
#1215 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1217 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1218 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1219 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1220 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1221 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1222 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1223 linkCache_getLink no uid found +0s … 0.576s
#1224 linkCache_getLink using $NBC_LINKCACHE +0s … 0.576s
#1225 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.577s
#1226 linkCache_getLink using $NBC_LINKCACHE +0s … 0.577s
#1227 linkCache_getLink no uid found +0s … 0.578s
#1228 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.578s
#1229 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.579s
#1230 linkCache_getLink using $NBC_LINKCACHE +0s … 0.579s
#1231 linkCache_getLink no uid found +0s … 0.579s
#1232 linkCache_getLink using $NBC_LINKCACHE +0s … 0.579s
#1233 linkCache_getLink no uid found +0.001s … 0.58s
#1234 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.581s
#1235 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1236 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1237 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1238 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1239 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1240 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1241 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1242 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.581s
#1243 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1244 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1245 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1246 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1247 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1248 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1249 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1250 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1251 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1252 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1253 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1254 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1255 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1256 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.581s
#1257 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1258 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1259 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1260 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1261 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1262 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1263 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1264 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1265 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1266 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1267 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1268 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1269 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1270 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.581s
#1271 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1272 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1273 linkCache_getLink no uid found +0s … 0.581s
#1274 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1275 linkCache_getLink using $NBC_LINKCACHE +0s … 0.581s
#1276 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.582s
#1277 linkCache_getLink no uid found +0s … 0.582s
#1278 linkCache_getLink using $NBC_LINKCACHE +0s … 0.582s
#1279 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.582s
#1280 linkCache_getLink using $NBC_LINKCACHE +0s … 0.582s
#1281 linkCache_getLink using $NBC_LINKCACHE +0s … 0.582s
#1282 linkCache_getLink using $NBC_LINKCACHE +0s … 0.582s
#1283 linkCache_getLink using $NBC_LINKCACHE +0s … 0.582s
#1284 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.582s
#1285 linkCache_getLink using $NBC_LINKCACHE +0s … 0.582s
#1286 linkCache_getLink using $NBC_LINKCACHE +0s … 0.582s
#1287 linkCache_getLink using $NBC_LINKCACHE +0s … 0.582s
#1288 linkCache_getLink using $NBC_LINKCACHE +0s … 0.582s
#1289 linkCache_getLink using $NBC_LINKCACHE +0s … 0.582s
#1290 linkCache_getLink using $NBC_LINKCACHE +0s … 0.582s
#1291 linkCache_getLink using $NBC_LINKCACHE +0s … 0.582s
#1292 linkCache_getLink using $NBC_LINKCACHE +0s … 0.582s
#1293 linkCache_getLink using $NBC_LINKCACHE +0s … 0.582s
#1294 linkCache_getLink using $NBC_LINKCACHE +0s … 0.583s
#1295 linkCache_getLink using $NBC_LINKCACHE +0s … 0.583s
#1296 linkCache_getLink using $NBC_LINKCACHE +0s … 0.583s
#1297 linkCache_getLink using $NBC_LINKCACHE +0s … 0.583s
#1298 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.583s
#1299 linkCache_getLink using $NBC_LINKCACHE +0s … 0.583s
#1300 linkCache_getLink no uid found +0.002s … 0.584s
#1301 linkCache_getLink using $NBC_LINKCACHE +0s … 0.584s
#1302 linkCache_getLink using $NBC_LINKCACHE +0s … 0.584s
#1303 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.585s
#1304 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1305 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1306 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1307 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1308 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1309 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1310 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1311 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1312 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.585s
#1313 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1314 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1315 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1316 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1317 linkCache_getLink no uid found +0s … 0.585s
#1318 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1319 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1320 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1321 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1322 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1323 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1324 linkCache_getLink using $NBC_LINKCACHE +0s … 0.585s
#1325 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1326 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.586s
#1327 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1328 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1329 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1330 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1331 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1332 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1333 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1334 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1335 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1336 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1337 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1338 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1339 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1340 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.586s
#1341 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1342 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1343 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1344 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1345 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1346 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1347 linkCache_getLink using $NBC_LINKCACHE +0s … 0.586s
#1348 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.588s
#1349 linkCache_getLink no uid found +0s … 0.588s
#1350 linkCache_getLink using $NBC_LINKCACHE +0s … 0.588s
#1351 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.589s
#1352 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.59s
#1353 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.591s
#1354 min, max, avg, median took s +0.
001s … 0.592s
#1355 return log +0s … 0.592s
Lenovo Ideapad 310 APU Quad Core A10 A10-9600P 7th Gen — (8 GB/1 TB HDD/Windows 10 Home/2 GB Graphics) 310 Laptop Rs.40490 Price in India — Buy Lenovo Ideapad 310 APU Quad Core A10 A10-9600P 7th Gen — (8 GB/1 TB HDD/Windows 10 Home/2 GB Graphics) 310 Laptop Black Online
Computers
Laptops
Lenovo Laptops
Lenovo Ideapad 310 APU Quad Core A10 A10-9600P 7th Gen — (8 GB/1 TB HDD/Windows 10 Home/2 GB Graphics) 310 Laptop (15.6 inch, Black, 2.2 kg)
Compare
3.9
578 Ratings & 131 Reviews
₹40,390
₹40,490
Hurry, Only 1 left!
Coupons for you
T&C
Available offers
On orders of ₹5,000 and above
T&C
T&C
T&C
Know More
Buy without Exchange
₹40,390
Buy with Exchange
up to ₹18,100 off
Enter pincode to check if exchange is available
1 Year Onsite WarrantyKnow More
Delivery
Check
Enter pincode
View Details
Highlights
- Pre-installed Genuine Windows 10 OS
- 15.6 inch HD LED Backlit Display
Easy Payment Options
- No cost EMI starting from ₹6,732/month
- Cash on Delivery
- Net banking & Credit/ Debit/ ATM card
View Details
Seller
CORSECA
4.
7
Product Description
If Friday nights are reserved for movies and Saturday nights for some soulful music, then the Lenovo Ideapad 310 is the laptop for you. This laptop is a fusion of quick processing and innovative design and enhances your multimedia experience.
Quick Processing
Powered by the APU quad-core A10 7th Gen processor and 8 GB DDR4 RAM, the Lenovo Ideapad 310 takes your entertainment experience to the next level. Play 3D games, binge watch movies, download songs, and do much more with this laptop.
Touchscreen
A movie marathon with your loved one or a game night with your friends — no matter what you’re planning, with the Ideapad 310, you can stay assured about non-stop entertainment, thanks to its intuitive 39.62 cm touchscreen and HD graphics.
Dynamic Audio
Enjoy your favourite music loud and clear with the Lenovo Ideapad 310, thanks to Dolby technology and stereo speakers.
Lightning-Fast Web Browsing
Browse the internet, stream videos online, download apps and do much more with a lightning-fast speed, thanks to its 802.
11 a/c WiFi connectivity.
Optical Drive
You don’t have to buy an external optical drive as this laptop comes with an integrated DVD/CD-RW drive so you can load programs, listen to CDs, and watch movies offline.
Storage
Store movies, music, pictures and all your important documents on this laptop without worrying about running out of storage space as it comes with up to 1 TB HDD storage.
Specifications
General
| Sales Package |
|
| Model Number |
|
| Part Number |
|
| Series |
|
| Color |
|
| Type |
|
| Suitable For |
|
| Battery Backup |
|
Processor And Memory Features
| Dedicated Graphic Memory Type |
|
| Dedicated Graphic Memory Capacity |
|
| Processor Brand |
|
| Processor Name |
|
| Processor Generation |
|
| SSD |
|
| RAM |
|
| RAM Type |
|
| HDD Capacity |
|
| Processor Variant |
|
| Clock Speed |
|
| Cache |
|
| RPM |
|
| Graphic Processor |
|
2 GHzOperating System
| OS Architecture |
|
| Operating System |
|
| Supported Operating System |
|
| System Architecture |
|
Port And Slot Features
| Mic In |
|
| USB Port |
|
| Multi Card Slot |
|
| Hardware Interface |
|
Display And Audio Features
| Touchscreen |
|
| Screen Size |
|
| Screen Resolution |
|
| Screen Type |
|
| Speakers |
|
| Internal Mic |
|
| Sound Properties |
|
62 cm (15.6 inch)Connectivity Features
| Wireless LAN |
|
| Bluetooth |
|
Dimensions
| Dimensions |
|
| Weight |
|
Additional Features
| Disk Drive |
|
| Web Camera |
|
| Read/Write Speed |
|
| Keyboard |
|
| Pointer Device |
|
| Additional Features |
|
Warranty
| Warranty Summary |
|
| Warranty Service Type |
|
| Covered in Warranty |
|
| Not Covered in Warranty |
|
| Domestic Warranty |
|
Accesories is also not covered under warranty:- adapter, battery. Software Damage is Also not coveredFrequently Bought Together
Lenovo Ideapad 310 APU Quad Core A10 A10-9600P 7th Gen — (8 GB/1 …
3.9
(578)
₹40,390
₹40,490
Currently unavailable
Ant Esports GM320 Wired Optical Gaming Mouse
4.5
(36)
HP 150 Wired Mouse and Keyboard Wired USB Multi-device Keyboard
4.4
(1,475)
1 Item
₹40,390
2 Add-ons
₹1,278
Total
₹41,668
Ratings & Reviews
578 Ratings &
131 Reviews
-
5★
-
4★
-
3★
-
2★
-
1★
-
267
-
152
-
81
-
17
-
61
Performance
Battery
Design
Display
4
Detailed Information
This model’s details are hard to find on the internet.
Here are the details-
AMD A10 7th Gen Processor
Radeon R5 512Mb DDR4 integrated graphics
Radeon R6 2GB DDR3 M435DX dedicated graphics card
PROS-
Great specs for the price point
Looks decent in this budget range
Average to good battery life(nearly 4..5Hrs)
CONS-
Average screen
Pathetic positioning of speakers hence low volume
Cover is fingerprint prone
Verdict-
If you have a budget of 40k and looking for a all rounder laptop(daliy work+l…
READ MORE
Rohan Thakur
Mar, 2017
Permalink
Report Abuse
5
Just wow!
amazing product.3 weeks now.
At first you will feel the laptop is slow but when u use it many times , u will feel the speed and performance of amd a10 and 8 gb ram.
i have tried only just cause 2 so far.it works smoothly.
the only defect i see is that our fingerprint gets stick to the laptop and its so hard to clean.
.
.
AFTER 8 MONTHS….
This laptop is super amazing. According to the specs the laptop shouldn’t run games after 2013. But this laptop run them. I have played FC4 (some optimiza…
READ MORE
Aravind Narayanan
Certified Buyer, Thiruvananthapuram
Jul, 2017
Permalink
Report Abuse
5
Highly recommended
Nice laptop. Worth the price. Super fast
READ MORE
Jinendra Jain
Certified Buyer, Mumbai
May, 2017
Permalink
Report Abuse
4
Nice Laptop
The Laptop is good for gaming. 2 GB of dedicated graphic card with 512 MB integrated on board graphic card. Altogether you get 2.5 GB of graphic memory. It can also utilize up to 6 GB of RAM as graphic memory.
READ MORE
Imran Khan
Certified Buyer, Chakan
Aug, 2017
Permalink
Report Abuse
5
Very Good
Excellent product at a really competitive price.
The notebook arrived 5 days after ordering. Disappointed in flipkart for poor logistics. The shipment was in my city for 3 days. The price that flipkart offers it at is unbeatable.
The notebook itself is satisfactory for the price. It has a dedicated R5 m435dx graphics card which is good enough for gaming. Just don’t expect it to play all and every game. GTA V is playable at 720p Medium preset. The temperatures are very well under limits.
…
READ MORE
Kapil Deshmukh
Certified Buyer, Pune
May, 2017
Permalink
Report Abuse
5
Working as expected
For this price range. Wanted a product that is decent enough with decent processing capability and better than the i3’s. That comes with Windows 10 and with 8GB Ram along with a graphics card of 2gb. This suited me and went for that. Till now working without problem. Not experiencing any lag in running my apps (like illustrator and Photoshop) and.
Came with McAfee Anti Virus. Will not be good to let that run for web safe mode because that could lag your browser experience. So keeping the leas…
READ MORE
Flipkart Customer
Certified Buyer, Bangalore
May, 2017
Permalink
Report Abuse
3
Decent product
Good product ,but boot up take some time,and battery back up up to 3 hrs and can be compared with Intel i3 laptops.good for beginers and don’t take it if u had already purchased or used i3 go for IdeaPad 310 with I-57 processor it’s available for around 40000 with dos and 44000 for laptop with Windows 10 home edition.if u know to install drivers and all go for hp laptop with improved rmd processor R5 and r7 around 30000 rs in that it has only dos,u should install windows and necessary softwar…
READ MORE
Flipkart Customer
Certified Buyer, Arumanai
Jun, 2017
Permalink
Report Abuse
4
Awesome delivery within 1 day Wow
Coming to the laptop, this is a fairly decent specification based on the price.
AMD A10 7 gen with a R6 graphics card is a good if not better alternative to Intel. RAM is DDR4 which is a plus point. Initially had some trouble with the booting afterwards was a charm. Movies play well with Dolby enhanced sound and the 15.6 inch screen is rightful companion to the experience.Tried running games like Witcher 3, lags a lot even in low graphics The only drawback is the outer covering is like a magn…
READ MORE
Pramit Dey
Certified Buyer, Kolkata
Feb, 2017
Permalink
Report Abuse
5
Highly recommended
Excellent specs. Value for money. Good looks. Good battery backup. Sound is good for a laptop. What more can you ask? Great delivery by flipkart. Been using it for about a week now.
What could have been done better? The shift key on the right side is not on the usual place so typing is a bit clumsy till we get used to this keyboard. 5 stars.
READ MORE
Sujith Cherian
Certified Buyer, Ernakulam
Jul, 2017
Permalink
Report Abuse
4
Wonderful
I am writing after using it for almost a week.
The graphics quality and processing speed is really satisfactory. Size is a little bigger than other 15.6in laptops but weight is light.
I can play games like Skyrim and Fallout on medium-high settings with 35-50fps. League of Legends gives steady 33fps. Haven’t tried newer games. Battery stays on for 1.5 hours with gaming and 3hrs with movie etc. But can’t expect it all at this price!
The only downside is heating. Heat dissipation is a little …
READ MORE
Rushikesh Ashtikar
Certified Buyer, Gandhinagar
Apr, 2017
Permalink
Report Abuse
+
All 131 reviews
Questions and Answers
Q:Is it good for photoshop ?
A:Yes, it is good for photoshop
Anonymous
Certified Buyer
Report Abuse
Q:Is this laptop good for programming with codeblocks and TurboC ++
A:Yes it is, this laptop processor is equal to Intel I5.
We are in a kind of miss conception that Intel processors are good, around the world AMD processors are best Its a marketing strategy by company
Anonymous
Certified Buyer
Report Abuse
Q:Is it better than i5 7th gen for gaming ?
A:yes of course better than that because A10 7th gen.
However i have restart issue with the machine since i got it from flipkart and i have visited the service station twice still the problem persists
Siddharth Jogi
Certified Buyer
Report Abuse
Q:Is there fingerprint scanner
What is unique in it?
A:Nothing unique. Budget laptop with 8gb ram.
Anonymous
Certified Buyer
Report Abuse
Read other answers
Q:does it support designing software like autocad, pro E??
A:yes
Anonymous
Certified Buyer
Report Abuse
Q:Would this laptop be good for graphic designing?
A:Average
Anonymous
Certified Buyer
Report Abuse
Read other answers
Q:how long the battery lasts
A:Around 3 hours
Bhuvanesh S
Certified Buyer
Report Abuse
Read other answers
Q:Does it support window 7 and 8
A:Yes it supports.
I have been using it over 6months now.. It’s simply wow..
I have bought it in exchange with my old Compaq laptop. And it’s value for money.
TARUN DAS
Certified Buyer
Report Abuse
Read other answers
Q:Is d screen is full hd ?
A:No just HD
Bhuvanesh S
Certified Buyer
Report Abuse
Q:does window 10 cd comes with it? and it is i3 or i5
A:No it doesn’t comes with windows 10 cd…it comes preinstalled…and it have a AMD processor not i3 or i5.
Sujeet Priyadarshi
Certified Buyer
Report Abuse
All questions+
Safe and Secure Payments.Easy returns.100% Authentic products.
Amd A10 — Computers & Laptops for sale in India
- Home/
- Electronics & Appliances/
- Computers & Laptops/
Categories
Computers & Laptops
-
All Categories
-
Electronics & Appliances
- Computers & Laptops (57)
- Computer Accessories (3)
- Hard Disks, Printers & Monitors (1)
Locations
India
-
- Maharashtra (10)
- Karnataka (9)
- Madhya Pradesh (8)
- Tamil Nadu (6)
- Rajasthan (6)
- Bihar (4)
- Haryana (3)
- Punjab (2)
- Delhi (2)
- Kerala (2)
- Chhattisgarh (1)
- West Bengal (1)
- Uttar Pradesh (1)
- Uttaranchal (1)
- Chandigarh (1)
Filters
Budget
Choose a range below
050,000+
Showing results for «amd a10»57 ads
Sort By : Date Published
-
Featured
₹ 17,499Hp laptop 745 G3 8th gen Amd A10
Chiriyatand Chauraha, Patna27 Sep
-
Featured
₹ 2,500branded desktop dc,c2d,i3,i5,amd a10,smart pc avl bulk qty best price
Nelpettai, Madurai4 days ago
-
Featured
₹ 9,999ACER AMD A10 R7 Hi Gaming 4.
ghz speed 4gb/500gb/18.5 moniter warantyAPMC Gokak, Gokak26 Sep
-
₹ 12,500Lenovo ,Hp AMD A10(same i7 4th gen equal)4gb 8gb ram,500gb 1tb HDD mix
Kamraj salai, MaduraiToday
-
₹ 21,500Hp laptop G3 Ryzen 7 AMD A10 processor Ram 8gb 256gb
Dak Bungalow Chauraha, PatnaToday
-
₹ 23,500Hp 745 g3 amd a10
Dak Bungalow Chauraha, PatnaToday
-
Want to see your stuff here?
Make some extra cash by selling things in your community. Go on, it’s quick and easy.
-
₹ 25,000Hp Cpu with AMD pro A10-9700 R7
Baundli, SamralaYesterday
-
₹ 19,500Hp 745 G3 AMD processor A12 or A10 Ram 8Gb 256gb
Dak Bungalow Chauraha, Patna2 days ago
-
₹ 16,500Hp AMD A10 6th gen slim laptop, 8gb ram, 256 ssd, 2gb graphic intel hd
Sector 20C, Chandigarh3 days ago
-
₹ 27,000HP AMD A10 , 256gb ssd , 8gb ram
Ghee Mandi, Amritsar2 days ago
-
₹ 12,800HP Elitebook 745 G2 AMD A10 Pro
Ambattur Srinivasa Nagar, Chennai2 days ago
-
₹ 14,300Hp ProBook 445 G2/AMD A10/8GB RAM/255GB SSD
KTC Nagar, Tirunelveli3 days ago
-
₹ 15,499Acer E5-551/ AMD A10 -7thgen(4GB-2TB)laptop
Wadi, Nagpur3 days ago
-
₹ 15,100(YASHIKA) LAPTOP HP 445 G2 AMD A10 7300 (4C +6G) QUAD CORE PROCESSOR
Siyaganj, Indore3 days ago
-
₹ 15,100(YASHIKA) LAPTOP HP 445 G2 AMD A10 7300 (4C +6G) QUAD CORE PROCESSOR
Adarsh Nagar, Jabalpur3 days ago
-
₹ 7,500Hp AMD A10 7th gen 16 gb ram 128 gb ssd 500 gb hdd2 gb graphics 7500rs
MI Road, Jaipur4 days ago
-
₹ 15,000745 G3 HP Elatebook AMD A10 Ram 8GB Excellent Condition Rs15000/-
Jharsa, Gurgaon4 days ago
-
₹ 17,500HP EliteBook 745 G3 AMD A10 PRO 8700B 8GB RAM/ 120GB SSD / 500GB HDD
Sadar Bazaar, Nagpur4 days ago
-
₹ 9,700(YASHIKA) (PLAY GOD-IV, GTA-V) AMD A10 7800B(12 Compute Cores 4C+8G)
Siyaganj, Indore4 days ago
-
₹ 9,700(YASHIKA) (PLAY GOD-IV, GTA-V) AMD A10 7800B (12 COMPUTE CORES 4C+8G)
New Market tt Nagar, Bhopal4 days ago
Core i5-11260H vs A10-9700 — How Many FPS
Availability
No items available
Availability
AMD AD9700AGABBOX 7th Generation A10-9700 Quad-Core Processor with Radeon R7 Graphics
Buy on Amazon
$164.
79
In Stock
Updated 25 minutes ago
Key Differences
In short — Core i5-11260H outperforms A10-9700 on the selected game parameters. We do not have the prices of both CPUs to compare value. The better performing Core i5-11260H is 1384 days newer than A10-9700.
Advantages of Intel Core i5-11260H
-
Performs up to 33% better in League of Legends than A10-9700 — 1068 vs 803 FPS
-
Consumes up to 46% less energy than AMD A10-9700 — 35 vs 65 Watts
-
Can execute more multi-threaded tasks simultaneously than AMD A10-9700 — 12 vs 4 threads
League of Legends
Resolution
1920×1080
Game Graphics
High
Core i5-11260H
Mobile • May 11th, 2021
FPS
1068
100%
Value, $/FPS
Price, $
FPS Winner
A10-9700
Desktop • Jul 27th, 2017
FPS
803
67%
Value, $/FPS
$0.21/FPS
100%
Price, $
$164.
79
100%
Value Winner
AMD AD9700AGABBOX 7th Generation A10-9700 Quad-Core Processor with Radeon R7 Graphics
Buy for $164.79 on Amazon
In Stock
Updated 25 minutes ago
Resolution
1920×1080
Game Graphics
High
Core i5-11260H
Mobile • May 11th, 2021
A10-9700
Desktop • Jul 27th, 2017
1068
FPS
803
FPS
League of Legends
267
FPS
197
FPS
Grand Theft Auto V
1423
FPS
1078
FPS
Minecraft
655
FPS
486
FPS
Counter-Strike: Global Offensive
467
FPS
344
FPS
VALORANT
Geekbench 5 Benchmarks
Core i5-11260H
Mobile • May 11th, 2021
Single-Core
1249
100%
Multi-Core
5359
100%
A10-9700
Desktop • Jul 27th, 2017
Single-Core
499
-50%
Multi-Core
1497
-158%
|
Intel Core i5-11260H |
vs |
AMD A10-9700 |
|---|---|---|
|
May 11th, 2021 |
Release Date | Jul 27th, 2017 |
| Core i5 | Collection | A10 |
| Tiger Lake | Codename | Bristol Ridge |
| Intel BGA 1499 | Socket | AMD Socket AM4 |
|
Mobile |
Segment |
Desktop |
|
6 |
Cores | 4 |
|
12 |
Threads | 4 |
2. 6 GHz |
Base Clock Speed |
3.5 GHz |
|
4.4 GHz |
Turbo Clock Speed | 3.8 GHz |
|
35 W |
TDP | 65 W |
|
10 nm |
Process Size | 28 nm |
| 26.0x | Multiplier |
35.0x |
| UHD Graphics 750 | Integrated Graphics | Radeon R7 |
| No | Overclockable | No |
Builds Using Core i5-11260H or A10-9700
League of Legends, 1080p, High
ASUS TUF Gaming F17 Laptop
393 FPS
$3/FPS
GeForce RTX 3050 Mobile
Core i5-11260H
32 GB, 1 TB SSD
Buy on Amazon
$1,179
In Stock
Updated 24 minutes ago
Asus TUF 17.3″ 144Hz FHD Gaming Laptop
393 FPS
$2.75/FPS
GeForce RTX 3050 Mobile
Core i5-11260H
32 GB, 1 TB SSD
Buy on Amazon
$1,079.99
In Stock
Updated 22 minutes ago
Victus 16 Gaming Laptop
393 FPS
$2.
16/FPS
GeForce RTX 3050 Mobile
Core i5-11260H
8 GB, 512 GB SSD
Buy on Amazon
$849.99
In Stock
Updated 22 minutes ago
ASUS TUF Gaming F17 Laptop
393 FPS
$4.08/FPS
GeForce RTX 3050 Mobile
Core i5-11260H
32 GB, 2 TB SSD
Buy on Amazon
$1,605
In Stock
Updated 23 minutes ago
2022 Asus TUF FX706HE Gaming Laptop
393 FPS
$3.69/FPS
GeForce RTX 3050 Mobile
Core i5-11260H
32 GB, 2 TB SSD
Buy on Amazon
$1,449
In Stock
Updated 20 minutes ago
Asus TUF 17.3″ 144Hz FHD Gaming Laptop
393 FPS
$2.49/FPS
GeForce RTX 3050 Mobile
Core i5-11260H
16 GB, N/A Storage
Buy on Amazon
$979
In Stock
Updated 24 minutes ago
2022 New ASUS TUF High-Performance Gaming Laptop
393 FPS
$2.97/FPS
GeForce RTX 3050 Mobile
Core i5-11260H
16 GB, 1 TB SSD
Buy on Amazon
$1,169
In Stock
Updated 22 minutes ago
ASUS TUF Gaming F17 Premium Laptop
393 FPS
$3.
05/FPS
GeForce RTX 3050 Mobile
Core i5-11260H
32 GB, 1 TB SSD
Buy on Amazon
$1,199.99
In Stock
Updated 23 minutes ago
Asus TUF 17.3″ 144Hz FHD Gaming Laptop
393 FPS
$2.19/FPS
GeForce RTX 3050 Mobile
Core i5-11260H
8 GB, N/A Storage
Buy on Amazon
$859.99
In Stock
Updated 23 minutes ago
ASUS TUF Gaming F17 Laptop
393 FPS
$4.58/FPS
GeForce RTX 3050 Mobile
Core i5-11260H
16 GB, 1 TB SSD
Buy on Amazon
$1,799.98
In Stock
Updated 22 minutes ago
Select from the most popular similar processor comparisons. Most compared processor combinations, including the currently selected ones, are at the top.
Ryzen 7 5800H
N/A Stock
Core i5-11260H
N/A Stock
Core i5-11260H
N/A Stock
Core i7-3610QM
N/A Stock
Core i5-11260H
N/A Stock
Pentium B940
N/A Stock
Core i5-11260H
N/A Stock
Pentium E5800
$119.
95
Core i5-11260H
N/A Stock
FX-8310
N/A Stock
Core i5-11260H
N/A Stock
Core i7-9700T
N/A Stock
Core i5-11260H
N/A Stock
Core i7-3970X
N/A Stock
Core i5-11260H
N/A Stock
Core M-5Y70
N/A Stock
Core i5-11260H
N/A Stock
Core i5-6600T
N/A Stock
AMD A10-5700 vs AMD Ryzen 7 4700U — comparative characteristics and benchmarks of
VS
processors
AMD A10-5700
AMD Ryzen 7 4700U
Which one to choose?
It’s time to choose the winner. What is the difference and which is better in AMD A10-5700 vs AMD Ryzen 7 4700U comparison? Which processor is more powerful and faster? It is quite simple to determine — look at the comparative table of all characteristics. A processor with more cores/threads, as well as a higher frequency and large L2-L3 is the absolute winner!
Cores, base and turbo frequency of the processor
Who will win in the comparison of AMD A10-5700 and AMD Ryzen 7 4700U.
The overall performance of a processor can be easily determined based on the number of cores, threads, base and turbo clock speed + L2-L3 volume. The more cores, L3, and clock speed, the more efficient the processor. Please note that high specifications require the use of a powerful cooling system.
3.40 GHz
Clock frequency
2.00 GHZ
4
Number of nuclei
8
4 No
Acceleration
No.
40009
It’s hard to compare AMD A10-5700 vs AMD Ryzen 7 4700U when graphics card function and specs only matter in laptops. In workstations, this is not an advantage, due to the installation of an additional graphics accelerator.
AMD Radeon HD 7660d
Name GPU
AMD Radeon 7 Graphics (Renoir)
0.80 GHZ
Frequency GPU
1.60 GHZ
NO TURBO
GPU 9000 GPU (TURBO) 9000 GPU (TURBO) 9000 GPU (TURBO) 9000 GPU (TURBo0003
4
Generation
11
version DirectX
12
6
Executive blocks
7
384
Number of shaders
9000 448 9000 9000
maximum memory
Maximum memory maximum memory
2 GB
2
Number of monitors
3
32 nm
Technology
7 nm
Q3/2012
Release date
0002 Q1/2020
Hardware codec support
Here we are dealing with specifications that are used by some processor manufacturers.
These figures are mostly technical and can be disregarded for comparative purposes.
Decode
H364
Decode / Encode
Decode / Encode
JPEG
Decode / EncoDe0003
h365 10bit
Decode / Encode
No
VP8
Decode / Encode
No
VP9
Decode / Encode
Decode
VC-1
Decode
Decode
AVC
Decode / Encode
RAM and PCIe
These are the memory standards supported by processors. The processor can support multi-channel RAM with a high clock speed, this directly affects its speed and performance.
DDR3-1866
Type of memory
DDR4-3200LPDR4-4266
Maximum memory
32 GB
2
2
2
NO
ECC 9000 Memory & Memory PCIe
Thermal management and TDP
Today’s systems are loaded with demanding games and workloads, which consequently unleash the full potential of the processor.
When choosing between AMD A10-5700 and AMD Ryzen 7 4700U, it is better to choose the option with less heat dissipation (TDP).
65 W
TDP
15 W
—
Maximum temperature
105 °C
—
Maximum TDP 3
0003
—
TDP Down
10 W
4.00 MB
L3-CACHE
8.00 MB
32 Nm
Technology
7 NM
TRINITY
Architecture
Renoir (Zen 2)
AMD-V
Virtualization
AMD-V, SEV
FM2
SOCKET (DVR)
FP6
Q3/2012
Release
Q1/2020 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000
002 ca. 100 $
Price
Compatible devices with this processor
You probably already know which devices use processors. It can be a desktop computer or a laptop.
Unknown
Used in
ASUS ZenBook 14Acer Swift 3
Cinebench R11.
5, 64bit (Single-Core)
This synthetic benchmark will help you determine the actual processing power of a single CPU core. Cinebench R11.5 is based on MAXON CINEMA 4D and uses 9 different test scenarios0003
AMD A10-5700
4x 3.40 GHz (4.00 GHz)
103 (100%)
AMD Ryzen 7 4700U
8x 2.00 GHz (4.10 GHz)
Cinebench R11.5, 64bit (Multi-Core)
Cinebench R11.5 performs simultaneous cross-platform tests on all processor cores. Running realistic 3D scenes, this benchmark will unleash the full potential of your single-core Intel or AMD
processor
AMD A10-5700
4x 3.
40 GHz (4.00 GHz)
300 (100%)
AMD Ryzen 7 4700U
8x 2.00 GHz (4.10 GHz)
Cinebench R11.5, 64bit (iGPU, OpenGL)
Cinebench 11.5 is based on Cinema 4D Suite, a popular software for creating shapes and other things in 3D. The iGPU test uses the processor’s internal graphics unit to execute OpenGL commands.
AMD A10-5700
4x 3.40 GHz (4.00 GHz)
440 (100%)
AMD Ryzen 7 4700U
8x 2.00 GHz (4.10 GHz)
Cinebench R15 (Single Core)
The latter is used to create 3D models and shapes.
Cinebench R15 is used to benchmark the performance of single core processors. Hyperthreading capability is not taken into account. It is an updated version of Cinebench 11.5. Like all new versions, the updated benchmark is based on Cinema 4 Suite software
AMD A10-5700
4x 3.40 GHz (4.00 GHz)
56 (29%)
AMD Ryzen 7 4700U
8x 2.00 GHz (4.10 GHz)
188 (100%)
Cinebench R15 (Multi-Core)
Cinebench R15 can be used to test the performance of multi-core processors. The test produces accurate and reliable results. This benchmark is an updated version of Cinebench 11.5, which is based on Cinema 4 Suite soft.
AMD A10-5700
4x 3.40 GHz (4.00 GHz)
231 (100%)
AMD Ryzen 7 4700U
8x 2.00 GHz (4.10 GHz)
Cinebench R20 (Single Core)
Cinebench R20 is based on Cinema 4 Suite. This is software used to create 3D shapes. The benchmark runs in single-core mode without considering the possibility of hyper-threading.
AMD A10-5700
4x 3.40 GHz (4.00 GHz)
AMD Ryzen 7 4700U
8x 2.
00 GHz (4.10 GHz)
464 (100%)
Cinebench R20 (Multi-Core)
This is a new version of the benchmark based on Cinebench R15 (both versions are based on Cinema 4, the most popular 3D modeling software). Cinebench R20 is used for benchmark tests of multi-core processor performance and hyper-threading capabilities.
AMD A10-5700
4x 3.40 GHz (4.00 GHz)
AMD Ryzen 7 4700U
8x 2.00 GHz (4.10 GHz)
2424 (100%)
Cinebench R23 (Single Core)
Cinebench R23 is a new version of the most popular single-core CPU rendering benchmark Cinebench.
We have results for all modern processors
AMD A10-5700
4x 3.40 GHz (4.00 GHz)
AMD Ryzen 7 4700U
8x 2.00 GHz (4.10 GHz)
1184 (100%)
Cinebench R23 (Multi-Core)
Cinebench R23 is a new version of the most popular multi-core CPU rendering benchmark, Cinebench. We have results for all modern processors
AMD A10-5700
4x 3.40 GHz (4.00 GHz)
AMD Ryzen 7 4700U
8x 2. 00 GHz (4.10 GHz)
6874 (100%)
Geekbench 3, 64bit (Single-Core)
Geekbench 3 is a benchmark for 64-bit Intel and AMD processors. It uses a new power rating system for a single processor core. This software simulates real scenarios for accurate results
AMD A10-5700
4x 3.40 GHz (4.00 GHz)
1892 (100%)
AMD Ryzen 7 4700U
8x 2.00 GHz (4.10 GHz)
Geekbench 3, 64bit (Multi-Core)
Geekbench 3 supports multi-core AMD and Intel processors. Being based on MAXON CINEMA 4D, it allows you to get the real comparative potential of the processor
AMD A10-5700
4x 3. 40 GHz (4.00 GHz)
5210 (100%)
AMD Ryzen 7 4700U
8x 2.00 GHz (4.10 GHz)
Geekbench 5, 64bit (Single-Core)
Geekbench 5 is the latest software. Completely new algorithms provide fairly accurate test results for single-core processors.
AMD A10-5700
4x 3.40 GHz (4.00 GHz)
473 (42%)
AMD Ryzen 7 4700U
8x 2.00 GHz (4.10 GHz)
1121 (100%)
Geekbench 5, 64bit (Multi-Core)
Geekbench 5 shows benchmark results for memory performance and multi-core processor speed. This takes into account the ability to hyperthreading.
AMD A10-5700
4x 3.40 GHz (4.00 GHz)
1263 (100%)
AMD Ryzen 7 4700U
8x 2.00 GHz (4.10 GHz)
Estimated results for PassMark CPU Mark
It tests all and general CPU performance (math calculations, compression and decompression speed, 2D&3D graphics tests). Please note that data may differ from actual situations.
AMD A10-5700
4x 3.40 GHz (4.00 GHz)
4252 (100%)
AMD Ryzen 7 4700U
8x 2. 00 GHz (4.10 GHz)
iGPU — FP32 Performance (Single-precision GFLOPS)
This test measures the performance of integrated graphics on Intel and AMD processors. The result is the calculated processing power in Single-Precision mode FP32
AMD A10-5700
4x 3.40 GHz (4.00 GHz)
614 (42%)
AMD Ryzen 7 4700U
8x 2.00 GHz (4.10 GHz)
1433 (100%)
Popular processor comparisons
| one. |
AMD Ryzen 7 4700U vs. AMD Ryzen 7 5700U |
|
| 2. |
AMD Ryzen 7 5700U vs. AMD Ryzen 7 4700U |
|
| 3. |
AMD A10-5700 vs. Intel Pentium Silver N5030 |
|
|
four. |
AMD A10-4600M vs. AMD A10-5700 |
|
| 5. |
AMD A10-5700 vs. AMD A10-5800K |
|
| 6. |
AMD A10-5700 vs. AMD A8-7650K |
|
| 7. |
AMD A10-5700 vs. Intel Celeron G5920 |
|
| eight. |
AMD A10-5700 vs. Intel Core i3-2100T |
|
|
9. |
AMD A10-5700 vs. Intel Core i9-10900K |
|
| ten. |
AMD A10-5700 vs. AMD Ryzen 5 PRO 4650G |
|
| eleven. |
AMD A10-5700 vs. Intel Pentium 957 |
|
| 12. |
AMD A10-5700 vs. Intel Xeon E5-2640 v2 |
|
| 13. |
AMD A10-5700 vs. AMD Ryzen 7 4700U |
|
|
fourteen. |
AMD A10-5700 vs. Intel Core i5-5250U |
|
| fifteen. |
AMD A10-5700 vs. AMD A9-9425 |
Overview of AMD A10-7850K and A10-7700K processors
In January of this year, the company AMD introduced the next generation of APUs codenamed Kaveri . In the new APUs, the manufacturer tried to implement its most promising developments. Computing cores were transferred to the Steamroller architecture, the graphics unit was built according to the progressive GCN patterns, while the processors themselves are manufactured according to the 28-nanometer process technology. Let’s use the example of A10-7850K and A10-7700K to take a closer look at what the manufacturer’s new chips are capable of.
Steamroller processor architecture
The x86 Kaveri processor unit uses the Steamroller architecture, which should increase the computing performance of the APU. Evaluating the changes made, we can say that Steamroller is rather an evolutionary development of Piledriver, which is used in Trinity/Richland chips. Here, a modular dual-core structure is still involved, in which some of the blocks are common to both cores. In particular, we are talking about blocks for decoding instructions and floating point operations. This approach allows us to somewhat simplify the overall structure of the chip, however, under certain conditions, with multi-threaded loads, such a model causes downtime of computing units.
Course
Development in Java
Introduce the popular Java programming language at your best hour, and earn $1000 per cob of career
REGISTER!
Steamroller tried to partially solve this problem by dividing the instruction decoder into two independent blocks for each core. This is one of the most dramatic improvements of the new architecture, which should increase the performance of the processor when working with integer calculations. The FPU still remains the same for both cores of the module, as does the fetch unit. However, some improvements have been made here as well. In particular, the prefetch block algorithm has been improved, from 64 KB to 9The instruction cache has been increased by 6 KB, and a number of secondary parameters have been optimized.
However, even for such changes it was necessary to significantly increase the number of transistors. And this is one of the reasons why AMD is in no hurry to release processors that include more than two paired modules.
The Steamroller does not offer any additional instruction sets. In this regard, the new architecture repeats Piledriver.
Graphics Core Next (GCN) 9 graphics architecture0009
Kaveri processors have received an advanced Radeon R7 graphics unit, which uses the latest GCN 1.1 architecture, similar to that used for high-end GPU graphics cards from the Hawaii family.
For AMD APUs, the integrated graphics unit is much more than just a display tool. The video core, called Specter, occupies 47% of the area of the entire crystal. In the maximum configuration, the Kaveri APU can contain 8 clusters, totaling 512 computing units. Recall that the Trinity/Richland chips used the VLIW4 architecture, and the number of shader processors did not exceed 384.
Thanks to its powerful integrated graphics by integrated solutions, AMD claims 856 GFLOPS compute performance for its top Kaveri model, with the GPU accounting for over 85% of the total power at 737 GFLOPS.
The graphics core also inherited improved video processing units. In particular, a unified UVD 4 video decoder and an improved VCE 2 encoding engine.
Given that the video core is based on the GCN architecture, the hybrid chip automatically receives support not only for DirectX 11.2, but also for the new low-level Mantle API, which allows more efficient use of GPU resources. In addition, the new APUs also feature a hardware DSP to implement AMD TrueSound. Support for this promises the opportunity to experience complex sound effects that will not load the computing unit. Of course, as in the case of Mantle, one cannot do without the due effort of software developers.
HSA concept
The previously listed features of the new APUs deserve special attention, but Kaveri finally implements mechanisms that give meaning to the catchy definition of «hybrid processor». We are talking about the technological solutions necessary for the ephemeral concept of HSA (Heterogeneous System Architecture) to be put into practice.
Support for hUMA technology (Heterogeneous Uniform Memory Access) allows you to solve the problem of accessing heterogeneous computing units to a single address space. In this case, there is no need to separate the video memory that is available to the GPU and the system area that x86 blocks work with. The implementation of hUMA should significantly simplify the development of applications and, in particular, algorithms for connecting all APU resources.
Another important technology implemented in Kaveri is hQ (Heterogeneous Queuing). It allows you to increase the autonomy of all computing units. In this case, the GPU gets the right to create independent threads for parallel execution of code without additional control from the CPU, as it was before.
It is for this reason that AMD specifies the total number of CPU and GPU units, and not just x86, to indicate the number of computing cores (Compute Core) of Kaveri processors. As a result, the top model appears as a 12-core APU (4 CPU + 8 GPU).
However, HSA hardware support alone is not enough to take advantage of this configuration. A software ecosystem is needed, which is built at a slower pace. The OpenCL 2.0 framework, which was approved in November 2013, should make the work of programmers easier. Here, in fact, the foundations are laid for the effective use of heterogeneous computing, such as the use of a common address space, work with shared virtual memory, dynamic parallelism, and other functions. Applications that implement HSA will have to wait. Actual programs that already use GPGPU calculations for some functions still implement only the capabilities of OpenCL 1.1 / 1.2.
Today, the number of applications that use heterogeneous computing, although growing, is still not growing as fast as we would like. In addition, not all algorithms can effectively use GPU resources, so the list of applications with appropriate optimization mainly includes packages for working with multimedia data. But among the applications that are used in everyday work, there are not so many striking examples.
Kaveri 9 processors0009
The new APUs are manufactured at Globalfoundries facilities at 28nm standards. The manufacturer managed to set up the production of crystals using this technical process, but it turned out to be not so easy to do.
The fact is that due to the more complex architecture and modular design features, Kaveri contains 2.41 billion transistors, which is almost twice as much as Richland’s 32nm APUs (1.3 billion). If we take into account that the physical area of the crystal remained practically unchanged — 245 vs. 246 mm² — the density of the transistor layout has almost doubled.
At launch, Kaveri’s chip line includes three APUs. The top model A10-7850K has a base frequency of 3.7 GHz with the ability to boost up to 4 GHz. The presence of the “K” index in the designation already habitually speaks of an unlocked multiplier, which makes it quite easy to force the processor. The graphic block includes 8 clusters with 512 calculators. The nominal frequency for the GPU is 720 MHz. The thermal package of the chip is 95 watts.
Model A10-7700K 9The 0602 also has two twin x86 blocks, but the base frequency of the chip is reduced to 3.5 GHz, and the dynamic acceleration threshold is 3.8 GHz. The number of computing graphics clusters has been reduced to 6, so the number of shader units is 384. At the same time, the GPU frequency has not been changed — 720 MHz. The TDP of this APU also falls within the 95 W range, and the “K” index in the model name is a sign that the chip allows overclockers to fool around.
The third model in the new APU line — quad-core A8-7600 . This chip is interesting in that it allows you to configure the power consumption depending on the operating conditions. If you need maximum economy, the APU can operate at 3.1/3.3 GHz, keeping within the TDP of 45 watts. If performance is a priority, then the processor operates according to the formula 3. 3 / 3.8 GHz, but its thermal package increases to 65 watts. The user can switch between modes on their own using the appropriate option in the BIOS of the motherboard. In principle, the idea of reducing power consumption by lowering clock speeds is a classic example of downclocking, which is often used by enthusiasts if they need to reduce CPU heat. Regardless of the mode, the GPU with 384 computers on board (like the A10-7700K) runs at 720 MHz.
The older model A10-7850K is priced at $172, the recommended price for the A10-7700K is $152, while the A8-7600 will be offered for $119. AMD’s pricing policy for new APUs is up for debate. Recall that the top chip of the Richland line is offered for $142. The cost of the new flagship is 20% higher than that of its predecessor. Obviously, the manufacturer believes in the high potential of Kaveri, raising the upper price bar to actually the level of quad-core Intel processors.
Socket FM2+
Kaveri APUs require a Socket FM2+ motherboard. Similar models appeared on sale last year, a few months before the announcement of new APUs. The boards are backwards compatible and will work without problems with Trinity/Richland processors, but, alas, you won’t be able to use Kaveri on devices with Socket FM2 due to differences in electrical wiring. To exclude attempts to self-upgrade, the chips even have mechanical incompatibility, so new APUs are not installed in FM2.
For entry-level systems based on Socket FM2+, we offer the AMD A55 chipset, which has been in service since the first Llano hybrid processors for Socket FM1. Recall that this chipset does not have built-in support for USB 3.0 and SATA 6 Gb / s, if necessary, these interfaces are implemented using additional controllers, but given the positioning of boards based on this chipset, this happens extremely rarely.
9 available for midrange motherboards0601 AMD A78 . Functionally, it is analogous to the A75, which means that the chipset supports 4 USB 3. 0 ports and has 6 SATA 6 Gb / s channels. However, even more popular is the AMD A88X with an eight-port SATA 6 Gb/s controller and the ability to split PCI Express processor lanes in x8+x8 mode for CrossFire mode.
Considering the general positioning of the platform, the price of the most expensive models based on AMD A88X is $120-140, while the vast majority of boards cost no more than $100. And in general, the choice of boards with Socket FM2+ is quite large. The hotline.ua catalog currently contains more than four dozen devices of various form factors. Finding the right option will not be a problem.
Processors for FM2+ bring the ability to transmit a picture with 4K resolution via HDMI. In addition, the new APUs also received a PCI Express 3.0 controller, allowing for the first time to «loop» a high-speed bus within the AMD platform. Motherboards with an FM2+ connector based on the A78 and A88X, which appeared much earlier than the APU Kaveri, a priori support this feature, well, video cards with PCI-E 3. 0 have been on sale for more than two years.
AMD A10-7850K and A10-7700K
To get acquainted with the capabilities of Kaveri, we used two models currently available — A10-7850K and A10-7700K. The processors are offered in boxes with a bright and rather stylish design.
The kit includes the processor itself in a clear plastic blister, a small shaped logo sticker, and a brochure with a quick installation guide. The APU comes with a stock cooling system.
The cooler includes a fairly simple aluminum heatsink that is blown by a 70mm fan. The total height of the cooler is 50 mm. In the area of contact with the processor, thermal paste was initially applied in a «square-nested» way.
During testing, we used the MSI A88X-G45 Gaming motherboard. According to the default CO control algorithm, the fan worked at 1800 rpm in idle mode. Under heavy load on an open bench, the rotation speed increased to 2900 rpm, while the processor temperature was kept at 65 C. The efficiency of such a CO is enough for the processor to operate in normal mode, however, for those who want to overclock the APU, as well as silence, a more efficient alternative will definitely be needed .
The boxed version of the A10-7850K retails for about $185, while the A10-7700K costs about $160. The A8-7600 was supposed to be on sale during the first quarter of this year, but at the time of writing this chip is still not available for purchase.
The A10-7850K processor has a frequency formula of 3.7/4 GHz, while in idle mode the chip frequency drops to 1700 MHz.
The graphics unit in the maximum configuration contains 512 computers, 32 texture modules and 8 rasterization units. The memory bandwidth depends entirely on the frequency of the system RAM. In dual-channel mode with a pair of DDR3-2133 modules, it is 34 GB / s. Of course, for a GPU of this level, the indicator is very low.
The A10-7700K is inferior to the flagship in x86 core clock speed. A pair of dual-core modules operate in 3.5 / 3.8 GHz mode. It is curious that without load, the APU frequency drops to 2000 MHz, and not 1700 MHz, as in the older model.
The graphics core of this processor includes 6 computing clusters for 384 shaders. The number of texture units has decreased to 24, while the number of rasterizers has not changed — 8. The GPU frequency of the already presented Kaveri models is 720 MHz. As for the memory bandwidth, in an identical system configuration with a 128-bit bus, it is still the same 34 GB / s.
Performance
To assess the capabilities of Kaveri processors, we have selected worthy opponents for new chips. First of all, this is the top model of the Richland family — A10-6800K. Comparison with the previous generation APU suggests itself. This APU is a good guideline. Intel processors are represented in this case by the Core i5-4440 model. One of the competitor’s most affordable quad-core CPUs, priced very close to that of the A10-7850K.
Starting with synthetic tests, first of all we evaluated the performance of the memory subsystem and APU caches of different generations.
It is worth noting that the data transfer rate for writing, reading, and copying data to RAM in the case of Kaveri increased slightly, but the memory latency also increased from 67 ns to 77 ns. The speed of writing and copying in L1 has more than doubled, the work of the second-level cache memory has significantly accelerated, but, again, the delays have become slightly longer. How such optimization will affect in practice, the test results will show.
The first measurements show that APUs of the previous generation won’t let beginners relax and the advantage of 400 MHz can offset architectural improvements in some cases. The minimal advantage of the A10-6800K over Kaveri chips in gaming synthetics and the 7-Zip archiver is another confirmation of this. At the same time, 28nm chips cope better with video encoding, despite the significant difference in frequencies. However, the rendering of the scene in Cinebench R15 demonstrates that brute force should not be ignored either. 400 MHz is 400 MHz.
Integer block improvements bring a very significant APU speedup in the Super Pi and wPrime benchmarks. And with chess combinations, Kaveri has gotten better, although with a quad-core Haswell carrier, they still play in different leagues.
After a series of stages in which APUs of different generations fought exclusively with each other, the results of PCMark 8 tests come as a pleasant surprise. Rather, a good performance increase with the involvement of the GPU could well be predicted, but the good optimization of the test package for OpenCL rather even exceeded expectations. Heterogeneous computing on the march. A clear demonstration of how it can be, and this is not yet OpenCL 2.0 involved. The prospects are interesting, the only question is how long it will take for such results to be not a rare exception. There is still a lot of work to be done here.
Integrated graphics testing is a treat for AMD solutions. Hybrid chips have a noticeably more powerful graphics unit than that of Intel processors. Therefore, in this case, it is curious how much the new GPU is improved in comparison with the previous solution built into Richland chips.
In 3DMark tests, the performance gain is 26-33%. At the same time, even the built-in A10-7700K with 384 computers operating at 720 MHz turns out to be noticeably preferable to the integrated graphics A10-6800K, which contains an identical number of shader units and operates at a frequency of 844 MHz.
In real games, a lot depends on the engines used. In general, Kaveri look better, but the situation is different. The A10-7850K is 20% ahead of the A10-6800K in Bioshock Infinite, has a 36% lead in Bafflefield 4, and a more modest 11% in Thief. By the way, the latter allows you to activate the Mantle API. After that, the results of devices with GCN graphics improved by about 10% (charts show figures without Mantle). The exception to the general picture was Total War: Rome II, where the top model with the Radeon R7 could only come close to the results of the A10-6800K.
During the experiments, we also evaluated the impact of memory bandwidth on the performance of the graphics subsystem.
The obtained results are a clear confirmation of the very strong dependence of the indicators on the operating frequency of the memory. FPS can be increased up to 50% by using DDR3-2400 instead of DDR3-1333. In this case, we can say that a set of two DDR3-2133 modules is the minimum required if you plan to use integrated graphics. Faster modules are already more expensive, but in the same 2400 MHz mode, nominal DDR3-2133 kits often work quite normally after a slight increase in timings and supply voltage.
Power consumption
The declared TDP level for both Kaveri models under consideration is 95 W, 5 W higher than the TDP of the A10-6800K, well, the Core i5-4440, according to the specification, should fit within the TDP of 84 W.
During the maximum load on the x86 computing units, the power consumption of the Kaveri chips is about the same as that of the previous flagship. But while playing Battlefield 4, the new APUs turned out to be noticeably more energy efficient. The Core i5-4440 is still far away, but if we recalculate the number of frames / s per watt of energy expended, then this ratio for the new AMD chips will look quite remarkable.
Overclocking
A more modern manufacturing process, as a rule, allows you to count on an improvement in the frequency potential of processors. However, alas, this is not an axiom. Seriously increased layout complexity, as well as almost doubling the density of transistors, affected the frequency potential of Kaveri. Despite the fact that APUs are manufactured according to the 28-nanometer process technology, you should not count on significant overclocking. Taking advantage of unlocked processors, after increasing the supply voltage by 0. 1 V, we managed to increase the clock speed of both Kaveri chips to 4.4 GHz. Not bad, but nothing more. 32nm Richland processors can generally be accelerated to 4.6-4.8GHz, although we can see that they still have lower performance per MHz than Steamroller APUs.
It is also worth noting the overclocking feature of Kaveri. The new APUs have an improved power state regulation mechanism and various mechanisms to avoid overheating of the processor and keep the chip’s power consumption at a given level. In this case, a situation is possible when, under high load, the frequencies of x86 and GPU blocks will automatically decrease, reducing performance, therefore the value of large numbers in the CPU-Z screenshot will be leveled.
We also experimented with overclocking the A10-7700K graphics core. A10-7700K GPU clock speed increased from 720 to 1029MHz (+43%). Note that it is possible to increase the frequency with a certain discreteness, therefore it is difficult to obtain the limiting «stable megahertz».
As you can see, the graphics core has a significant potential for increasing the frequency, but with its increase, the performance does not scale as well as we would like. The fact is that the bottleneck of the graphics subsystem in this case is the memory bandwidth, which is very problematic to increase. Valid RAM mode is DDR3-2400. The Socket FM2+ platform does not provide other boost dividers. High-speed GDDR5 would be here, but, alas, this type of RAM as a system RAM is not yet foreseen even in the medium term.
Despite the very significant overclocking of the GPU, the performance gain is not that great. In synthetic applications, this is a good 20-25%, but in real games, the frames / c increased noticeably more modestly — 5-15%. Note that increasing the operating clock frequency of the GPU from 720 to 1029 MHz increased the power consumption of the system under graphics load by 15–20 watts.
Results
Summing up, with all the desire to avoid ambiguous assessments of new AMD chips, we can’t do it. The processor architecture of Steamroller is indeed more efficient than Piledriver, which often allows not only to level the difference in frequencies of older APU models of two generations, but also in some cases brings Kaveri to the lead. However, in computing tasks with a high load on x86 blocks, even new processors find it difficult to compete with Intel’s quad-core processors. However, there is a lot of power hidden in AMD APUs that can be unleashed using the HSA concept. We have to hope that software developers will increasingly move to the side of heterogeneous computing, given that OpenCL 2.0 makes it possible to significantly simplify this process without requiring serious sacrifices.
For gaming systems or powerful PCs with discrete graphics, Intel chips are still preferable. At the same time, Kaveri processors definitely deserve attention, especially when it comes to assembling a universal system, the owner of which will have enough opportunities for integrated video. APUs have a number of interesting features that do not lie on the surface. The new chips will also be a good choice if you are a techno-romantic at heart who wants to stretch the pleasure of buying over time, rejoicing at the good results of your system in the next optimized application. The price cut will add to the appeal of the new APUs, and it would be interesting to see a new wave of mid-range and entry-level hybrid chips.
AMD A10-7850K, A10-7700 and A10-6800K processors provided for testing by AMD, www.amd.com
Intel Core i5-4440 processor provided for testing by Euro Plus, www.eplus.kiev.ua
Processor A10-9700 [in 3 benchmarks]
AMD
A10-9700
- Interface
- Core frequency
- Video memory size
- Memory type
- Memory frequency
- Maximum resolution
Description
AMD started AMD A10-9700 sales on July 27, 2017 at a suggested price of $90. This is a Bristol Ridge architecture desktop processor primarily aimed at office systems. It has 4 cores and 4 threads and is manufactured using 28nm process technology, the maximum frequency is 3800MHz, the multiplier is locked.
In terms of compatibility, this is an AM4 processor with a TDP of 65W and a maximum temperature of 74°C. It supports DDR4-2400 memory.
It provides poor benchmark performance at
3.52%
from the leader, which is AMD EPYC 7h22.
A10
9700
or
EPYC
7h22
General information
Type information (desktop or laptop) and architecture A10-
- 0
- 50
- 100
Features
A10-9700 quantitative parameters: number of cores and threads, clock speeds, manufacturing process, cache size and multiplier lock state. They indirectly speak about the performance of the processor, but for an accurate assessment, you need to consider the results of the tests.
Compatible
Information on A10-9700 compatibility with other computer components. Useful, for example, when choosing the configuration of a future computer or to upgrade an existing one.
Please note that the power consumption of some processors can significantly exceed their nominal TDP even without overclocking. Some may even double their claims if the motherboard allows you to adjust the power settings of the processor. 9700 technological solutions and sets of additional instructions. This information is needed if the processor is required to support specific technologies.
| AES-NI | + | |
| FMA | + | |
| AVX | + | |
| FRTC | 1 | |
| FreeSync | 1 | |
| PowerTune | + | |
| TrueAudio | + | |
| PowerNow | + | |
| PowerGating | + | |
| 0476 |
Virtualization technologies
The technologies supported by the A10-9700 that accelerate the performance of virtual machines are listed.
| AMD-V | + |
Memory support
Types, maximum size and number of channels of RAM supported by A10-9700. Higher memory frequency may be supported depending on the motherboard. 9700 for performance in non-gaming benchmarks. The overall score is set from 0 to 100, where 100 corresponds to the fastest processor at the moment.
Overall performance in tests
This is our overall performance rating. We regularly improve our algorithms, but if you find any inconsistencies, feel free to speak up in the comments section, we usually fix problems quickly.
A10-9700
3.52
- Passmark
- GeekBench 5 Single-Core
- GeekBench 5 Multi-Core
Passmark
Passmark CPU Mark is a widely used benchmark that consists of 8 different tests, including integer and floating point calculations, extended instruction tests, compression, encryption, and game physics calculations. Also includes a separate single-threaded test.
Benchmark coverage: 68%
A10-9700
3548
GeekBench 5 Single-Core
GeekBench 5 Single-Core is a cross-platform application designed as CPU benchmarks that independently recreate certain real world tasks that can be used to accurately measure performance. This version uses only one processor core.
Benchmark coverage: 37%
A10-9700
498
GeekBench 5 Multi-Core
GeekBench 5 Multi-Core is a cross-platform application designed as CPU benchmarks that independently recreate certain real world tasks that can accurately measure performance. This version uses all available processor cores.
Benchmark coverage: 37%
A10-9700
1490
Relative capacity
Overall performance of the A10-9700 compared to its closest competitor in desktop processors.
Intel Pentium Gold G6400T
101. 14
Intel Core i5-4460T
101.14
AMD Athlon II X4 651
100.85
AMD A10-9700
100
AMD Athlon X4 950
99.72
Intel Core i3-4330
99.72
AMD Ryzen Embedded V1202B
99.43
Competitor from Intel
We believe that the nearest equivalent to A10-9700 from Intel is Core i3-4330, which is approximately equal in speed and lower by 2 positions in our rating.
Core i3
4330
Compare
Here are some of Intel’s closest competitors to the A10-9700:
Intel Pentium Gold G5420
101.42
Intel Core i5-4460T
101.14
Intel Pentium Gold G6400T
101. 14
AMD A10-9700
100
Intel Core i3-4330
99.72
Intel Pentium G4560
99.15
Intel Pentium Gold G5420T
98.86
Other processors
Here we recommend several processors that are more or less similar in performance to the reviewed one.
Athlon X4
950
Compare
Pentium
G4560
Compare
Pentium Gold
G6400T
Compare
Pentium Gold
G5420T
Compare
Pentium Gold
G5420
Compare
A12
9800
Compare
Recommended graphics cards
According to our statistics, these graphics cards are most often used with A10-9700:
Radeon R7
Graphics
25. 5%
GeForce GTX
1050
13.7%
GeForce GTX
1050 Ti
6.8%
GeForce GT
1030
5.9%
Radeon RX
550
5.8%
GeForce GTX
1650
2.4%
Radeon RX
Vega 7
1.9%
Radeon RX
570
1.8%
GeForce GT
710
1.8%
GeForce GT
730
1.6%
User rating
Here you can see the evaluation of the processor by users, as well as put your own rating.
Tips and comments
Here you can ask a question about the A10-9700 processor, agree or disagree with our judgements, or report errors or inaccuracies on the site.
Please enable JavaScript to view the comments powered by Disqus.
2 films and 2 series
In fact, in October, first of all, you need to look through the peephole, secondly, into the mailbox, thirdly, out the window, and fourthly, the condition of the car (is it ready? to the road, whether it is conveniently parked, whether the wheels are pumped up). If the above does not appeal to you, then you should carefully read useful books about survival in the open, hugging a cat or dog.
And at the very end, if there is absolutely nothing to do, you can watch series and movies on the Internet. On the other hand, watching a movie or series will not be superfluous. It helps to switch, relax, calm down, because the news is pouring in such a stream that it’s time to choke. Remembering «Fight Club», the spirit animal that lives in my cave is a sea lion: I want to spank with flippers and yell.
Well, if you are interested in the title, then the answer is in the conclusion.
Table of Contents
- «Era of Survival»
- «DMZ»
- Glitch / «Glitch»
- The Midnight Club
- Night Werewolf
- Avenue 5
- Grimcutty
- Exception / «Exception»
- Shantaram
- The Peripheral
- Guillermo del Toro’s Cabinet of Curiosities / Guillermo del Toro’s Cabinet of Curiosities
- Conclusion
«Era of Survival»
When : already
Considering that almost nothing interesting comes out in cinemas, it is necessary to highlight potentially interesting films. And then there’s fantasy. The description of the film sounds curious:
“The land of the future. Humanity is on the verge of extinction. Although technology has reached an incredibly high level, people every day fight for their lives with nature, which has evolved and turned into a ruthless killer. Restoring balance and tipping the scales that hold the fate of the entire human species — that’s what the 13-year-old girl Vesper has to do.
I decided to mark the film also for the reason that it comes with a rating of 16+, that is, in theory, you can expect a harsh and tough story. All the better!
«DMZ»
When : already
A fantastic TV series «DMZ» is on at «Amediatek». It’s short for «demilitarized zone». A series based on comics about the world of the future, in which there is a civil war between the United States and the Free Armies. There is only one zone without weapons in the country, which is not controlled by anyone, and this is the center of New York. Fantasy, apocalypse, a beautiful picture — everything we love. From the trailer, of course, it is noticeable that the budget was slightly lacking. But let’s not quibble. If someone is already watching the series, then share your impressions in the comments.
Glitch
When : October 7,
In the old days, it would have passed by the show, but Netflix has taught that Korean TV shows released on the service are almost always, if not hits, then a good product. And this series also has an intriguing plot. The Korean boyfriend of the Korean girl (this happens because it takes place in Korea) disappears in a flash of light. Trying to find him, the girl begins an investigation, during which she encounters a group of UFO witnesses.
In theory it should be good and interesting. Last October, a Korean series similar in mystical mystery was released about demons from hell killing their victims. By the way, I’m looking forward to the second season, even more than the notorious «Squid».
The Midnight Club
When : October 7th
Another horror film in anticipation of Halloween. This pagan holiday is indifferent to us, but no one will refuse good horror films.
The plot looks like this. A group of terminally ill teenagers gather in the basement of the hospital and tell scary stories to each other. Along the way, they make a promise that the dead will have to try to contact the still living members of the «night owls» club.
To be honest, of course, it’s annoying that all these teenagers, who, don’t forget, should be terminally ill, look like hefty horses in the frame, which should not be in a hospital, but somewhere in a factory.
Werewolf by Night
When : October 7,
Disney+ is also not far behind and will launch a horror movie based on Marvel comics on October 7th. The film was shot in the retro genre. Kind of a mix of noir and frankenstein. Nothing is clear from the trailer, to be honest, it doesn’t even catch on. However, it is often these releases, from which you expect nothing, that turn out to be the most interesting.
Grimcutty
When : October 10
Another typical autumn horror movie about a certain monster that appeared from social networks. Apparently, right at the headquarters of Facebook * Zuckerberg personally did.
Exception But several factors came together. First, a fantastic dystopian plot. In the distant future, people were forced to leave Earth and move to another galaxy. A forward detachment of spaceships arrives on a planet to be populated. Each team member is printed on a biological 3D printer. And then the action begins. Sounds good, doesn’t it? Well, at least it’s intriguing.
Secondly, Yoshitaka Amano is responsible for the visual component here. This is the artist-designer who made Final Fantasy.
So there is hope that it will turn out to be interesting and unbanal.
The Peripheral / «Peripherals»
When : October 21
Well, frankly, with the new Lord of the Rings series, Amazon Prime did not work out. With great difficulty, I mastered the first series. The girl so generally about the middle asked to go to another room. Well, this is how it usually happens: they wanted the best, but it turned out as always.
At the end of October, Amazon Prime should please with a new series from the creators of Westworld. It will be fantastic again. Nothing is clear from the trailer. The main character puts on some kind of virtual reality headset, and then a video sequence with allusions to the «Throne», «The Matrix» and the inscription «Based on a novel by William Gibson. » Gibson’s novel Neuromancer 1984 years old, by the way, I recently recommended that you read in the context of the series based on the Cyberpunk 2077 universe. This is the work from which all modern cyberpunk fiction has grown.
Peripherals is also a Gibson novel. I have not read it, as the book is relatively recent — it was released in 2014. I don’t know how the series will turn out in the end, but I’ll definitely read the book. And I recommend you.
Guillermo del Toro’s Cabinet of Curiosities
When : October 24
Halloween is celebrated in the United States at the end of September, so it’s no surprise that the number of horror movies is on the rise. Decided to choose this 8-episode series as Guillermo del Toro was hired by Netflix to create it. So we are promised 8 mystical and terrifying stories, which will be released one per day starting October 24th.
The trailer looks very nice. There is a feeling of warm tube horror films when people are frightened by some monsters, monsters from the basement and other cute and far from real life horror.
Conclusion
To be honest, I don’t like October just because of the abundance of horror movies. Every service is trying to come up with something. This time, in principle, lucky. «Peripherals» advised me to read a good science fiction novel. Perhaps Apple managed to make a good series based on Shantar. In theaters, «Era of Survival» is on. The picture looks nice. You can probably still appreciate the «DMZ» and «Avenue 5». Well, the anime «Exception».
In the comments, as always, I propose to talk about the good films and series that you have watched lately.
*Meta Platforms, which includes the social networks Facebook and Instagram, has been recognized as an extremist organization and banned in the Russian Federation.
Video codecs of 2022
Photo by Artyom Belyakin.
Gone are the days when you could invent or build one thing and live on royalty for the rest of your life. In the field of electronics and its accompanying ecosystem, the abolition of this concept is visible to the naked eye. Consumer devices have ceased to be the product of a single company, today its name (brand) is a kind of flag around which not only “their own”, but also hordes of “mercenaries” gather in the form of chips, technologies and software. All this gives rise to fierce competition among manufacturers, because over time, consumer demands are only growing. Or manufacturers themselves will tell consumers about the growth of these needs, trying to gain a competitive advantage and thus stand out from the competition. At a deeper level, different technologies compete for the wallet and/or acceptance of consumer product manufacturers. Given the role of video content quality per se in social media and commercial online television, the film industry and streaming services, invisible things such as codec-based image standards are a critical factor. It is video codecs and their hardware implementation in mobile chipsets, computer video cards, set-top boxes, camcorders, and others that are responsible for the subjective perception of all goods that we buy with our hard-earned money. On this battlefield, manufacturers have laconic goals — to provide the best possible «picture» with the smallest video file size. The smaller the video file, the faster the consumer will receive their virtual product, expressed in emotions. The common name for this process is called «video compression», which includes two scenarios: video encoding and video decoding.
Encoding (compression) occurs during the conversion of vulgar analog video to digital form, and decoding occurs during the transition from a file (digital state) to a visual embodiment on the screen of a smartphone or tablet, TV or laptop, etc. For this reason, all manufacturers of electronic equipment that are somehow connected with the recording, transmission over the network and playback of video content try, if not to support the development of new codecs, then at least in their products to comply with all relevant ones. Gone are the days when a user had to convert a movie from AVI to MP4 in order to watch it while driving to work on their brand new Sony Ericsson. Users have forgotten how to do this, but they have not forgotten how to watch their favorite TV shows and streams. From a smartphone, everyone expects “omnivorousness”, and from services — the immediacy of fulfilling their orders.
Actual video codecs of 2022.
There are no official statistics on the topic “the most used video codecs” in principle. The codec is not a parameter that can be calculated using automatic network analysis. And not only is their use limited to the network, there are local devices, such as video cameras and projectors, that are not tied to any common point from which data can be taken. However, it is possible to come from the demand side of the interested parties. In the case of codecs, these are producers and sellers of video content like Netflix or Google YouTube. You will be surprised, but in 2022 not everyone uses the H.264 codec, there are people who are tightly tied to the ancient Mpeg-2 codec and other antiques. A survey conducted by Bitmovin shows that their customers (content producers) plan their actions in 2022 as follows:
Consider this data as follows: 8% of respondents want to introduce or bring to implementation full support for H.264/AVC, 25% — H.265/HEVC. In all this, the most surprising thing is that the H.264 codec is already 19 years old, but its support is not in all the equipment that is “on hand” and is used to create content (shooting) and / or broadcast it (streaming) via networks. An important clarification is that video encoding (compression) into any format can be done in two ways. Either at the hardware level, or at the software level, using processor power for general computing. In the first case, the operation is performed almost instantly with low power consumption, and in the second, everything is exactly the opposite, it takes a long time and under the noise of the CPU cooling system. So, for example, until April 2021, Google used VP9 software encoding(for 4K video), and after the introduction of specialized Argus transcoding chips into their servers, the encoding time was reduced by 33 times. The tasks of Google YouTube (and other social networks focused on video content) include not only storing the client video file, but also providing access to this video to other users, and then the size of the transferred file is of key importance. As a result, the profitability of such companies comes down to issues of server activity session time (energy consumption) and cost reduction from consumables (the same thermal paste and the exhaustion of the resource of cooling systems).
The introduction of new codecs into new consumer products is precisely to create demand for their hardware support among manufacturers of hardware, chipsets or video cards for the entire range of manufactured devices. To this end, the creators of new codecs get together in teams and actively offer their brainchildren to interested companies. Let me give you an example of such cooperation. In the Nvidia Geforce 3000 series video cards, only hardware support for decoding (playback) of the AV1 codec was implemented, and encoding (compression) was added in the 4000 series. This is necessary so that an economical and better way of storing and transmitting video becomes available to ordinary consumers, among whom there are many bloggers, employees of advertising agencies and PR departments of industrial production, interested in the highest quality video content with smaller storage sizes (I recalled the editor-in-chief with its dozens of external HDDs).
This section should be expanded by mentioning that “the whole world” has long gone to the Internet, where smartphones and other mobile devices rule the roost. The gradual introduction of devices for playing video content of increasing resolution also pushes the development of new video codecs. Based on this, it is enough to recall the requirements of Google Android for smartphone manufacturers (we have repeatedly talked about this), where the H.264 video codec has been key and necessary for several years. Here is the answer to the question “what is the material about”, the issue of updating the standards has long been overdue.
The AV1 codec is still under development, although it is already supported by some chipsets and products at the base level (playback). Among them are smartphones based on Samsung Exynos 2100/2200 chipsets, MediaTek Dimensity 1000 (possibly more recent), several smart TVs and Google’s upcoming Chromecast. Such an explosive growth of interest in the AV1 codec can only be explained by one thing — it shows better image quality at smaller file sizes than all existing ones (on sale). Here is an example compared to the . 265 (HEVC) codec, note the grass:
Isn’t it time to introduce the term «video crop»?
The H.265 video codec is another promising option developed by the MPEG group to replace H.264. It is not known whether he will get to the mass implementation «in hardware», which does not seem strange due to the obvious loss in quality of AV1. But, speaking of the premium mobile segment, H.265 (HEVC) cannot be ignored, it is the only one that supports HDR video with a color depth of 10 bits, there are simply no alternatives. As with other modern codecs, development of HEVC continues and modern consumer devices are limited to basic playback.
If you’re a fan of counting other people’s money, I suggest you go to the Sisvel site and see how much royalty codec developers receive from each device that can play content using their video compression method. These are real drops, but they turn into an ocean after introduction and mass production.
Conclusion
New standards for the storage and transmission of digital information are being developed for a long time, they are being introduced into a mass product even longer, and we may not even live to see the end of support for existing ones. At the same time, ordinary electronics users have absolutely no reason to worry about the apparent stagnation, because the most widely used H.264 codec is not supported except by smart coffee maker chips, and video image quality issues are being resolved by ever-increasing Internet speeds. Indeed, the introduction of new codecs is a headache for Google, Netflix, Kinopoisk and other online cinemas, and not ours. Yes, and I would not want to see every single pimple on the face of an actor or friends, this is already too much, I’m sure not everyone is ready for such a close relationship with the content.
Alexander Noskov
technologies
top
Review of AMD A10-9700 processor: specifications, tests in benchmarks
AMD A10-970 processor was released: July27 2017. At the time of release, the processor cost $90. The processor is designed for desktop computers and is based on the Bristol Ridge architecture.
Processor unlocked for overclocking. The total number of cores is 4. The maximum clock frequency of the processor is 3.8 GHz. Maximum temperature — 90°C. Technological process — 28 nm. Cache size: L2 — 2 MB.
Supported memory type: DDR4.
Supported socket type: AM4. The maximum number of processors in the configuration is 1. Power consumption (TDP): 65 Watt.
The processor integrates Radeon R7 Series graphics with the following graphics parameters: maximum frequency — 1029 MHz, number of cores — 6.
Benchmarks
|
||||||
| PassMark CPU mark |
|
|
||||
| Geekbench 4 Single Core |
|
|||||
| Geekbench 4 Multi-Core |
|
|||||
| 3DMark Fire Strike Physics Score |
|
|||||
| CompuBench 1. Face Detection |
|
|
||||
| CompuBench 1.5 Desktop Ocean Surface Simulation |
|
|
||||
| CompuBench 1.5 Desktop T-Rex |
|
|
||||
| CompuBench 1.5 Desktop Video Composition |
|
|
||||
| CompuBench 1.5 Desktop Bitcoin Mining |
|
|
||||
| GFXBench 4.0 Car Chase Offscreen |
|
|
||||
| GFXBench 4.0 Manhattan |
|
|
||||
| GFXBench 4. T-Rex |
|
|
||||
| GFXBench 4.0 Car Chase Offscreen |
|
|
||||
| GFXBench 4.0 Manhattan |
|
|
||||
| GFXBench 4.0 T-Rex |
|
|
| Name | Meaning |
|---|---|
| PassMark — Single thread mark | 1618 |
| PassMark — CPU mark | 3548 |
| Geekbench 4 — Single Core | 493 |
| Geekbench 4 — Multi-Core | 1465 |
| 3DMark Fire Strike — Physics Score | 0 |
| CompuBench 1. |
20.497 mPixels/s |
| CompuBench 1.5 Desktop — Ocean Surface Simulation | 227.004 Frames/s |
| CompuBench 1.5 Desktop — T-Rex | 1.533 Frames/s |
| CompuBench 1.5 Desktop — Video Composition | 27.928 Frames/s |
| CompuBench 1.5 Desktop — Bitcoin Mining | 87.933 mHash/s |
| GFXBench 4.0 — Car Chase Offscreen | 1358 Frames |
| GFXBench 4.0 — Manhattan | 2370 Frames |
| GFXBench 4.0 — T-Rex | 7174 Frames |
| GFXBench 4. |
1358.000 Fps |
| GFXBench 4.0 — Manhattan | 2370.000 Fps |
| GFXBench 4.0 — T-Rex | 7174.000 Fps |
| Boost Core Clock | 758 MHz |
| Core frequency | 200 MHz |
| Floating point performance | 526.8 gflops |
| Process | 28nm |
| Number of shaders | 384 |
| Texturing Speed | 16. |
| Power consumption (TDP) | 15 Watt |
| Number of transistors | 2,410 million |
Gaming performance
1. Counter-Strike: GO (2012)
2. Total War: Three Kingdoms (2019))
3. F1 2019 (2019)
4. F1 2018 (2018)
5. The Crew 2 (2018)
6. Playerunknown’s Battlegrounds (PUBG) (2017)
7 Team Fortress 2 (2017)
8. Dirt 4 (2017)
9 Rocket League (2017)
10 Mass Effect Andromeda (2017)
11. For Honor (2017)
12 Resident Evil 7 (2017)
13. Dishonored 2 (2016)
14. Call of Duty Infinite Warfare (2016)
15 Titanfall 2 (2016)
16. Farming Simulator 17 (2016)
17 Civilization VI (2016)
18. Battlefield 1 (2016)
19. Deus Ex Mankind Divided (2016)
20 Mirror’s Edge Catalyst (2016)
21 Overwatch (2016)
22. Doom (2016)
23. Hitman 2016 (2016)
24 Far Cry Primal (2016)
25. XCOM 2 (2016)
26 Rise of the Tomb Raider (2016)
27 Rainbow Six Siege (2015)
28 Assassin’s Creed Syndicate (2015)
29 Star Wars Battlefront (2015)
30 Fallout 4 (2015)
31. Call of Duty: Black Ops 3 (2015)
32. Anno 2205 (2015)
33. World of Warships (2015)
34. Dota 2 Reborn (2015)
35. The Witcher 3 (2015)
36 Dirt Rally (2015)
37. GTA V (2015)
38 Dragon Age: Inquisition (2014)
39 Far Cry 4 (2014)
40 Assassin’s Creed Unity (2014)
41. Call of Duty: Advanced Warfare (2014)
42 Alien: Isolation (2014)
43. Middle-earth: Shadow of Mordor (2014)
44 Sims 4 (2014)
45 Wolfenstein: The New Order (2014)
46. The Elder Scrolls Online (2014)
47. Thief (2014)
48. X-Plane 10.25 (2013)
49. Battlefield 4 (2013)
50 Total War: Rome II (2013)
51 Company of Heroes 2 (2013)
52 Metro: Last Light (2013)
53 BioShock Infinite (2013)
54. StarCraft II: Heart of the Swarm (2013)
55. Tomb Raider (2013)
56 Crysis 3 (2013)
57. Hitman: Absolution (2012)
58. Borderlands 2 (2012)
59 Diablo III (2012)
60. The Elder Scrolls V: Skyrim (2011)
61 Deus Ex Human Revolution (2011)
62. World of Warcraft (2005)
Counter-Strike: GO (2012)
| Low, 1024×768 | 57.10 |
| Medium, 1366×768 | 42.90 |
| High, 1366×768 | 38.00 |
| Ultra, 1920×1080 | 23.60 |
Total War: Three Kingdoms (2019)
| Low, 1280×720 | 28.00 |
F1 2019 (2019)
| Low, 1280×720 | 40.50 |
| Medium, 1920×1080 | 16.60 |
F1 2018 (2018)
| Low, 1280×720 | 24.00 |
| Medium, 1920×1080 | 13.80 |
The Crew 2 (2018)
| LOW, 1280×720 | 22.80 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Low, 1280×720 | 20. |
Team Fortress 2 (2017)
| Ultra, 1920×1080 | 32.20 |
Dirt 4 ( 2017)
| Low, 1280×720 | 54.00 |
| Medium, 1920×1080 | 21.10 |
Rocket League (2017)
| Low, 1280×720 | 50.40 |
| Medium, 1920×1080 | 32.00 |
Mass Effect Andromeda (2017)
| Low, 1280×720 | 7.20 |
For Honor (2017)
| Low, 1280×720 | 36.30 |
| Medium, 1920×1080 | 13.30 |
Resident Evil 7 (2017)
| Low, 1280×720 | 48.20 |
| Medium, 1920×1080 | 20. |
Dishonored 2 (2016)
| Low, 1280×720 | 19.10 |
Call of Duty Infinite Warfare (2016)
| Low, 1280×720 | 32.40 |
Titanfall 2 (2016)
| Low, 1280×720 | 60.30 |
| Medium, 1366×768 | 45.20 |
| High, 1920×1080 | 16.60 |
Farming Simulator 17 (2016)
| Medium, 1366×768 | 70.00 |
| High, 1920×1080 | 27.30 |
Civilization VI (2016)
| Low, 1024×768 | 49.70 |
| Medium, 1366×768 | 18.20 |
Battlefield 1 (2016)
| Low, 1280×720 | 13. |
Deus Ex Mankind Divided (2016)
| Low, 1280×720 | 19.48 |
| Medium, 1366×768 | 17.40 |
Mirror’s Edge Catalyst (2016)
| LOW, 1280×720 | 30.45 |
Overwatch (2016)
| LOW, 1280476 LOW, 1280476 LOW, 1280476 LOU.0477 | |
| Medium, 1366×768 | 41.10 |
| High, 1920×1080 | 19.50 |
Doom (2016)
| Low, 1280×720 | 22.30 |
Hitman 2016 (2016)
| Low, 1280×720 | 10.90 |
Far Cry Primal (2016)
| Low, 1280×720 | 20.50 |
| Medium, 1920×1080 | 9. |
XCOM 2 (2016)
| Low, 1280×720 | 23.60 |
| Medium, 1920×1080 | 9.40 |
Rise of the Tomb Raider (2016 )
| Low, 1024×768 | 28.40 |
| Medium, 1366×768 | 17.75 |
| High, 1920×1080 | 8.10 |
Rainbow Six Siege (2015)
| Low, 1024×768 | 53.12 |
| Medium, 1366×768 | 33.70 |
| High, 1920×1080 | 17.63 |
| Ultra, 1920×1080 | 13.70 |
Assassin’s Creed Syndicate (2015)
| Low, 1024×768 | 12.40 |
| Medium, 1366×768 | 7.40 |
Star Wars Battlefront (2015)
| Low, 1024×768 | 25. |
| Medium, 1366×768 | 17.15 |
| High, 1920×1080 | 8.80 |
| Ultra, 1920×1080 | 8.00 |
Fallout 4 (2015)
| Low, 1280×720 | 19.88 |
| Medium, 1366×768 | 14.15 |
| High, 1920×1080 | 6.10 |
Call of Duty: Black Ops 3 (2015)
| Low, 1024×768 | 34.43 |
| Medium, 1366×768 | 22.37 |
| High, 1920×1080 | 14.30 |
Anno 2205 (2015)
| Low, 1024×768 | 27.90 |
| Medium, 1366×768 | 15.38 |
| High, 1920×1080 | 7.25 |
| Ultra, 1920×1080 | 2.20 |
World of Warships (2015)
| Low, 1366×768 | 57. |
| Medium, 1366×768 | 42.05 |
| High, 1920×1080 | 21.55 |
| Ultra, 1920×1080 | 13.27 |
DOTA 2 Reborn (2015)
| 62.65 | |
| Medium, 1366×768 | 46.05 |
| High, 1920×1080 | 29.10 |
| Ultra, 1920×1080 | 26.20 |
The Witcher 3 (2015)
| Low , 1024×768 | 24.10 |
| Medium, 1366×768 | 16.00 |
| High, 1920×1080 | 8.30 |
| Ultra, 1920×1080 | 5.50 |
Dirt Rally (2015)
| Low, 1024×768 | 111.28 |
| Medium, 1366×768 | 36. |
| High, 1920×1080 | 19.97 |
| Ultra, 1920×1080 | 12.93 |
GTA V (2015)
| Low, 1024×768 | 53.55 |
| Medium, 1366×768 | 47.05 |
| High, 1920×1080 | 12.70 |
| Ultra, 1920×1080 | 5.15 |
Dragon Age: Inquisition (2014)
| Low, 1024×768 | 34.04 |
| Medium, 1366×768 | 22.78 |
| High, 1920×1080 | 8.98 |
| Ultra, 1920×1080 | 7.00 |
Far Cry 4 (2014)
| Low, 1024×768 | 33.10 |
| Medium, 1366×768 | 23.85 |
| High, 1920×1080 | 12.15 |
| Ultra, 1920×1080 | 6. |
Assassin’s Creed Unity (2014)
| LOW, 1024×768 | 24.30 |
| Medium, 1366×768 | 16.90 |
CALL OF DVIN0473
| Low, 1024×768 | 50.30 |
| Medium, 1366×768 | 32.70 |
| High, 1920×1080 | 25.45 |
| Ultra, 1920×1080 | 12.25 |
Alien: Isolation ( 2014)
| LOW, 1024×768 | 51.71 |
| Medium, 1366×768 | |
| HIGH, 1
10482, 1 10HA0477 | |
| Ultra, 1920×1080 | 15.67 |
Middle-earth: Shadow of Mordor (2014)
| Low, 1280×720 | 35.25 |
| Medium, 1344×756 | 23.59 |
| High, 1920×1080 | 13. |
| Ultra, 1920×1080 | 10.00 |
Sims 4 (2014)
| Low, 1024×768 | 106.43 |
| Medium, 1366×768 | 41.53 |
| High, 1920×1080 | 24.47 |
| Ultra, 1920×1080 | 20.20 |
Wolfenstein: The New Order (2014)
| Low, 1280×720 | 49.25 |
| Medium, 1280×720 | 47.50 |
| High, 1920×1080 | 26.45 |
The Elder Scrolls Online (2014)
| Low, 1024×768 | 60.00 |
| Medium, 1366×768 | 46.00 |
| High, 1366×768 | 29.90 |
| Ultra, 1920×1080 | 15.40 |
Thief (2014)
| Low, 1024×768 | 24. |
| Medium, 1366×768 | 17.23 |
| High, 1366×768 | 13.54 |
| Ultra, 1920×1080 | 7.03 |
X-Plane 10.25 (2013)
| Low, 1024×768 | 53.33 |
| Medium, 1366×768 | 24.38 |
| High, 1366×768 | 11.58 |
| Ultra, 1920×1080 | 8.35 |
Battlefield 4 (2013)
| Low, 1024×768 | 37.83 |
| Medium, 1366×768 | 29.03 |
| High, 1366×768 | 17.62 |
| Ultra, 1920×1080 | 7.20 |
Total War: Rome II (2013)
| Low, 1024×768 | 53.25 |
| Medium, 1366×768 | 41.80 |
| High, 1366×768 | 36. |
| Ultra, 1920×1080 | 13.00 |
Company of Heroes 2 (2013)
| Low, 1024×768 | 23.28 |
| Medium, 1366×768 | 20.87 |
| High, 1366×768 | 15.50 |
| Ultra, 1920×1080 | 6.28 |
Metro: Last Light (2013)
| LOW, 1024×768 | 33.23 |
| Medium, 1366×768 | |
| HIG, 1366HG0477 | |
| Ultra, 1920×1080 | 8.05 |
BioShock Infinite (2013)
| Low, 1280×720 | 60.49 |
| Medium, 1366×768 | 28.18 |
| High, 1366×768 | 26.10 |
| Ultra, 1920×1080 | 9.18 |
Starcraft II: Heart of the SVARM (2013)
| 94. |
|
| Medium, 1366×768 | 55.90 |
| High, 1366×768 | 37.75 |
| Ultra, 1920×1080 | 16.90 |
Tomb Raider (2013)
| Low, 1024×768 | 74.88 |
| Medium, 1366×768 | 40.32 |
| High, 1366×768 | 27.10 |
| Ultra, 1920×1080 | 14.27 |
Crysis 3 (2013)
| Low, 1024×768 | 35.88 |
| Medium, 1366×768 | 21.55 |
| High, 1366×768 | 14.98 |
| Ultra, 1920×1080 | 6.03 |
Hitman: Absolution (2012)
| Low, 1024×768 | 35.97 |
| Medium, 1366×768 | 29.52 |
| High, 1366×768 | 16. |
| Ultra, 1920×1080 | 8.28 |
Borderlands 2 (2012)
| Low, 1024×768 | 64.50 |
| Medium, 1366×768 | 44.55 |
| High, 1366×768 | 33.75 |
| Ultra, 1920×1080 | 22.90 |
Diablo III (2012)
| Low, 1024×768 | 55.45 |
| Medium, 1366×768 | 40.50 |
| High, 1366×768 | 34.45 |
| Ultra, 1920×1080 | 30.35 |
The Elder Scrolls V: Skyrim (2011)
| Low, 1280×720 | 45.53 |
| Medium, 1366×768 | 32.90 |
| High, 1366×768 | 23.73 |
| Ultra, 1920×1080 | 14.00 |
Deus Ex Human Revolution (2011)
| Low, 1024×768 | 69. |
| High, 1366×768 | 47.95 |
| Ultra, 1920×1080 | 21.60 |
World of Warcraft (2005)
| Ultra, 1920×1080 | 21.00 |
Characteristics0477
configuration