Processor amd a9 vs intel i5: AMD A9-9425 vs Intel Core i5-8265U: What is the difference?

AMD A9-9425 vs Intel Core i5-8265U: What is the difference?

44points

AMD A9-9425

54points

Intel Core i5-8265U

vs

68 facts in comparison

AMD A9-9425

Intel Core i5-8265U

Why is AMD A9-9425 better than Intel Core i5-8265U?

• 458MHz faster GPU clock speed?
  758MHzvs300MHz
• 0.25MB/core more L2 cache per core?
  0.5MB/corevs0.25MB/core
• 15 higher clock multiplier?
  31vs16
• Has FMA4?

Why is Intel Core i5-8265U better than AMD A9-9425?

• 267MHz higher ram speed?
  2400MHzvs2133MHz
• 6 more CPU threads?
  8vs2
• 10°C higher maximum operating temperature?
  100°Cvs90°C
• 14nm smaller semiconductor size?
  14nmvs28nm
• 3.95x higher PassMark result?
  6130vs1552
• 0. 2GHz higher turbo clock speed?
  3.9GHzvs3.7GHz
• 60KB bigger L1 cache?
  256KBvs196KB
• 1.6x higher PassMark result (single)?
  2135vs1331

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 A9-9425

7 User reviews

AMD A9-9425

6. 7/10

7 User reviews

Intel Core i5-8265U

3 User reviews

Intel Core i5-8265U

9.0/10

3 User reviews

Features

Value for money

6.7/10

7 votes

8.3/10

3 votes

Gaming

4.9/10

7 votes

7.3/10

3 votes

Performance

5.9/10

7 votes

9.3/10

3 votes

Reliability

7.0/10

7 votes

9.3/10

3 votes

Energy efficiency

7.9/10

7 votes

8.3/10

3 votes

Performance

1.CPU speed

2 x 3.1GHz

4 x 1.6GHz

The CPU speed indicates how many processing cycles per second can be executed by a CPU, considering all of its cores (processing units). It is calculated by adding the clock rates of each core or, in the case of multi-core processors employing different microarchitectures, of each group of cores.

2.CPU threads

More threads result in faster performance and better multitasking.

3.turbo clock speed

3.7GHz

3.9GHz

When the CPU is running below its limitations, it can boost to a higher clock speed in order to give increased performance.

4.Has an unlocked multiplier

✖AMD A9-9425

✖Intel Core i5-8265U

Some processors come with an unlocked multiplier which makes them easy to overclock, allowing you to gain increased performance in games and other apps.

5.L2 cache

A larger L2 cache results in faster CPU and system-wide performance.

6.L3 cache

Unknown. Help us by suggesting a value. (AMD A9-9425)

A larger L3 cache results in faster CPU and system-wide performance.

7.L1 cache

A larger L1 cache results in faster CPU and system-wide performance.

8.L2 core

0.5MB/core

0.25MB/core

More data can be stored in the L2 cache for access by each core of the CPU.

9.L3 core

Unknown. Help us by suggesting a value. (AMD A9-9425)

1.5MB/core

More data can be stored in the L3 cache for access by each core of the CPU.

Memory

1.RAM speed

2133MHz

2400MHz

It can support faster memory, which will give quicker system performance.

2.maximum memory bandwidth

Unknown. Help us by suggesting a value. (AMD A9-9425)

37.5GB/s

This is the maximum rate that data can be read from or stored into memory.

3.DDR memory version

DDR (Double Data Rate) memory is the most common type of RAM. Newer versions of DDR memory support higher maximum speeds and are more energy-efficient.

4. memory channels

More memory channels increases the speed of data transfer between the memory and the CPU.

5.maximum memory amount

Unknown. Help us by suggesting a value. (AMD A9-9425)

The maximum amount of memory (RAM) supported.

6.bus transfer rate

Unknown. Help us by suggesting a value. (AMD A9-9425)

The bus is responsible for transferring data between different components of a computer or device.

7.Supports ECC memory

✖AMD A9-9425

✖Intel Core i5-8265U

Error-correcting code memory can detect and correct data corruption. It is used when is it essential to avoid corruption, such as scientific computing or when running a server.

8.eMMC version

Unknown. Help us by suggesting a value. (AMD A9-9425)

Unknown. Help us by suggesting a value. (Intel Core i5-8265U)

A higher version of eMMC allows faster memory interfaces, having a positive effect on the performance of a device. For example, when transferring files from your computer to the internal storage over USB.

9.bus speed

Unknown. Help us by suggesting a value. (AMD A9-9425)

Unknown. Help us by suggesting a value. (Intel Core i5-8265U)

The bus is responsible for transferring data between different components of a computer or device.

Benchmarks

1.PassMark result

This benchmark measures the performance of the CPU using multiple threads.

2.PassMark result (single)

This benchmark measures the performance of the CPU using a single thread.

3.Geekbench 5 result (multi)

Geekbench 5 is a cross-platform benchmark that measures a processor’s multi-core performance. (Source: Primate Labs, 2022)

4.Cinebench R20 (multi) result

Unknown. Help us by suggesting a value. (Intel Core i5-8265U)

Cinebench R20 is a benchmark tool that measures a CPU’s multi-core performance by rendering a 3D scene.

5.Cinebench R20 (single) result

Unknown. Help us by suggesting a value. (Intel Core i5-8265U)

Cinebench R20 is a benchmark tool that measures a CPU’s single-core performance by rendering a 3D scene.

6.Geekbench 5 result (single)

Geekbench 5 is a cross-platform benchmark that measures a processor’s single-core performance. (Source: Primate Labs, 2022)

7.Blender (bmw27) result

Unknown. Help us by suggesting a value. (AMD A9-9425)

731.93seconds

The Blender (bmw27) benchmark measures the performance of a processor by rendering a 3D scene. More powerful processors can render the scene in less time.

8.Blender (classroom) result

Unknown. Help us by suggesting a value. (AMD A9-9425)

1694.63seconds

The Blender (classroom) benchmark measures the performance of a processor by rendering a 3D scene. More powerful processors can render the scene in less time.

9.performance per watt

This means the CPU is more efficient, giving a greater amount of performance for each watt of power used.

Features

1.uses multithreading

✖AMD A9-9425

✔Intel Core i5-8265U

Multithreading technology (such as Intel’s Hyperthreading or AMD’s Simultaneous Multithreading) provides increased performance by splitting each of the processor’s physical cores into virtual cores, also known as threads. This way, each core can run two instruction streams at once.

2.Has AES

✔AMD A9-9425

✔Intel Core i5-8265U

AES is used to speed up encryption and decryption.

3.Has AVX

✔AMD A9-9425

✔Intel Core i5-8265U

AVX is used to help speed up calculations in multimedia, scientific and financial apps, as well as improving Linux RAID software performance.

4.SSE version

SSE is used to speed up multimedia tasks such as editing an image or adjusting audio volume. Each new version contains new instructions and improvements.

5.Has F16C

✔AMD A9-9425

✔Intel Core i5-8265U

F16C is used to speed up tasks such as adjusting the contrast of an image or adjusting volume.

6.bits executed at a time

Unknown. Help us by suggesting a value. (AMD A9-9425)

Unknown. Help us by suggesting a value. (Intel Core i5-8265U)

NEON provides acceleration for media processing, such as listening to MP3s.

7.Has MMX

✔AMD A9-9425

✔Intel Core i5-8265U

MMX is used to speed up tasks such as adjusting the contrast of an image or adjusting volume.

8.Has TrustZone

✖AMD A9-9425

✖Intel Core i5-8265U

A technology integrated into the processor to secure the device for use with features such as mobile payments and streaming video using digital rights management (DRM).

9.front-end width

Unknown. Help us by suggesting a value. (AMD A9-9425)

Unknown. Help us by suggesting a value. (Intel Core i5-8265U)

The CPU can decode more instructions per clock (IPC), meaning that the CPU performs better

Miscellaneous

1.Has integrated LTE

✖AMD A9-9425

✖Intel Core i5-8265U

The system on a chip (SoC) has an integrated LTE cellular chip. LTE is capable of downloading at faster speeds than older, 3G technology.

2.floating-point performance

0.2 TFLOPS (AMD Radeon R5)

Unknown. Help us by suggesting a value.

Floating-point performance is a measurement of the raw processing power of the GPU.

3.pixel rate

3.2 GPixel/s (AMD Radeon R5)

Unknown. Help us by suggesting a value.

The number of pixels that can be rendered to the screen every second.

4. texture rate

6.4 GTexels/s (AMD Radeon R5)

Unknown. Help us by suggesting a value.

The number of textured pixels that can be rendered to the screen every second.

Price comparison

Cancel

Which are the best CPUs?

AMD A9-9425 vs Intel Core i5-8250U: What is the difference?

44points

AMD A9-9425

49points

Intel Core i5-8250U

vs

68 facts in comparison

AMD A9-9425

Intel Core i5-8250U

Why is AMD A9-9425 better than Intel Core i5-8250U?

• 458MHz faster GPU clock speed?
  758MHzvs300MHz
• 0.3GHz higher turbo clock speed?
  3.7GHzvs3.4GHz
• 0.25MB/core more L2 cache per core?
  0.5MB/corevs0.25MB/core
• 15 higher clock multiplier?
  31vs16
• Has FMA4?

Why is Intel Core i5-8250U better than AMD A9-9425?

• 267MHz higher ram speed?
  2400MHzvs2133MHz
• 6 more CPU threads?
  8vs2
• 10°C higher maximum operating temperature?
  100°Cvs90°C
• 14nm smaller semiconductor size?
  14nmvs28nm
• 3. 83x higher PassMark result?
  5941vs1552
• 60KB bigger L1 cache?
  256KBvs196KB
• 45.68% higher PassMark result (single)?
  1939vs1331
• 1 more memory channels?
  2vs1

Which are the most popular comparisons?

AMD A9-9425

vs

Intel Core i5-8265U

Intel Core i5-8250U

vs

Intel Core i3-1115G4

AMD A9-9425

vs

Intel Core i3-7020U

Intel Core i5-8250U

vs

AMD Ryzen 5 3500U

AMD A9-9425

vs

Intel Celeron N4020

Intel Core i5-8250U

vs

Intel Core i3-1005G1

AMD A9-9425

vs

Intel Core i5-8305G

Intel Core i5-8250U

vs

AMD Ryzen 3 2200U

AMD A9-9425

vs

Intel Core i3-6006U

Intel Core i5-8250U

vs

Intel Core i7-6500U

AMD A9-9425

vs

AMD A4-9125

Intel Core i5-8250U

vs

AMD Ryzen 3 3200U

AMD A9-9425

vs

AMD Athlon Silver 3050U

Intel Core i5-8250U

vs

AMD Ryzen 5 2500U

AMD A9-9425

vs

Intel Core i5-6200U

Intel Core i5-8250U

vs

AMD Ryzen 5 5500U

AMD A9-9425

vs

AMD Athlon 300U

Intel Core i5-8250U

vs

Intel Core i7-7500U

Intel Core i5-8250U

vs

Intel Core i5-7200U

Price comparison

User reviews

Overall Rating

AMD A9-9425

7 User reviews

AMD A9-9425

6. 7/10

7 User reviews

Intel Core i5-8250U

5 User reviews

Intel Core i5-8250U

7.4/10

5 User reviews

Features

Value for money

6.7/10

7 votes

7.4/10

5 votes

Gaming

4.9/10

7 votes

6.6/10

5 votes

Performance

5.9/10

7 votes

7.4/10

5 votes

Reliability

7.0/10

7 votes

8.8/10

5 votes

Energy efficiency

7.9/10

7 votes

6.4/10

5 votes

Performance

1.CPU speed

2 x 3.1GHz

4 x 1.6GHz

The CPU speed indicates how many processing cycles per second can be executed by a CPU, considering all of its cores (processing units). It is calculated by adding the clock rates of each core or, in the case of multi-core processors employing different microarchitectures, of each group of cores.

2.CPU threads

More threads result in faster performance and better multitasking.

3.turbo clock speed

3.7GHz

3.4GHz

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 A9-9425

✖Intel Core i5-8250U

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 A9-9425)

A larger L3 cache results in faster CPU and system-wide performance.

7.L1 cache

A larger L1 cache results in faster CPU and system-wide performance.

8.L2 core

0.5MB/core

0.25MB/core

More data can be stored in the L2 cache for access by each core of the CPU.

9.L3 core

Unknown. Help us by suggesting a value. (AMD A9-9425)

1.5MB/core

More data can be stored in the L3 cache for access by each core of the CPU.

Memory

1.RAM speed

2133MHz

2400MHz

It can support faster memory, which will give quicker system performance.

2.maximum memory bandwidth

Unknown. Help us by suggesting a value. (AMD A9-9425)

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

Unknown. Help us by suggesting a value. (AMD A9-9425)

The maximum amount of memory (RAM) supported.

6.bus transfer rate

Unknown. Help us by suggesting a value. (AMD A9-9425)

The bus is responsible for transferring data between different components of a computer or device.

7.Supports ECC memory

✖AMD A9-9425

✖Intel Core i5-8250U

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 A9-9425)

Unknown. Help us by suggesting a value. (Intel Core i5-8250U)

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 A9-9425)

Unknown. Help us by suggesting a value. (Intel Core i5-8250U)

The bus is responsible for transferring data between different components of a computer or device.

Benchmarks

1.PassMark result

This benchmark measures the performance of the CPU using multiple threads.

2.PassMark result (single)

This benchmark measures the performance of the CPU using a single thread.

3.Geekbench 5 result (multi)

Geekbench 5 is a cross-platform benchmark that measures a processor’s multi-core performance. (Source: Primate Labs, 2022)

4.Cinebench R20 (multi) result

Cinebench R20 is a benchmark tool that measures a CPU’s multi-core performance by rendering a 3D scene.

5.Cinebench R20 (single) result

Cinebench R20 is a benchmark tool that measures a CPU’s single-core performance by rendering a 3D scene.

6.Geekbench 5 result (single)

Geekbench 5 is a cross-platform benchmark that measures a processor’s single-core performance. (Source: Primate Labs, 2022)

7.Blender (bmw27) result

Unknown. Help us by suggesting a value. (AMD A9-9425)

771.41seconds

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 A9-9425)

2852.02seconds

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 A9-9425

✔Intel Core i5-8250U

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 A9-9425

✔Intel Core i5-8250U

AES is used to speed up encryption and decryption.

3.Has AVX

✔AMD A9-9425

✔Intel Core i5-8250U

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 A9-9425

✔Intel Core i5-8250U

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 A9-9425)

Unknown. Help us by suggesting a value. (Intel Core i5-8250U)

NEON provides acceleration for media processing, such as listening to MP3s.

7.Has MMX

✔AMD A9-9425

✔Intel Core i5-8250U

MMX is used to speed up tasks such as adjusting the contrast of an image or adjusting volume.

8.Has TrustZone

✖AMD A9-9425

✖Intel Core i5-8250U

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 A9-9425)

Unknown. Help us by suggesting a value. (Intel Core i5-8250U)

The CPU can decode more instructions per clock (IPC), meaning that the CPU performs better

Miscellaneous

1.Has integrated LTE

✖AMD A9-9425

✖Intel Core i5-8250U

The system on a chip (SoC) has an integrated LTE cellular chip. LTE is capable of downloading at faster speeds than older, 3G technology.

2.floating-point performance

0.2 TFLOPS (AMD Radeon R5)

Unknown. Help us by suggesting a value.

Floating-point performance is a measurement of the raw processing power of the GPU.

3.pixel rate

3.2 GPixel/s (AMD Radeon R5)

Unknown. Help us by suggesting a value.

The number of pixels that can be rendered to the screen every second.

4.texture rate

6. 4 GTexels/s (AMD Radeon R5)

Unknown. Help us by suggesting a value.

The number of textured pixels that can be rendered to the screen every second.

Price comparison

Cancel

Which are the best CPUs?

AMD A9-9420 vs Intel Core i5-8250U vs AMD A9-9410

log 03. 23:47:26

#0 checking url part for id 9184 +0s … 0s

#1 checking url part for id 9206 +0s … 0s

#2 checking url part for id 8181 +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.007s … 0.008s

#6 linkCache_getLink no uid found +0.005s … 0.012s

#7 linkCache_getLink no uid found +0.003s … 0.016s

#8 linkCache_getLink using $NBC_LINKCACHE +0s … 0.016s

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

#10 linkCache_getLink using $NBC_LINKCACHE +0s … 0.016s

#11 linkCache_getLink using $NBC_LINKCACHE +0s … 0.016s

#12 linkCache_getLink using $NBC_LINKCACHE +0s … 0.016s

#13 linkCache_getLink using $NBC_LINKCACHE +0s … 0.016s

#14 linkCache_getLink using $NBC_LINKCACHE +0s … 0.016s

#15 linkCache_getLink using $NBC_LINKCACHE +0s … 0.016s

#16 linkCache_getLink using $NBC_LINKCACHE +0s … 0.016s

#17 linkCache_getLink using $NBC_LINKCACHE +0s … 0.016s

#18 linkCache_getLink using $NBC_LINKCACHE +0s … 0.016s

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

#20 composed specs +0s … 0.016s

#21 did output specs +0s … 0.016s

#22 getting avg benchmarks for device 9184 +0.001s … 0.017s

#23 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.017s

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

#25 got single benchmarks 9184 +0.013s … 0.03s

#26 linkCache_getLink using $NBC_LINKCACHE +0.005s … 0.036s

#27 getting avg benchmarks for device 9206 +0.001s … 0.036s

#28 linkCache_getLink using $NBC_LINKCACHE +0.006s … 0.042s

#29 got single benchmarks 9206 +0.242s … 0.284s

#30 getting avg benchmarks for device 8181 +0.001s … 0.285s

#31 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.285s

#32 got single benchmarks 8181 +0.009s … 0.294s

#33 got avg benchmarks for devices +0s … 0.294s

#34 linkCache_getLink no uid found +0s … 0.294s

#35 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.296s

#36 linkCache_getLink no uid found +0s … 0.296s

#37 linkCache_getLink no uid found +0.001s … 0.297s

#38 linkCache_getLink using $NBC_LINKCACHE +0s … 0.297s

#39 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.298s

#40 linkCache_getLink using $NBC_LINKCACHE +0s … 0.298s

#41 linkCache_getLink no uid found +0s … 0.298s

#42 linkCache_getLink using $NBC_LINKCACHE +0s … 0.298s

#43 linkCache_getLink using $NBC_LINKCACHE +0s … 0.298s

#44 linkCache_getLink using $NBC_LINKCACHE +0.019s … 0.317s

#45 linkCache_getLink no uid found +0s … 0.317s

#46 linkCache_getLink no uid found +0s … 0.318s

#47 linkCache_getLink no uid found +0.001s … 0.319s

#48 linkCache_getLink no uid found +0.001s … 0.32s

#49 linkCache_getLink no uid found +0s … 0.32s

#50 linkCache_getLink no uid found +0s … 0.32s

#51 linkCache_getLink no uid found +0s … 0.32s

#52 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s

#53 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.321s

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

#55 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.323s

#56 linkCache_getLink no uid found +0s … 0.323s

#57 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.324s

#58 linkCache_getLink using $NBC_LINKCACHE +0s … 0.325s

#59 linkCache_getLink using $NBC_LINKCACHE +0.482s … 0.807s

#60 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#61 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#62 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#63 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#64 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#65 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#66 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#67 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#68 linkCache_getLink using $NBC_LINKCACHE +0s … 0. 807s

#69 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#70 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#71 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#72 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#73 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#74 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#75 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#76 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#77 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#78 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#79 linkCache_getLink no uid found +0s … 0.807s

#80 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#81 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

#82 linkCache_getLink using $NBC_LINKCACHE +0s … 0.807s

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

#84 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#85 linkCache_getLink no uid found +0s … 0.808s

#86 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#87 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#88 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#89 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#90 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#91 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#92 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#93 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#94 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#95 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#96 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#97 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

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

#99 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#102 linkCache_getLink no uid found +0s … 0.808s

#103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#105 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#107 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#110 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#112 linkCache_getLink no uid found +0s … 0.808s

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

#114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#116 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#123 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#124 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#125 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#126 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#127 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.808s

#128 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#130 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#133 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#136 linkCache_getLink no uid found +0s … 0.808s

#137 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#138 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#139 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#140 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

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

#142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#143 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#144 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#147 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#148 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#149 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#150 linkCache_getLink no uid found +0s … 0.808s

#151 linkCache_getLink no uid found +0s … 0.808s

#152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#153 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#154 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#155 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

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

#157 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#158 linkCache_getLink using $NBC_LINKCACHE +0s … 0.808s

#159 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.809s

#160 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.809s

#161 linkCache_getLink using $NBC_LINKCACHE +0s … 0.809s

#162 linkCache_getLink using $NBC_LINKCACHE +0s … 0.809s

#163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#164 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#165 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#166 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#167 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#169 linkCache_getLink no uid found +0s … 0.81s

#170 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.81s

#171 linkCache_getLink no uid found +0s … 0.81s

#172 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#174 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#175 linkCache_getLink no uid found +0s … 0.81s

#176 linkCache_getLink no uid found +0s … 0.81s

#177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#179 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#180 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#181 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#182 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#183 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#184 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#185 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.81s

#186 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#187 linkCache_getLink no uid found +0s … 0.81s

#188 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#189 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#191 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#192 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#193 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#194 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#195 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#196 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#197 linkCache_getLink using $NBC_LINKCACHE +0s … 0.81s

#198 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.811s

#199 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.812s

#200 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.812s

#201 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#202 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#203 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#205 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#206 linkCache_getLink no uid found +0s … 0.812s

#207 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#208 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#209 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#210 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#211 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#212 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#213 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#214 linkCache_getLink using $NBC_LINKCACHE +0s .. . 0.812s

#215 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#216 linkCache_getLink no uid found +0s … 0.812s

#217 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#218 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#219 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#220 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#221 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#222 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#223 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#224 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#225 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#226 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#227 linkCache_getLink no uid found +0s … 0.812s

#228 linkCache_getLink no uid found +0s … 0.812s

#229 linkCache_getLink no uid found +0s . .. 0.812s

#230 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#231 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#232 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#233 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#234 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#235 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#236 linkCache_getLink using $NBC_LINKCACHE +0s … 0.812s

#237 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.813s

#238 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.814s

#239 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#240 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#241 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#242 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#243 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.814s

#244 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#245 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#246 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#247 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#248 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#249 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#250 linkCache_getLink no uid found +0s … 0.814s

#251 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#252 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#253 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#254 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#255 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#256 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#257 linkCache_getLink using $NBC_LINKCACHE +0s .. . 0.814s

#258 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#259 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#260 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#261 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#262 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#263 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#264 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#265 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#266 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#267 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#268 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#269 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#270 linkCache_getLink no uid found +0s … 0.814s

#271 linkCache_getLink no uid found +0s … 0.814s

#272 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.814s

#273 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#274 linkCache_getLink no uid found +0s … 0.814s

#275 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#276 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#277 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#278 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#279 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#280 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#281 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#282 linkCache_getLink using $NBC_LINKCACHE +0s … 0.814s

#283 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.815s

#284 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.816s

#285 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#286 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.816s

#287 linkCache_getLink no uid found +0s … 0.816s

#288 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#289 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#290 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#291 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#292 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#293 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#294 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#295 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#296 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#297 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#298 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#299 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#300 linkCache_getLink using $NBC_LINKCACHE +0s .. . 0.816s

#301 linkCache_getLink no uid found +0s … 0.816s

#302 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#303 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#304 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#305 linkCache_getLink no uid found +0s … 0.816s

#306 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#307 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#308 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#309 linkCache_getLink no uid found +0s … 0.816s

#310 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#311 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#312 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#313 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#314 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#315 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.816s

#316 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#317 linkCache_getLink using $NBC_LINKCACHE +0s … 0.816s

#318 linkCache_getLink using $NBC_LINKCACHE +0s … 0.817s

#319 linkCache_getLink using $NBC_LINKCACHE +0s … 0.817s

#320 linkCache_getLink using $NBC_LINKCACHE +0s … 0.817s

#321 linkCache_getLink using $NBC_LINKCACHE +0s … 0.817s

#322 linkCache_getLink using $NBC_LINKCACHE +0s … 0.817s

#323 linkCache_getLink using $NBC_LINKCACHE +0s … 0.817s

#324 linkCache_getLink using $NBC_LINKCACHE +0s … 0.817s

#325 linkCache_getLink using $NBC_LINKCACHE +0s … 0.817s

#326 linkCache_getLink using $NBC_LINKCACHE +0s … 0.817s

#327 linkCache_getLink using $NBC_LINKCACHE +0s … 0.817s

#328 linkCache_getLink using $NBC_LINKCACHE +0s … 0.817s

#329 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.817s

#330 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.818s

#331 linkCache_getLink using $NBC_LINKCACHE +0s … 0.818s

#332 linkCache_getLink using $NBC_LINKCACHE +0s … 0.818s

#333 linkCache_getLink using $NBC_LINKCACHE +0s … 0.818s

#334 linkCache_getLink using $NBC_LINKCACHE +0s … 0.818s

#335 linkCache_getLink using $NBC_LINKCACHE +0s … 0.818s

#336 linkCache_getLink using $NBC_LINKCACHE +0s … 0.818s

#337 linkCache_getLink using $NBC_LINKCACHE +0s … 0.818s

#338 linkCache_getLink using $NBC_LINKCACHE +0s … 0.818s

#339 linkCache_getLink using $NBC_LINKCACHE +0s … 0.818s

#340 linkCache_getLink using $NBC_LINKCACHE +0s … 0.818s

#341 linkCache_getLink using $NBC_LINKCACHE +0s … 0.818s

#342 linkCache_getLink using $NBC_LINKCACHE +0s … 0.818s

#343 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.818s

#344 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.819s

#345 linkCache_getLink using $NBC_LINKCACHE +0s … 0.82s

#346 linkCache_getLink using $NBC_LINKCACHE +0s … 0.82s

#347 linkCache_getLink using $NBC_LINKCACHE +0s … 0.82s

#348 linkCache_getLink using $NBC_LINKCACHE +0s … 0.82s

#349 linkCache_getLink using $NBC_LINKCACHE +0s … 0.82s

#350 linkCache_getLink using $NBC_LINKCACHE +0s … 0.82s

#351 linkCache_getLink using $NBC_LINKCACHE +0s … 0.82s

#352 linkCache_getLink using $NBC_LINKCACHE +0s … 0.82s

#353 linkCache_getLink using $NBC_LINKCACHE +0s … 0.82s

#354 linkCache_getLink using $NBC_LINKCACHE +0s … 0.82s

#355 linkCache_getLink using $NBC_LINKCACHE +0s … 0.82s

#356 linkCache_getLink using $NBC_LINKCACHE +0s … 0.82s

#357 linkCache_getLink using $NBC_LINKCACHE +0s .. . 0.82s

#358 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.821s

#359 linkCache_getLink using $NBC_LINKCACHE +0s … 0.821s

#360 linkCache_getLink using $NBC_LINKCACHE +0s … 0.821s

#361 linkCache_getLink using $NBC_LINKCACHE +0s … 0.821s

#362 linkCache_getLink using $NBC_LINKCACHE +0s … 0.821s

#363 linkCache_getLink using $NBC_LINKCACHE +0s … 0.821s

#364 linkCache_getLink using $NBC_LINKCACHE +0s … 0.821s

#365 linkCache_getLink using $NBC_LINKCACHE +0s … 0.821s

#366 linkCache_getLink using $NBC_LINKCACHE +0s … 0.821s

#367 linkCache_getLink no uid found +0s … 0.821s

#368 linkCache_getLink using $NBC_LINKCACHE +0s … 0.821s

#369 linkCache_getLink using $NBC_LINKCACHE +0s … 0.821s

#370 linkCache_getLink using $NBC_LINKCACHE +0s … 0.821s

#371 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.821s

#372 linkCache_getLink using $NBC_LINKCACHE +0s … 0.821s

#373 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.822s

#374 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.823s

#375 linkCache_getLink using $NBC_LINKCACHE +0s … 0.823s

#376 linkCache_getLink using $NBC_LINKCACHE +0s … 0.823s

#377 linkCache_getLink using $NBC_LINKCACHE +0s … 0.823s

#378 linkCache_getLink using $NBC_LINKCACHE +0s … 0.823s

#379 linkCache_getLink using $NBC_LINKCACHE +0s … 0.823s

#380 linkCache_getLink using $NBC_LINKCACHE +0s … 0.823s

#381 linkCache_getLink using $NBC_LINKCACHE +0s … 0.823s

#382 linkCache_getLink no uid found +0s … 0.823s

#383 linkCache_getLink using $NBC_LINKCACHE +0s … 0.823s

#384 linkCache_getLink using $NBC_LINKCACHE +0s … 0.823s

#385 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.823s

#386 linkCache_getLink using $NBC_LINKCACHE +0s … 0.823s

#387 linkCache_getLink using $NBC_LINKCACHE +0s … 0.823s

#388 linkCache_getLink using $NBC_LINKCACHE +0s … 0.823s

#389 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.824s

#390 linkCache_getLink no uid found +0.001s … 0.825s

#391 linkCache_getLink using $NBC_LINKCACHE +0s … 0.825s

#392 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.827s

#393 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.828s

#394 linkCache_getLink using $NBC_LINKCACHE +0s … 0.828s

#395 linkCache_getLink using $NBC_LINKCACHE +0s … 0.828s

#396 linkCache_getLink no uid found +0s … 0.828s

#397 linkCache_getLink using $NBC_LINKCACHE +0s … 0.828s

#398 linkCache_getLink using $NBC_LINKCACHE +0s … 0.828s

#399 linkCache_getLink no uid found +0.002s . .. 0.83s

#400 linkCache_getLink using $NBC_LINKCACHE +0s … 0.83s

#401 linkCache_getLink using $NBC_LINKCACHE +0s … 0.83s

#402 linkCache_getLink using $NBC_LINKCACHE +0s … 0.83s

#403 linkCache_getLink using $NBC_LINKCACHE +0s … 0.83s

#404 linkCache_getLink using $NBC_LINKCACHE +0s … 0.83s

#405 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.831s

#406 linkCache_getLink using $NBC_LINKCACHE +0s … 0.831s

#407 linkCache_getLink no uid found +0s … 0.831s

#408 linkCache_getLink using $NBC_LINKCACHE +0s … 0.831s

#409 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.832s

#410 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.833s

#411 linkCache_getLink no uid found +0s … 0.833s

#412 linkCache_getLink using $NBC_LINKCACHE +0s … 0.833s

#413 linkCache_getLink using $NBC_LINKCACHE +0s … 0. 833s

#414 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.834s

#415 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.834s

#416 linkCache_getLink using $NBC_LINKCACHE +0s … 0.834s

#417 linkCache_getLink using $NBC_LINKCACHE +0s … 0.834s

#418 linkCache_getLink no uid found +0s … 0.834s

#419 linkCache_getLink using $NBC_LINKCACHE +0s … 0.835s

#420 linkCache_getLink using $NBC_LINKCACHE +0s … 0.835s

#421 linkCache_getLink using $NBC_LINKCACHE +0s … 0.835s

#422 linkCache_getLink using $NBC_LINKCACHE +0s … 0.835s

#423 linkCache_getLink using $NBC_LINKCACHE +0.064s … 0.898s

#424 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.899s

#425 linkCache_getLink using $NBC_LINKCACHE +0s … 0.899s

#426 linkCache_getLink using $NBC_LINKCACHE +0s … 0.899s

#427 linkCache_getLink no uid found +0s . .. 0.899s

#428 linkCache_getLink using $NBC_LINKCACHE +0s … 0.899s

#429 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.899s

#430 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.9s

#431 linkCache_getLink using $NBC_LINKCACHE +0s … 0.901s

#432 linkCache_getLink using $NBC_LINKCACHE +0s … 0.901s

#433 linkCache_getLink no uid found +0s … 0.901s

#434 linkCache_getLink using $NBC_LINKCACHE +0s … 0.901s

#435 linkCache_getLink using $NBC_LINKCACHE +0s … 0.901s

#436 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.901s

#437 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.903s

#438 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s

#439 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s

#440 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s

#441 linkCache_getLink no uid found +0s . .. 0.903s

#442 linkCache_getLink using $NBC_LINKCACHE +0s … 0.903s

#443 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.904s

#444 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.905s

#445 linkCache_getLink using $NBC_LINKCACHE +0s … 0.905s

#446 linkCache_getLink using $NBC_LINKCACHE +0s … 0.905s

#447 linkCache_getLink no uid found +0s … 0.905s

#448 linkCache_getLink using $NBC_LINKCACHE +0s … 0.905s

#449 linkCache_getLink using $NBC_LINKCACHE +0s … 0.905s

#450 linkCache_getLink using $NBC_LINKCACHE +0s … 0.905s

#451 linkCache_getLink using $NBC_LINKCACHE +0s … 0.905s

#452 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.907s

#453 linkCache_getLink using $NBC_LINKCACHE +0s … 0.907s

#454 linkCache_getLink no uid found +0s … 0.907s

#455 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.907s

#456 linkCache_getLink no uid found +0.002s … 0.909s

#457 linkCache_getLink using $NBC_LINKCACHE +0s … 0.909s

#458 linkCache_getLink using $NBC_LINKCACHE +0s … 0.909s

#459 linkCache_getLink no uid found +0s … 0.909s

#460 linkCache_getLink using $NBC_LINKCACHE +0s … 0.909s

#461 linkCache_getLink using $NBC_LINKCACHE +0s … 0.909s

#462 linkCache_getLink using $NBC_LINKCACHE +0s … 0.909s

#463 linkCache_getLink using $NBC_LINKCACHE +0s … 0.909s

#464 linkCache_getLink using $NBC_LINKCACHE +0s … 0.909s

#465 linkCache_getLink using $NBC_LINKCACHE +0s … 0.909s

#466 linkCache_getLink no uid found +0s … 0.909s

#467 linkCache_getLink using $NBC_LINKCACHE +0s … 0.909s

#468 linkCache_getLink using $NBC_LINKCACHE +0s … 0.909s

#469 linkCache_getLink using $NBC_LINKCACHE +0s … 0.909s

#470 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.91s

#471 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.912s

#472 linkCache_getLink using $NBC_LINKCACHE +0s … 0.912s

#473 linkCache_getLink no uid found +0s … 0.912s

#474 linkCache_getLink using $NBC_LINKCACHE +0s … 0.912s

#475 linkCache_getLink using $NBC_LINKCACHE +0s … 0.912s

#476 linkCache_getLink using $NBC_LINKCACHE +0s … 0.912s

#477 linkCache_getLink using $NBC_LINKCACHE +0s … 0.912s

#478 linkCache_getLink using $NBC_LINKCACHE +0s … 0.912s

#479 linkCache_getLink using $NBC_LINKCACHE +0s … 0.912s

#480 linkCache_getLink using $NBC_LINKCACHE +0s … 0.912s

#481 linkCache_getLink using $NBC_LINKCACHE +0s … 0.912s

#482 linkCache_getLink using $NBC_LINKCACHE +0s … 0.912s

#483 linkCache_getLink using $NBC_LINKCACHE +0s … 0.912s

#484 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.913s

#485 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.914s

#486 linkCache_getLink using $NBC_LINKCACHE +0s … 0.914s

#487 linkCache_getLink no uid found +0s … 0.915s

#488 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s

#489 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s

#490 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s

#491 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s

#492 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s

#493 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s

#494 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s

#495 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s

#496 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s

#497 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s

#498 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.916s

#499 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.917s

#500 linkCache_getLink using $NBC_LINKCACHE +0s … 0.917s

#501 linkCache_getLink using $NBC_LINKCACHE +0s … 0.917s

#502 linkCache_getLink using $NBC_LINKCACHE +0s … 0.917s

#503 linkCache_getLink using $NBC_LINKCACHE +0s … 0.917s

#504 linkCache_getLink no uid found +0s … 0.917s

#505 linkCache_getLink using $NBC_LINKCACHE +0s … 0.917s

#506 linkCache_getLink using $NBC_LINKCACHE +0s … 0.917s

#507 linkCache_getLink using $NBC_LINKCACHE +0s … 0.917s

#508 linkCache_getLink using $NBC_LINKCACHE +0s … 0.917s

#509 linkCache_getLink using $NBC_LINKCACHE +0s … 0.917s

#510 linkCache_getLink using $NBC_LINKCACHE +0s … 0.917s

#511 linkCache_getLink using $NBC_LINKCACHE +0s … 0.917s

#512 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.918s

#513 linkCache_getLink no uid found +0.001s … 0.92s

#514 linkCache_getLink using $NBC_LINKCACHE +0s … 0.92s

#515 linkCache_getLink no uid found +0s … 0.92s

#516 linkCache_getLink using $NBC_LINKCACHE +0s … 0.92s

#517 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.92s

#518 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.921s

#519 linkCache_getLink using $NBC_LINKCACHE +0s … 0.921s

#520 linkCache_getLink using $NBC_LINKCACHE +0s … 0.921s

#521 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#522 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#523 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#524 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#525 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#526 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.922s

#527 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#528 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#529 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#530 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#531 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#532 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#533 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#534 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#535 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#536 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#537 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#538 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#539 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#540 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.922s

#541 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#542 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#543 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#544 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#545 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#546 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#547 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#548 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#549 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#550 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#551 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#552 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#553 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#554 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.922s

#555 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#556 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#557 linkCache_getLink no uid found +0s … 0.922s

#558 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#559 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#560 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#561 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#562 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#563 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#564 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#565 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#566 linkCache_getLink no uid found +0s … 0.922s

#567 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#568 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#569 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.922s

#570 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#571 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#572 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#573 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#574 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#575 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#576 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#577 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#578 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#579 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#580 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#581 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#582 linkCache_getLink no uid found +0s … 0.922s

#583 linkCache_getLink using $NBC_LINKCACHE +0s .. . 0.922s

#584 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#585 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#586 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#587 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#588 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#589 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#590 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#591 linkCache_getLink no uid found +0s … 0.922s

#592 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#593 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#594 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#595 linkCache_getLink using $NBC_LINKCACHE +0s … 0.922s

#596 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#597 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#598 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#599 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#600 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#601 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#602 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#603 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#604 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#605 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#606 linkCache_getLink no uid found +0s … 0.923s

#607 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#608 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#609 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#610 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#611 linkCache_getLink using $NBC_LINKCACHE +0s … 0. 923s

#612 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#613 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#614 linkCache_getLink no uid found +0s … 0.923s

#615 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#616 linkCache_getLink using $NBC_LINKCACHE +0s … 0.923s

#617 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.923s

#618 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.925s

#619 linkCache_getLink no uid found +0s … 0.925s

#620 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#621 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#622 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#623 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#624 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#625 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#626 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.925s

#627 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#628 linkCache_getLink no uid found +0s … 0.925s

#629 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#630 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#631 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#632 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#633 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#634 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#635 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#636 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#637 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#638 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#639 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#640 linkCache_getLink using $NBC_LINKCACHE +0s .. . 0.925s

#641 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#642 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#643 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#644 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#645 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#646 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#647 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#648 linkCache_getLink using $NBC_LINKCACHE +0s … 0.925s

#649 linkCache_getLink no uid found +0s … 0.925s

#650 linkCache_getLink no uid found +0s … 0.925s

#651 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.926s

#652 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.928s

#653 linkCache_getLink no uid found +0s … 0.928s

#654 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#655 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.928s

#656 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#657 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#658 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#659 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#660 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#661 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#662 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#663 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#664 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#665 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#666 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#667 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#668 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#669 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.928s

#670 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#671 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#672 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#673 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#674 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#675 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#676 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#677 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#678 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#679 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#680 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s

#681 linkCache_getLink no uid found +0s … 0.928s

#682 linkCache_getLink no uid found +0s … 0.928s

#683 linkCache_getLink using $NBC_LINKCACHE +0s … 0.929s

#684 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.93s

#685 linkCache_getLink using $NBC_LINKCACHE +0s … 0.93s

#686 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#687 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#688 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#689 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#690 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#691 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#692 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#693 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#694 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#695 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#696 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#697 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#698 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.931s

#699 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#700 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#701 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#702 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#703 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#704 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#705 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#706 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#707 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#708 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#709 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#710 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#711 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#712 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.931s

#713 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#714 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#715 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#716 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#717 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#718 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#719 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#720 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#721 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#722 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#723 linkCache_getLink no uid found +0s … 0.931s

#724 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#725 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#726 linkCache_getLink using $NBC_LINKCACHE +0s .. . 0.931s

#727 linkCache_getLink no uid found +0s … 0.931s

#728 linkCache_getLink no uid found +0s … 0.931s

#729 linkCache_getLink using $NBC_LINKCACHE +0s … 0.931s

#730 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.932s

#731 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.933s

#732 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#733 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#734 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#735 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#736 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#737 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#738 linkCache_getLink no uid found +0s … 0.933s

#739 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#740 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#741 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.933s

#742 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#743 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#744 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#745 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#746 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#747 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#748 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#749 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#750 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#751 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#752 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#753 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#754 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#755 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.933s

#756 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#757 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#758 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#759 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#760 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#761 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#762 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#763 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#764 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#765 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#766 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#767 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#768 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#769 linkCache_getLink no uid found +0s .. . 0.933s

#770 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#771 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#772 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#773 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#774 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s

#775 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#776 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#777 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#778 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#779 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#780 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#781 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#782 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#783 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.934s

#784 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#785 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#786 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#787 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#788 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#789 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#790 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#791 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#792 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#793 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#794 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#795 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#796 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#797 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.934s

#798 linkCache_getLink no uid found +0s … 0.934s

#799 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#800 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#801 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#802 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#803 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#804 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#805 linkCache_getLink no uid found +0s … 0.934s

#806 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#807 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#808 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#809 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#810 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#811 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#812 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.934s

#813 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#814 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#815 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#816 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#817 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s

#818 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.934s

#819 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.936s

#820 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#821 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#822 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#823 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#824 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#825 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#826 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.936s

#827 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#828 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#829 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#830 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#831 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#832 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#833 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#834 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#835 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#836 linkCache_getLink no uid found +0s … 0.936s

#837 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#838 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#839 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#840 linkCache_getLink using $NBC_LINKCACHE +0s .. . 0.936s

#841 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#842 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#843 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#844 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#845 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#846 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#847 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#848 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#849 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#850 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#851 linkCache_getLink no uid found +0s … 0.936s

#852 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#853 linkCache_getLink no uid found +0s … 0.936s

#854 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#855 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.936s

#856 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#857 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#858 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#859 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#860 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#861 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#862 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#863 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#864 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#865 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#866 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#867 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#868 linkCache_getLink using $NBC_LINKCACHE +0s … 0.936s

#869 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.937s

#870 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#871 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#872 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#873 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#874 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#875 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#876 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#877 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#878 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#879 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#880 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#881 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#882 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#883 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.937s

#884 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#885 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#886 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#887 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#888 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#889 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#890 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#891 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#892 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#893 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#894 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#895 linkCache_getLink no uid found +0s … 0.937s

#896 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#897 linkCache_getLink no uid found +0s … 0.937s

#898 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.937s

#899 linkCache_getLink no uid found +0s … 0.937s

#900 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#901 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#902 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#903 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s

#904 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.937s

#905 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.939s

#906 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#907 linkCache_getLink no uid found +0s … 0.939s

#908 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#909 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#910 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#911 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#912 linkCache_getLink using $NBC_LINKCACHE +0s .. . 0.939s

#913 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#914 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#915 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#916 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#917 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#918 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#919 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#920 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#921 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#922 linkCache_getLink no uid found +0s … 0.939s

#923 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#924 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#925 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#926 linkCache_getLink no uid found +0s … 0.939s

#927 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.939s

#928 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#929 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#930 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#931 linkCache_getLink using $NBC_LINKCACHE +0s … 0.939s

#932 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.942s

#933 linkCache_getLink using $NBC_LINKCACHE +0s … 0.942s

#934 linkCache_getLink using $NBC_LINKCACHE +0s … 0.942s

#935 linkCache_getLink no uid found +0s … 0.942s

#936 linkCache_getLink using $NBC_LINKCACHE +0s … 0.942s

#937 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.943s

#938 linkCache_getLink using $NBC_LINKCACHE +0s … 0.943s

#939 linkCache_getLink using $NBC_LINKCACHE +0s … 0.943s

#940 linkCache_getLink using $NBC_LINKCACHE +0s … 0.943s

#941 linkCache_getLink no uid found +0s .. . 0.943s

#942 linkCache_getLink no uid found +0.002s … 0.945s

#943 linkCache_getLink using $NBC_LINKCACHE +0s … 0.945s

#944 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.947s

#945 linkCache_getLink no uid found +0s … 0.947s

#946 linkCache_getLink no uid found +0.002s … 0.949s

#947 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#948 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#949 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#950 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#951 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#952 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#953 linkCache_getLink no uid found +0s … 0.949s

#954 linkCache_getLink no uid found +0s … 0.949s

#955 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#956 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.949s

#957 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#958 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#959 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#960 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#961 linkCache_getLink no uid found +0s … 0.949s

#962 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#963 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#964 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#965 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#966 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#967 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#968 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#969 linkCache_getLink using $NBC_LINKCACHE +0s … 0.949s

#970 linkCache_getLink using $NBC_LINKCACHE +0s .. . 0.949s

#971 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.951s

#972 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#973 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#974 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#975 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#976 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#977 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#978 linkCache_getLink no uid found +0s … 0.951s

#979 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#980 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#981 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#982 linkCache_getLink no uid found +0s … 0.951s

#983 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#984 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#985 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.951s

#986 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#987 linkCache_getLink no uid found +0s … 0.951s

#988 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#989 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#990 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#991 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#992 linkCache_getLink no uid found +0s … 0.951s

#993 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#994 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#995 linkCache_getLink using $NBC_LINKCACHE +0s … 0.951s

#996 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.952s

#997 linkCache_getLink using $NBC_LINKCACHE +0s … 0.952s

#998 linkCache_getLink using $NBC_LINKCACHE +0s … 0.953s

#999 linkCache_getLink no uid found +0s … 0.953s

#1000 linkCache_getLink no uid found +0s . .. 0.953s

#1001 linkCache_getLink using $NBC_LINKCACHE +0s … 0.953s

#1002 linkCache_getLink using $NBC_LINKCACHE +0s … 0.953s

#1003 linkCache_getLink using $NBC_LINKCACHE +0s … 0.953s

#1004 linkCache_getLink using $NBC_LINKCACHE +0s … 0.953s

#1005 linkCache_getLink using $NBC_LINKCACHE +0s … 0.953s

#1006 linkCache_getLink using $NBC_LINKCACHE +0s … 0.953s

#1007 linkCache_getLink using $NBC_LINKCACHE +0s … 0.953s

#1008 linkCache_getLink using $NBC_LINKCACHE +0s … 0.953s

#1009 linkCache_getLink using $NBC_LINKCACHE +0s … 0.953s

#1010 linkCache_getLink using $NBC_LINKCACHE +0s … 0.953s

#1011 linkCache_getLink using $NBC_LINKCACHE +0s … 0.953s

#1012 linkCache_getLink using $NBC_LINKCACHE +0s … 0.953s

#1013 linkCache_getLink using $NBC_LINKCACHE +0s … 0.953s

#1014 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.953s

#1015 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.954s

#1016 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.955s

#1017 linkCache_getLink using $NBC_LINKCACHE +0s … 0.955s

#1018 linkCache_getLink using $NBC_LINKCACHE +0s … 0.955s

#1019 linkCache_getLink using $NBC_LINKCACHE +0s … 0.955s

#1020 linkCache_getLink using $NBC_LINKCACHE +0s … 0.955s

#1021 linkCache_getLink no uid found +0s … 0.955s

#1022 linkCache_getLink using $NBC_LINKCACHE +0s … 0.955s

#1023 linkCache_getLink using $NBC_LINKCACHE +0s … 0.955s

#1024 linkCache_getLink no uid found +0s … 0.955s

#1025 linkCache_getLink using $NBC_LINKCACHE +0s … 0.955s

#1026 linkCache_getLink using $NBC_LINKCACHE +0s … 0.955s

#1027 linkCache_getLink using $NBC_LINKCACHE +0s … 0.955s

#1028 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.955s

#1029 linkCache_getLink using $NBC_LINKCACHE +0s … 0.955s

#1030 linkCache_getLink using $NBC_LINKCACHE +0s … 0.955s

#1031 linkCache_getLink using $NBC_LINKCACHE +0s … 0.955s

#1032 linkCache_getLink using $NBC_LINKCACHE +0s … 0.955s

#1033 linkCache_getLink using $NBC_LINKCACHE +0s … 0.955s

#1034 linkCache_getLink using $NBC_LINKCACHE +0s … 0.955s

#1035 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.956s

#1036 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.958s

#1037 linkCache_getLink using $NBC_LINKCACHE +0s … 0.958s

#1038 linkCache_getLink using $NBC_LINKCACHE +0s … 0.958s

#1039 linkCache_getLink using $NBC_LINKCACHE +0s … 0.958s

#1040 linkCache_getLink using $NBC_LINKCACHE +0s … 0.958s

#1041 linkCache_getLink using $NBC_LINKCACHE +0s … 0.958s

#1042 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.958s

#1043 linkCache_getLink using $NBC_LINKCACHE +0s … 0.958s

#1044 linkCache_getLink using $NBC_LINKCACHE +0s … 0.958s

#1045 linkCache_getLink using $NBC_LINKCACHE +0s … 0.958s

#1046 linkCache_getLink using $NBC_LINKCACHE +0s … 0.958s

#1047 linkCache_getLink using $NBC_LINKCACHE +0s … 0.958s

#1048 linkCache_getLink no uid found +0s … 0.958s

#1049 linkCache_getLink no uid found +0s … 0.958s

#1050 linkCache_getLink using $NBC_LINKCACHE +0s … 0.958s

#1051 linkCache_getLink using $NBC_LINKCACHE +0s … 0.958s

#1052 linkCache_getLink using $NBC_LINKCACHE +0s … 0.958s

#1053 linkCache_getLink using $NBC_LINKCACHE +0s … 0.958s

#1054 linkCache_getLink using $NBC_LINKCACHE +0s … 0.958s

#1055 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.96s

#1056 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.96s

#1057 linkCache_getLink no uid found +0s … 0.96s

#1058 linkCache_getLink using $NBC_LINKCACHE +0s … 0.96s

#1059 linkCache_getLink using $NBC_LINKCACHE +0s … 0.96s

#1060 linkCache_getLink using $NBC_LINKCACHE +0s … 0.96s

#1061 linkCache_getLink using $NBC_LINKCACHE +0s … 0.96s

#1062 linkCache_getLink using $NBC_LINKCACHE +0s … 0.96s

#1063 linkCache_getLink no uid found +0s … 0.96s

#1064 linkCache_getLink using $NBC_LINKCACHE +0s … 0.96s

#1065 linkCache_getLink using $NBC_LINKCACHE +0s … 0.96s

#1066 linkCache_getLink using $NBC_LINKCACHE +0s … 0.96s

#1067 linkCache_getLink using $NBC_LINKCACHE +0s … 0.96s

#1068 linkCache_getLink using $NBC_LINKCACHE +0s … 0.96s

#1069 linkCache_getLink using $NBC_LINKCACHE +0s … 0.96s

#1070 linkCache_getLink using $NBC_LINKCACHE +0s … 0.96s

#1071 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.96s

#1072 linkCache_getLink using $NBC_LINKCACHE +0s … 0.96s

#1073 linkCache_getLink using $NBC_LINKCACHE +0s … 0.96s

#1074 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.962s

#1075 linkCache_getLink using $NBC_LINKCACHE +0s … 0.962s

#1076 linkCache_getLink using $NBC_LINKCACHE +0s … 0.962s

#1077 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.963s

#1078 linkCache_getLink using $NBC_LINKCACHE +0s … 0.963s

#1079 linkCache_getLink using $NBC_LINKCACHE +0s … 0.964s

#1080 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.965s

#1081 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.967s

#1082 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.968s

#1083 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.969s

#1084 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.971s

#1085 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.972s

#1086 linkCache_getLink using $NBC_LINKCACHE +0s … 0.972s

#1087 linkCache_getLink using $NBC_LINKCACHE +0s … 0.972s

#1088 linkCache_getLink using $NBC_LINKCACHE +0s … 0.972s

#1089 linkCache_getLink using $NBC_LINKCACHE +0s … 0.972s

#1090 linkCache_getLink using $NBC_LINKCACHE +0s … 0.972s

#1091 linkCache_getLink no uid found +0s … 0.972s

#1092 linkCache_getLink using $NBC_LINKCACHE +0s … 0.972s

#1093 linkCache_getLink using $NBC_LINKCACHE +0s … 0.972s

#1094 linkCache_getLink no uid found +0s … 0.972s

#1095 linkCache_getLink using $NBC_LINKCACHE +0s … 0.972s

#1096 linkCache_getLink using $NBC_LINKCACHE +0s … 0.972s

#1097 linkCache_getLink using $NBC_LINKCACHE +0s … 0.972s

#1098 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1099 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.973s

#1100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1105 linkCache_getLink no uid found +0s … 0.973s

#1106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1107 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1110 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1113 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.973s

#1114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1116 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1123 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1124 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1125 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1126 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1127 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.973s

#1128 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1130 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1133 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1134 linkCache_getLink no uid found +0s … 0.973s

#1135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1137 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1138 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1139 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1140 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1141 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.973s

#1142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1143 linkCache_getLink using $NBC_LINKCACHE +0s … 0.973s

#1144 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.974s

#1145 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.975s

#1146 linkCache_getLink no uid found +0s … 0.975s

#1147 linkCache_getLink no uid found +0s … 0.975s

#1148 linkCache_getLink using $NBC_LINKCACHE +0s … 0.975s

#1149 linkCache_getLink using $NBC_LINKCACHE +0s … 0.975s

#1150 linkCache_getLink using $NBC_LINKCACHE +0s … 0.975s

#1151 linkCache_getLink using $NBC_LINKCACHE +0s … 0.975s

#1152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.975s

#1153 linkCache_getLink using $NBC_LINKCACHE +0s … 0.975s

#1154 linkCache_getLink using $NBC_LINKCACHE +0s … 0.975s

#1155 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.975s

#1156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.975s

#1157 linkCache_getLink using $NBC_LINKCACHE +0s … 0.975s

#1158 linkCache_getLink using $NBC_LINKCACHE +0s … 0.975s

#1159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.976s

#1160 linkCache_getLink using $NBC_LINKCACHE +0s … 0.976s

#1161 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.977s

#1162 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.979s

#1163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1164 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1165 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1166 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1167 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1169 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.979s

#1170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1171 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1172 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1174 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1175 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1176 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1179 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1180 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1181 linkCache_getLink no uid found +0s … 0.979s

#1182 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1183 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.979s

#1184 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1185 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1186 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1187 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1188 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1189 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1191 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1192 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1193 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1194 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1195 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1196 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1197 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.979s

#1198 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1199 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1200 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1201 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1202 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1203 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1205 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1206 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1207 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1208 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1209 linkCache_getLink no uid found +0s … 0.979s

#1210 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1211 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.979s

#1212 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1213 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1214 linkCache_getLink no uid found +0s … 0.979s

#1215 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1217 linkCache_getLink using $NBC_LINKCACHE +0s … 0.979s

#1218 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.981s

#1219 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.983s

#1220 linkCache_getLink using $NBC_LINKCACHE +0s … 0.983s

#1221 linkCache_getLink no uid found +0s … 0.983s

#1222 linkCache_getLink using $NBC_LINKCACHE +0s … 0.983s

#1223 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.985s

#1224 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.987s

#1225 linkCache_getLink no uid found +0s . .. 0.987s

#1226 linkCache_getLink using $NBC_LINKCACHE +0s … 0.987s

#1227 linkCache_getLink using $NBC_LINKCACHE +0s … 0.987s

#1228 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.988s

#1229 linkCache_getLink no uid found +0s … 0.988s

#1230 linkCache_getLink using $NBC_LINKCACHE +0s … 0.988s

#1231 linkCache_getLink using $NBC_LINKCACHE +0s … 0.988s

#1232 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.991s

#1233 linkCache_getLink using $NBC_LINKCACHE +0s … 0.991s

#1234 linkCache_getLink no uid found +0s … 0.991s

#1235 linkCache_getLink using $NBC_LINKCACHE +0s … 0.991s

#1236 min, max, avg, median took s +0.001s … 0.992s

#1237 return log +0.001s … 0.993s

AMD A9-9425 vs Intel Core i5-650

AMD A9-9425 vs Intel Core i5-650

Comparison of the technical characteristics between the processors, with the AMD A9-9425 on one side and the Intel Core i5-650 on the other side. The first is dedicated to the notebook sector, It has 2 cores, 2 threads, a maximum frequency of 3,7GHz. The second is used on the desktop segment, it has a total of 2 cores, 4 threads, its turbo frequency is set to 3,5 GHz. The following table also compares the lithography, the number of transistors (if indicated), the amount of cache memory, the maximum RAM memory capacity, the type of memory accepted, the release date, the maximum number of PCIe lanes, the values ​​obtained in Geekbench 4 and Cinebench R15.

Note: Commissions may be earned from the links above.

This page contains references to products from one or more of our advertisers. We may receive compensation when you click on links to those products. For an explanation of our advertising policy, please visit this page.

Specifications:

Processor		AMD A9-9425				Intel Core i5-650
Market (main)		Notebook				Desktop
ISA		x86-64 (64 bit)				x86-64 (64 bit)
Microarchitecture		Excavator				Westmere
Core name		Stoney Ridge				Clarkdale
Family		A9-9000				Core i5-600
Part number(s), S-Spec		AM9425AYN23AC				BX80616I5650, BXC80616I5650, CM80616003174AH, Q3GN, Q4DC, SLBLK, SLBTJ
Release date		Q1 2016				Q1 2010
Lithography		28 nm				32 nm
Transistors		1. 200.000.000				382.000.000
Cores		2				2
Threads		2				4
Base frequency		3,1 GHz				3,2 GHz
Turbo frequency		3,7 GHz				3,5 GHz
Cache memory		1 MB				4 MB
Max memory capacity		8 GB				16,38 GB
Memory types		DDR4-2133				DDR3 1066/1333
Max # of memory channels		1				2
Max PCIe lanes		8				16
TDP		15 W				73 W
Suggested PSU		—				600W ATX Power Supply
GPU integrated graphics		AMD Radeon R5 Mobile Graphics (Stoney)				Intel HD Graphics (Westmere)
GPU cores		3				—
GPU execution units		—				12
GPU shading units		192				96
GPU base clock		200 MHz				733 MHz
GPU boost clock		800 MHz				733 MHz
GPU FP32 floating point		325,2 GFLOPS				102,3 GFLOPS
Socket		BGA				LGA1156
Compatible motherboard		—				Socket LGA 1156 Motherboard
Maximum temperature		90°C				72. 6°C
Crypto engine		—				AES New Instructions
Security		—				Trusted Execution Technology, Execute Disable Bit
CPU-Z single thread		196				255
CPU-Z multi thread		351				718
Cinebench R15 single thread		120				102
Cinebench R15 multi-thread		360				239
PassMark single thread		1.342				1.371
PassMark CPU Mark		1. 538				2.174
(Windows 64-bit) Geekbench 4 single core		3.628				2.433
(Windows 64-bit) Geekbench 4 multi-core		7.137				4.805
(Windows) Geekbench 5 single core		419				528
(Windows) Geekbench 5 multi-core		666				1.170
(SGEMM) GFLOPS performance		88,06 GFLOPS				34 GFLOPS
(Multi-core / watt performance) Performance / watt ratio		476 pts / W				66 pts / W
Amazon
eBay

Note: Commissions may be earned from the links above.

We can better compare what are the technical differences between the two processors.

Suggested PSU: We assume that we have An ATX computer case, a high end graphics card, 16GB RAM, a 512GB SSD, a 1TB HDD hard drive, a Blu-Ray drive. We will have to rely on a more powerful power supply if we want to have several graphics cards, several monitors, more memory, etc.

Price: For technical reasons, we cannot currently display a price less than 24 hours, or a real-time price. This is why we prefer for the moment not to show a price. You should refer to the respective online stores for the latest price, as well as availability.

We see that the two processors have an equivalent number of cores, the maximum frequency of AMD A9-9425 is greater, that the PDT of AMD A9-9425 is lower. The AMD A9-9425 was designed earlier.

Performances :

Performance comparison between the two processors, for this we consider the results generated on benchmark software such as Geekbench 4.

	CPU-Z — Multi-thread & single thread score
Intel Core i5-650	255 718
AMD A9-9425	196 351

In single core, the difference is 30%. In multi-core, the difference in terms of gap is 105%.

Note: Commissions may be earned from the links above. These scores are only an
average of the performances got with these processors, you may get different results.

CPU-Z is a system information software that provides the name of the processor, its model number, the codename, the cache levels, the package, the process. It can also gives data about the mainboard, the memory. It makes real time measurement, with finally a benchmark for the single thread, as well as for the multi thread.

	Cinebench R15 — Multi-thread & single thread score
AMD A9-9425	120 360
Intel Core i5-650	102 239

In single core, the difference is 18%. In multi-core, the differential gap is 51%.

Note: Commissions may be earned from the links above. These scores are only an
average of the performances got with these processors, you may get different results.

Cinebench R15 evaluates the performance of CPU calculations by restoring a photorealistic 3D scene. The scene has 2,000 objects, 300,000 polygons, uses sharp and fuzzy reflections, bright areas, shadows, procedural shaders, antialiasing, and so on. The faster the rendering of the scene is created, the more powerful the PC is, with a high number of points.

	PassMark — CPU Mark & single thread
Intel Core i5-650	1.371 2.174
AMD A9-9425	1.342 1.538

In single core, the difference is 2%. In multi-core, the difference in terms of gap is 41%.

Note: Commissions may be earned from the links above. These scores are only an
average of the performances got with these processors, you may get different results.

PassMark is a benchmarking software that performs several performance tests including prime numbers, integers, floating point, compression, physics, extended instructions, encoding, sorting. The higher the score is, the higher is the device capacity.

On Windows 64-bit:

	Geekbench 4 — Multi-core & single core score — Windows 64-bit
AMD A9-9425	3.628 7.137
Intel Core i5-650	2.433 4.805

In single core, the difference is 49%. In multi-core, the differential gap is 49%.

On Linux 64-bit:

	Geekbench 4 — Multi-core & single core score — Linux 64-bit
AMD A9-9425	3. 740 6.747
Intel Core i5-650	2.560 4.761

In single core, the difference is 46%. In multi-core, the differential gap is 42%.

On Mac OS X 64-bit:

	Geekbench 4 — Multi-core & single core score — Mac OS X 64-bit
AMD A9-9425	4.681 9.717
Intel Core i5-650	2.096 4.170

In single core, the difference is 123%. In multi-core, the differential gap is 133%.

Note: Commissions may be earned from the links above. These scores are only an
average of the performances got with these processors, you may get different results.

Geekbench 4 is a complete benchmark platform with several types of tests, including data compression, images, AES encryption, SQL encoding, HTML, PDF file rendering, matrix computation, Fast Fourier Transform, 3D object simulation, photo editing, memory testing. This allows us to better visualize the respective power of these devices. For each result, we took an average of 250 values on the famous benchmark software.

On Windows:

	Geekbench 5 — Multi-core & single core score — Windows
Intel Core i5-650	528 1.170
AMD A9-9425	419 666

In single core, the difference is 26%. In multi-core, the difference in terms of gap is 76%.

On Linux:

	Geekbench 5 — Multi-core & single core score — Linux
Intel Core i5-650	530 1.180
AMD A9-9425	396 482

In single core, the difference is 34%. In multi-core, the difference in terms of gap is 145%.

Note: Commissions may be earned from the links above. These scores are only an
average of the performances got with these processors, you may get different results.

Geekbench 5 is a software for measuring the performance of a computer system, for fixed devices, mobile devices, servers. This platform makes it possible to better compare the power of the CPU, the computing power and to compare it with similar or totally different systems. Geekbench 5 includes new workloads that represent work tasks and applications that we can find in reality.

Equivalence:

AMD A9-9425 Intel equivalentIntel Core i5-650 AMD equivalent

See also:

AMD A9-9420AMD A9-9420e

Intel Core i5-6500Intel Core i5-6500T

Intel Core i5-5675R vs AMD A9-9425

Comparative analysis of Intel Core i5-5675R and AMD A9-9425 processors for all known characteristics in the following categories: Essentials, Performance, Memory, Graphics, Graphics interfaces, Graphics image quality, Graphics API support, Compatibility, Peripherals, Security & Reliability, Advanced Technologies, Virtualization.
Benchmark processor performance analysis: PassMark — Single thread mark, PassMark — CPU mark, Geekbench 4 — Single Core, Geekbench 4 — Multi-Core, GFXBench 4.0 — Car Chase Offscreen (Frames), GFXBench 4.0 — Manhattan (Frames), GFXBench 4.0 — T-Rex (Frames), GFXBench 4.0 — Car Chase Offscreen (Fps), GFXBench 4.0 — Manhattan (Fps), GFXBench 4.0 — T-Rex (Fps), CompuBench 1.5 Desktop — Face Detection (mPixels/s), CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s), CompuBench 1.5 Desktop — T-Rex (Frames/s), CompuBench 1.5 Desktop — Video Composition (Frames/s), CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s).

Intel Core i5-5675R

Buy on Amazon

vs

AMD A9-9425

Buy on Amazon

 

Differences

Reasons to consider the Intel Core i5-5675R

• 2 more cores, run more applications at once: 4 vs 2
• A newer manufacturing process allows for a more powerful, yet cooler running processor: 14 nm vs 28 nm
• Around 73% better performance in PassMark — Single thread mark: 2297 vs 1329
• 3. 7x better performance in PassMark — CPU mark: 5653 vs 1518
• Around 9% better performance in Geekbench 4 — Multi-Core: 3349 vs 3077
• 3x better performance in GFXBench 4.0 — Car Chase Offscreen (Frames): 2827 vs 943
• 4.4x better performance in GFXBench 4.0 — Manhattan (Frames): 5454 vs 1243
• 2.5x better performance in GFXBench 4.0 — T-Rex (Frames): 8825 vs 3556
• 3x better performance in GFXBench 4.0 — Car Chase Offscreen (Fps): 2827 vs 943
• 4.4x better performance in GFXBench 4.0 — Manhattan (Fps): 5454 vs 1243
• 2.5x better performance in GFXBench 4.0 — T-Rex (Fps): 8825 vs 3556

Number of cores	4 vs 2
Manufacturing process technology	14 nm vs 28 nm
PassMark — Single thread mark	2297 vs 1329
PassMark — CPU mark	5653 vs 1518
Geekbench 4 — Multi-Core	3349 vs 3077
GFXBench 4. 0 — Car Chase Offscreen (Frames)	2827 vs 943
GFXBench 4.0 — Manhattan (Frames)	5454 vs 1243
GFXBench 4.0 — T-Rex (Frames)	8825 vs 3556
GFXBench 4.0 — Car Chase Offscreen (Fps)	2827 vs 943
GFXBench 4.0 — Manhattan (Fps)	5454 vs 1243
GFXBench 4.0 — T-Rex (Fps)	8825 vs 3556

Reasons to consider the AMD A9-9425

• Around 3% higher clock speed: 3.7 GHz vs 3.60 GHz
• 4.3x lower typical power consumption: 15 Watt vs 65 Watt
• 2.2x better performance in Geekbench 4 — Single Core: 2034 vs 931

Maximum frequency	3. 7 GHz vs 3.60 GHz
Thermal Design Power (TDP)	15 Watt vs 65 Watt
Geekbench 4 — Single Core	2034 vs 931

Compare benchmarks

CPU 1: Intel Core i5-5675R
CPU 2: AMD A9-9425

PassMark — Single thread mark	CPU 1 CPU 2
PassMark — CPU mark	CPU 1 CPU 2
Geekbench 4 — Single Core	CPU 1 CPU 2
Geekbench 4 — Multi-Core	CPU 1 CPU 2
GFXBench 4. 0 — Car Chase Offscreen (Frames)	CPU 1 CPU 2
GFXBench 4.0 — Manhattan (Frames)	CPU 1 CPU 2
GFXBench 4.0 — T-Rex (Frames)	CPU 1 CPU 2
GFXBench 4. 0 — Car Chase Offscreen (Fps)	CPU 1 CPU 2
GFXBench 4.0 — Manhattan (Fps)	CPU 1 CPU 2
GFXBench 4.0 — T-Rex (Fps)	CPU 1 CPU 2

Name	Intel Core i5-5675R	AMD A9-9425
PassMark — Single thread mark	2297	1329
PassMark — CPU mark	5653	1518
Geekbench 4 — Single Core	931	2034
Geekbench 4 — Multi-Core	3349	3077
GFXBench 4. 0 — Car Chase Offscreen (Frames)	2827	943
GFXBench 4.0 — Manhattan (Frames)	5454	1243
GFXBench 4.0 — T-Rex (Frames)	8825	3556
GFXBench 4.0 — Car Chase Offscreen (Fps)	2827	943
GFXBench 4.0 — Manhattan (Fps)	5454	1243
GFXBench 4.0 — T-Rex (Fps)	8825	3556
CompuBench 1.5 Desktop — Face Detection (mPixels/s)		7. 781
CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s)		112.324
CompuBench 1.5 Desktop — T-Rex (Frames/s)		0.615
CompuBench 1.5 Desktop — Video Composition (Frames/s)		13.577
CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s)		40.717

Compare specifications (specs)

	Intel Core i5-5675R	AMD A9-9425
Architecture codename	Broadwell	Stoney Ridge
Launch date	Q2’15	2Q18
Place in performance rating	199	1097
Processor Number	i5-5675R
Series	5th Generation Intel® Core™ i5 Processors	AMD A9-Series APU for Laptops
Status	Discontinued
Vertical segment	Desktop	Laptop
Family		AMD A-Series Processors
OPN Tray		AM9425AYN23AC
OS Support		Windows 10 — 64-Bit Edition, RHEL x86 64-Bit, Ubuntu x86 64-Bit
64 bit support
Base frequency	3. 10 GHz	3.1 GHz
Bus Speed	5 GT/s DMI2
Manufacturing process technology	14 nm	28 nm
Maximum frequency	3.60 GHz	3.7 GHz
Number of cores	4	2
Number of threads	4
Compute Cores		5
Die size		124 mm
L1 cache		128 KB (per core)
L2 cache		1 MB
Maximum case temperature (TCase)		74 °C
Maximum core temperature		90°C
Number of GPU cores		3
Transistor count		1200 million
Unlocked
Max memory channels	2	1
Maximum memory bandwidth	29. 86 GB/s
Maximum memory size	32 GB
Supported memory types	DDR3L-1333/1600/1866 @ 1.5V	DDR4
Supported memory frequency		2133 MHz
Device ID	0x1622
eDRAM	128 MB
Graphics base frequency	300 MHz
Graphics max dynamic frequency	1. 10 GHz
Intel® Clear Video HD technology
Intel® Clear Video technology
Intel® Flexible Display Interface (Intel® FDI)
Intel® InTru™ 3D technology
Intel® Quick Sync Video
Max video memory	32 GB
Processor graphics	Intel® Iris® Pro Graphics 6200	AMD Radeon R5 Graphics
Enduro
Graphics max frequency		900 MHz
Switchable graphics
Unified Video Decoder (UVD)
DisplayPort
DVI
eDP
HDMI
Number of displays supported	3
VGA
Max resolution over DisplayPort	[email protected]
Max resolution over eDP	[email protected]
Max resolution over HDMI 1. 4	[email protected]
Max resolution over VGA	[email protected]
DirectX	11.2	12
OpenGL	4.3
Vulkan
Low Halogen Options Available
Max number of CPUs in a configuration	1	1
Package Size	37. 5mm x 37.5mm
Sockets supported	FCBGA1364
Thermal Design Power (TDP)	65 Watt	15 Watt
Thermal Solution	PCA 2013D
Configurable TDP		10-15 Watt
Max number of PCIe lanes	16
PCI Express revision	3.0	3.0
PCIe configurations	Up to 1×16, 2×8, 1×8+2×4
Scalability	1S Only
Anti-Theft technology
Execute Disable Bit (EDB)
Intel® Identity Protection technology
Intel® OS Guard
Intel® Secure Key technology
Intel® Trusted Execution technology (TXT)
4G WiMAX Wireless
Enhanced Intel SpeedStep® technology
Idle States
Instruction set extensions	Intel® SSE4. 1, Intel® SSE4.2, Intel® AVX2
Intel 64
Intel® AES New Instructions
Intel® Stable Image Platform Program (SIPP)
Intel® TSX-NI
Intel® Turbo Boost technology
Intel® vPro™ Platform Eligibility
Thermal Monitoring
Adaptive Voltage and Frequency Scaling (AVFS)
AMD App Acceleration
AMD HD3D technology
AMD Mantle API
DualGraphics
Fused Multiply-Add (FMA)
Fused Multiply-Add 4 (FMA4)
Intel® Advanced Vector Extensions (AVX)
Intel® Virtualization Technology (VT-x)
Intel® Virtualization Technology for Directed I/O (VT-d)
Intel® Virtualization Technology for Itanium (VT-i)
Intel® VT-x with Extended Page Tables (EPT)
AMD Virtualization (AMD-V™)

Intel Core i5-5200U vs.

AMD A9-9420

Intel Core i5-5200U

The Intel Core i5-5200U operates with 2 cores and 4 CPU threads. It run at 2.70 GHz base 2.50 GHz all cores while the TDP is set at 15 W.The processor is attached to the BGA 1168 CPU socket. This version includes 3.00 MB of L3 cache on one chip, supports 2 memory channels to support DDR3-1600 RAM and features 2.0 PCIe Gen 12 lanes. Tjunction keeps below — degrees C. In particular, Broadwell U Architecture is enhanced with 14 nm technology and supports VT-x, VT-x EPT, VT-d. The product was launched on Q1/2015

AMD A9-9420

The AMD A9-9420 operates with 2 cores and 4 CPU threads. It run at 3.60 GHz base 3.00 GHz all cores while the TDP is set at 15 W.The processor is attached to the FP4 CPU socket. This version includes 2.00 MB of L3 cache on one chip, supports 1 memory channels to support DDR4-2133 RAM and features 3.0 PCIe Gen 8 lanes. Tjunction keeps below 90 °C degrees C. In particular, Stoney Ridge (Excavator) Architecture is enhanced with 28 nm technology and supports AMD-V. The product was launched on Q2/2017

Intel Core i5-5200U

AMD A9-9420

Compare Detail

2.20 GHz	Frequency	3.00 GHz
2	Cores	2
2.70 GHz	Turbo (1 Core)	3.60 GHz
2.50 GHz	Turbo (All Cores)	3.00 GHz
Yes	Hyperthreading	No
No	Overclocking	No
normal	Core Architecture	normal
Intel HD Graphics 5500	GPU	AMD Radeon R5 (Stoney Ridge)
0.90 GHz	GPU (Turbo)	No turbo
14 nm	Technology	28 nm
0.90 GHz	GPU (Turbo)	No turbo
11.2	DirectX Version	12
3	Max. displays	3
DDR3-1600	Memory	DDR4-2133
2	Memory channels	1
	Max memory
No	ECC	No
—	L2 Cache	—
3. 00 MB	L3 Cache	2.00 MB
2.0	PCIe version	3.0
12	PCIe lanes	8
14 nm	Technology	28 nm
BGA 1168	Socket	FP4
15 W	TDP	15 W
VT-x, VT-x EPT, VT-d	Virtualization	AMD-V
Q1/2015	Release date	Q2/2017
Show more data		Show more data

Cinebench R20 (Single-Core)

Cinebench R20 is the successor of Cinebench R15 and is also based on the Cinema 4 Suite. Cinema 4 is a worldwide used software to create 3D forms. The single-core test only uses one CPU core, the amount of cores or hyperthreading ability doesn’t count.

Cinebench R20 (Multi-Core)

Cinebench R20 is the successor of Cinebench R15 and is also based on the Cinema 4 Suite. Cinema 4 is a worldwide used software to create 3D forms. The multi-core test involves all CPU cores and taks a big advantage of hyperthreading.

Cinebench R15 (Single-Core)

Cinebench R15 is the successor of Cinebench 11.5 and is also based on the Cinema 4 Suite. Cinema 4 is a worldwide used software to create 3D forms. The single-core test only uses one CPU core, the amount of cores or hyperthreading ability doesn’t count.

Cinebench R15 (Multi-Core)

Cinebench R15 is the successor of Cinebench 11.5 and is also based on the Cinema 4 Suite. Cinema 4 is a worldwide used software to create 3D forms. The multi-core test involves all CPU cores and taks a big advantage of hyperthreading.

Geekbench 5, 64bit (Single-Core)

Geekbench 5 is a cross plattform benchmark that heavily uses the systems memory. A fast memory will push the result a lot. The single-core test only uses one CPU core, the amount of cores or hyperthreading ability doesn’t count.

Geekbench 5, 64bit (Multi-Core)

Geekbench 5 is a cross plattform benchmark that heavily uses the systems memory. A fast memory will push the result a lot. The multi-core test involves all CPU cores and taks a big advantage of hyperthreading.

iGPU — FP32 Performance (Single-precision GFLOPS)

The theoretical computing performance of the internal graphics unit of the processor with simple accuracy (32 bit) in GFLOPS. GFLOPS indicates how many billion floating point operations the iGPU can perform per second.

Geekbench 3, 64bit (Single-Core)

Geekbench 3 is a cross plattform benchmark that heavily uses the systems memory. A fast memory will push the result a lot. The single-core test only uses one CPU core, the amount of cores or hyperthreading ability doesn’t count.

Geekbench 3, 64bit (Multi-Core)

Geekbench 3 is a cross plattform benchmark that heavily uses the systems memory. A fast memory will push the result a lot. The multi-core test involves all CPU cores and taks a big advantage of hyperthreading.

Cinebench R11.5, 64bit (Single-Core)

Cinebench 11. 5 is based on the Cinema 4D Suite, a software that is popular to generate forms and other stuff in 3D. The single-core test only uses one CPU core, the amount of cores or hyperthreading ability doesn’t count.

Cinebench R11.5, 64bit (Multi-Core)

Cinebench 11.5 is based on the Cinema 4D Suite, a software that is popular to generate forms and other stuff in 3D. The multi-core test involves all CPU cores and taks a big advantage of hyperthreading.

Cinebench R11.5, 64bit (iGPU, OpenGL)

Cinebench 11.5 is based on the Cinema 4D Suite, a software that is popular to generate forms and other stuff in 3D. The iGPU test uses the CPU internal graphic unit to execute OpenGL commands.

Estimated results for PassMark CPU Mark

Some of the CPUs listed below have been benchmarked by CPU-Comparison. However the majority of CPUs have not been tested and the results have been estimated by a CPU-Comparison’s secret proprietary formula. As such they do not accurately reflect the actual Passmark CPU mark values and are not endorsed by PassMark Software Pty Ltd.

Electric Usage Estimate

Average hours of use per day

Average CPU Utilization (0-100%)

Power cost, dollar per kWh

Electric Usage Estimate

Average hours of use per day

Average CPU Utilization (0-100%)

Power cost, dollar per kWh

Intel Core i5-5200U		AMD A9-9420
15 W	Max TDP	15 W
NA	Power consumption per day (kWh)	NA
NA	Running cost per day	NA
NA	Power consumption per year (kWh)	NA
NA	Running cost per year	NA

Popular Comparision

Comments

AMD A9-9425 vs Intel Core i5-8250U: What is the difference?

44 BALLLA

AMD A9-9425

49 BALLLA

Intel Core i5-8250U

VS

68 Facts compared to

AMD A9-9425

Intel Core i5-8250U

Why AMD A9-

Why AMD A9-000U

Why AMD A9-000U

Why AMD A9-000u

Intel Core i5-8250U?

• GPU frequency 458MHz higher?
  758MHz vs 300MHz
• 0. 3GHz higher turbo clock speed?
  3.7GHz vs 3.4GHz
• 0.25MB/core more L2 cache per core?
  0.5MB/core vs 0.25MB/core
• 15 higher hour multiplier?
  31 vs 16
• Has FMA4?

Why is Intel Core i5-8250U better than AMD A9-9425?

• 267MHz higher RAM speed?
  2400MHz vs 2133MHz
• 6 more CPU threads?
  8 vs 2
• 10°C higher than maximum operating temperature?
  100°C vs 90°C
• Is 14nm smaller?
  14nm vs 28nm
• 3.83x higher PassMark result?
  5941 vs 1552
• 60KB more L1 cache?
  256KB vs 196KB
• 45.68% higher PassMark score (single)?
  1939 vs 1331
• 1 more memory channels?
  2 vs 1

Which comparisons are the most popular?

AMD A9-9425

VS

Intel Core i5-8265U

Intel Core i5-8250U

VS

Intel Core I3-1115g4 AMD A9-9425

VS 9000)

Intel Core i5-8250U

vs

AMD Ryzen 5 3500U

AMD A9-9425

vs

Intel Celeron N4020

Intel Core i5-8250U

VS

Intel Core i3-1005g1

AMD A9-9425

VS

Intel Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core 40004

AMD RYZEN 3 2200U

AMD A9-9425

VS

Intel Core i3-6006u

Intel Core i5-8250U

VS

Intel Core i7-6500U

VS

AMD AMD AMD AMD AMD -9125

Intel Core i5-8250U

vs

AMD Ryzen 3 3200U

AMD A9-9425

vs

AMD Athlon Silver 3050U

Intel Core i5-8250U

vs

AMD Ryzen 5 2500U

AMD A9-9425

vs

Intel Core i5-6200u

Intel Core i5-8250u

VS

AMD RYZEN 5 5500U

A9-9425

VS

AMD ATHLON

VS

VS I5-8250U 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u, i7-7500U9Ol000 /10

5 Votes

performance

5. 9 /10

7 Votes

7.4 /10

5 Votes

Reliability

7.0 /10

004 7 VOTES

8.8 /10

5 Votes

Energy Effectiveness

7.9 /10

7 Votes

6.4 /10

9000 5 VOTES

Production

Production. Production. Production; productivity. Production; productivity. Production; productivity; productivity. Production; productivity. Production; productivity. Production;

2 x 3.1GHz

4 x 1.6GHz

CPU speed indicates how many processing cycles per second a processor can perform, given all its cores (processors). It is calculated by adding the clock speeds of each core or, in the case of multi-core processors, each group of cores.

2nd processor thread

More threads result in better performance and better multitasking.

3.speed turbo clock

3.7GHz

3.4GHz

When the processor is running below its limits, it can jump to a higher clock speed to increase performance.

4. Has unlocked multiplier

✖AMD A9-9425

✖Intel Core i5-8250U

Some processors come with an unlocked multiplier and are easier to overclock, allowing for better performance in games and other applications.

5.L2 Cache

More L2 scratchpad memory results in faster results in CPU and system performance tuning.

6.L3 cache

Unknown. Help us offer a price. (AMD A9-9425)

More L3 scratchpad memory results in faster results in CPU and system performance tuning.

7.L1 cache

More L1 cache results in faster results in CPU and system performance tuning.

8.core L2

0.5MB/core

0.25MB/core

More data can be stored in the L2 scratchpad for access by each processor core.

9. L3 core

Unknown. Help us offer a price. (AMD A9-9425)

1.5MB/core

More data can be stored in the L3 scratchpad for access by each processor core.

Memory

1.RAM speed

2133MHz

2400MHz

Can support faster memory which speeds up system performance.

2.max memory bandwidth

Unknown. Help us offer a price. (AMD A9-9425)

34.1GB/s

This is the maximum rate at which data can be read from or stored in memory.

3. DDR version

DDR (Dynamic Dynamic Random Access Memory Double Data Rate) is the most common type of RAM. New versions of DDR memory support higher maximum speeds and are more energy efficient.

4.Memory channels

More memory channels increase the speed of data transfer between memory and processor.

5.max memory

Unknown. Help us offer a price. (AMD A9-9425)

Maximum amount of memory (RAM).

6.bus baud rate

Unknown. Help us offer a price. (AMD A9-9425)

The bus is responsible for transferring data between various components of a computer or device.

7. Supports memory troubleshooting code

✖AMD A9-9425

✖Intel Core i5-8250U

Memory troubleshooting code can detect and repair data corruption. It is used when necessary to avoid distortion, such as in scientific computing or when starting a server.

8.eMMC version

Unknown. Help us offer a price. (AMD A9-9425)

Unknown. Help us offer a price. (Intel Core i5-8250U)

A newer version of eMMC — built-in flash memory — speeds up the memory interface, has a positive effect on device performance, for example, when transferring files from a computer to internal memory via USB.

9. bus frequency

Unknown. Help us offer a price. (AMD A9-9425)

Unknown. Help us offer a price. (Intel Core i5-8250U)

The bus is responsible for transferring data between various components of a computer or device

Geotagging

1. PassMark result

This benchmark measures CPU performance using multi-threading.

2. PassMark result (single)

This test measures processor performance using a thread of execution.

3.Geekbench 5 result (multi-core)

Geekbench 5 is a cross-platform test that measures the performance of a multi-core processor. (Source: Primate Labs,2022)

4.Cinebench R20 result (multi-core)

Cinebench R20 is a test that measures the performance of a multi-core processor by rendering a 3D scene.

5.Result Cinebench R20 (single core)

Cinebench R20 is a test to evaluate the performance of a single core processor when rendering a 3D scene.

6.Geekbench 5 result (single core)

Geekbench 5 is a cross-platform test that measures the single core performance of a processor. (Source: Primate Labs, 2022)

7. Blender test result (bmw27)

Unknown. Help us offer a price. (AMD A9-9425)

771.41seconds

The Blender benchmark (bmw27) measures CPU performance by rendering a 3D scene. More powerful processors can render a scene in a shorter time.

8.Blender result (classroom)

Unknown. Help us offer a price. (AMD A9-9425)

2852.02seconds

The Blender (classroom) benchmark measures CPU performance by rendering a 3D scene. More powerful processors can render a scene in a shorter time.

9.performance per watt

This means that the processor is more efficient, giving more performance per watt of power used.

Functions

1. uses multithreading

✖AMD A9-9425

✔Intel Core i5-8250U

processor cores into logical cores, also known as threads. Thus, each core can run two instruction streams at the same time.

2. Has AES

✔AMD A9-9425

✔Intel Core i5-8250U

AES is used to speed up encryption and decryption.

3. Has AVX

✔AMD A9-9425

✔Intel Core i5-8250U

AVX is used to help speed up calculations in multimedia, scientific and financial applications, and to improve the performance of the Linux RAID program.

4.Version SSE

SSE is used to speed up multimedia tasks such as editing images or adjusting audio volume. Each new version contains new instructions and improvements.

5. Has F16C

✔AMD A9-9425

✔Intel Core i5-8250U

F16C is used to speed up tasks such as image contrast adjustment or volume control.

6.bits transmitted at the same time

Unknown. Help us offer a price. (AMD A9-9425)

Unknown. Help us offer a price. (Intel Core i5-8250U)

NEON provides faster media processing such as MP3 listening.

7. Has MMX

✔AMD A9-9425

✔Intel Core i5-8250U

MMX is used to speed up tasks such as adjusting image contrast or adjusting volume.

8.Has TrustZone

✖AMD A9-9425

✖Intel Core i5-8250U

Technology is integrated into the processor to ensure device security when using features such as mobile payments and streaming video using Digital Rights Management (DRM) technology ).

9.interface width

Unknown. Help us offer a price. (AMD A9-9425)

Unknown. Help us offer a price. (Intel Core i5-8250U)

The processor can decode more instructions per clock (IPC), which means that the processor performs better

Other

i5-8250U

System on a Chip (SoC) has an integrated LTE cellular chip. LTE can download at higher speeds than older 3G technologies.

2.flops

0.2 TFLOPS (AMD Radeon R5)

Unknown. Help us offer a price.

FLOPS is a measurement of GPU processing power.

3.pixel speed

3.2 GPixel/s (AMD Radeon R5)

Unknown. Help us offer a price.

The number of pixels that can be displayed on the screen every second.

4. texture size

6.4 GTexels/s (AMD Radeon R5)

Unknown. Help us offer a price.

The number of textured pixels that can be displayed on the screen every second.

Price comparison

Cancel

Which CPU is better?

Compare AMD A9-9420 and Intel Core i5-560M

Comparative analysis of AMD A9-9420 and Intel Core i5-560M processors by all known characteristics in the categories: General Information, Performance, Memory, Graphics, Graphical Interfaces, Compatibility, Peripherals, Virtualization, Security and Reliability, Technology.
Analysis of processor performance by benchmarks: PassMark — Single thread mark, PassMark — CPU mark, Geekbench 4 — Single Core, Geekbench 4 — Multi-Core, CompuBench 1.5 Desktop — Face Detection (mPixels/s), CompuBench 1.5 Desktop — Ocean Surface Simulation ( Frames/s), CompuBench 1.5 Desktop — T-Rex (Frames/s), CompuBench 1.5 Desktop — Video Composition (Frames/s), CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s), GFXBench 4.0 — Car Chase Offscreen (Frames ), GFXBench 4.0 — Manhattan (Frames), GFXBench 4.0 — T-Rex (Frames), GFXBench 4.0 — Car Chase Offscreen (Fps), GFXBench 4.0 — Manhattan (Fps), GFXBench 4.0 — T-Rex (Fps).

AMD A9-9420

versus

Intel Core i5-560M

Benefits

Why choose AMD A9-9420

• : 3.6 GHz vs 3.20 GHz
• Newer manufacturing process of the processor allows it to be more powerful, but with lower power consumption: 28 nm vs 32 nm
• L2 cache is 2 times larger, which means more data can be stored in it for quick access
• 2. 3 times less power consumption: 15 Watt vs 35 Watt
• Performance in PassMark — Single thread mark benchmark is about 4% higher : 1301 vs 1249
• 4.3 times greater performance in Geekbench 4 — Single Core: 1907 vs 446
• 3 times greater performance in Geekbench 4 — Multi-Core benchmark: 2847 vs 950
• in the benchmark CompuBench 1.5 Desktop — Face Detection (mPixels/s) about 31% more: 0.626 vs 0.479
• CompuBench 1.5 Desktop — T-Rex (Frames/s) about 50% more performance: 0.108 vs 0.072
• CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s) about 19% more: 2.538 vs 2.133

Issue date	1 June 2016 vs 1 September 2010
Maximum frequency	3.6 GHz vs 3.20 GHz
Process	28 nm vs 32 nm
Level 2 cache	1MB vs 512KB
Power consumption (TDP)	15 Watt vs 35 Watt
PassMark — Single thread mark	1301 vs 1249
Geekbench 4 — Single Core	1907 vs 446
Geekbench 4 — Multi-Core	2847 vs 950
CompuBench 1. 5 Desktop — Face Detection (mPixels/s)	0.626 vs 0.479
CompuBench 1.5 Desktop — T-Rex (Frames/s)	0.108 vs 0.072
CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s)	2.538 vs 2.133

Reasons to choose Intel Core i5-560M

• 2 more threads: 4 vs 2
• About 17% more max core temperature: 105°C vs 90°C
• About 25% more performance in PassMark — CPU mark benchmark: 1878 vs 1502
• Performance in CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/ s) 7.9 times more: 25.197 vs 3.197

Number of threads	4 vs 2
Maximum core temperature	105°C vs 90°C
PassMark — CPU mark	1878 vs 1502
CompuBench 1. 5 Desktop — Ocean Surface Simulation (Frames/s)	25.197 vs 3.197

Benchmark comparison

CPU 1: AMD A9-9420
CPU 2: Intel Core i5-560M

PassMark — Single thread mark	CPU 1 CPU 2
PassMark — CPU mark	CPU 1 CPU 2
Geekbench 4 — Single Core	CPU 1 CPU 2
Geekbench 4 — Multi-Core	CPU 1 CPU 2
CompuBench 1. 5 Desktop — Face Detection (mPixels/s)	CPU 1 CPU 2
CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s)	CPU 1 CPU 2	25.197
CompuBench 1.5 Desktop — T-Rex (Frames/s)	CPU 1 CPU 2
CompuBench 1. 5 Desktop — Bitcoin Mining (mHash/s)	CPU 1 CPU 2

Name	AMD A9-9420	Intel Core i5-560M
PassMark — Single thread mark	1301	1249
PassMark — CPU mark	1502	1878
Geekbench 4 — Single Core	1907	446
Geekbench 4 — Multi-Core	2847	950
CompuBench 1. 5 Desktop — Face Detection (mPixels/s)	0.626	0.479
CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s)	3.197	25.197
CompuBench 1.5 Desktop — T-Rex (Frames/s)	0.108	0.072
CompuBench 1.5 Desktop — Video Composition (Frames/s)	0.309
CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s)	2.538	2.133
GFXBench 4.0 — Car Chase Offscreen (Frames)	799
GFXBench 4. 0 — Manhattan (Frames)	1062
GFXBench 4.0 — T-Rex (Frames)	2951
GFXBench 4.0 — Car Chase Offscreen (Fps)	799
GFXBench 4.0 — Manhattan (Fps)	1062
GFXBench 4.0 — T-Rex (Fps)	2951

Feature comparison

configuration

	AMD A9-9420	Intel Core i5-560M
Architecture name	Stoney Ridge	Arrandale
Family	AMD A-Series Processors
Issue date	1 June 2016	September 1, 2010
OPN Tray	AM9420AYN23AC
OS Support	Windows 10 — 64-Bit Edition, RHEL x86 64-Bit, Ubuntu x86 64-Bit
Place in the rating	1720	2369
Series	AMD A9-Series APU for Laptops	Legacy Intel® Core™ Processors
Applicability	Laptop	Mobile
Price at first issue date		$225
Price now		$89. 97
Processor Number		i5-560M
Status		Discontinued
Price/performance ratio (0-100)		8.47
Support 64 bit
Base frequency	3GHz	2.66 GHz
Compute Cores	5
Crystal area	124.5mm	81 mm2
Level 2 cache	1MB	512KB
Process	28nm	32nm
Maximum core temperature	90°C	105°C
Maximum frequency	3. 6 GHz	3.20 GHz
Number of cores	2	2
Number of GPU cores	3
Number of threads	2	4
Number of transistors	1200 Million	382 million
Unlocked
Bus Speed ​​		2.5 GT/s DMI
System bus (FSB)		2500MHz
Level 1 cache		128KB
Level 3 cache		3072KB
Supported memory frequency	2133MHz
Maximum number of memory channels		2
Maximum memory bandwidth		17. 1 GB/s
Maximum memory size		8GB
Supported memory types		DDR3 800/1066
Maximum GPU clock	847MHz	766MHz
Number of iGPU cores	3
Integrated graphics	AMD Radeon R5 Graphics	Intel HD Graphics
Graphics base frequency		500MHz
Graphics max dynamic frequency		766MHz
Intel® Clear Video Technology HD
Intel® Clear Video Technology
Intel® Flexible Display Interface (Intel® FDI)
DisplayPort
HDMI
Maximum number of monitors supported		2
Configurable TDP	10-15 Watt
Power consumption (TDP)	15 Watt	35 Watt
Low Halogen Options Available
Maximum number of processors in		1
Package Size		rPGA 37. 5mmx 37.5mm, BGA 34mmx28mm
Supported sockets		BGA1288, PGA988
Revision PCI Express	3.0	2.0
Number of PCI Express lanes		16
PCIe configurations		1×16
AMD Virtualization (AMD-V™)
Intel® Virtualization Technology (VT-x)
Intel® Virtualization Technology for Directed I/O (VT-d)
Intel® VT-x with Extended Page Tables (EPT)
Execute Disable Bit (EDB)
Intel® Trusted Execution Technology (TXT)
Enhanced Intel SpeedStep® Technology
Flexible Display interface (FDI)
Idle States
Extended instructions		Intel® SSE4. 1, Intel® SSE4.2
Intel 64
Intel® AES New Instructions
Intel® Fast Memory Access
Intel® Flex Memory Access
Intel® Hyper-Threading Technology
Intel® Turbo Boost Technology
Intel® vPro™ Platform Eligibility
Physical Address Extensions (PAE)		36-bit
Thermal Monitoring

Intel Core i5-11500 vs AMD A9-9425 — comparative characteristics and benchmarks of processors

VS

Intel Core i5-11500

AMD A9-9425

Which one to choose?

It’s time to choose the winner. What is the difference and which is better in Intel Core i5-11500 vs AMD A9-9425 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 Intel Core i5-11500 and AMD A9-9425. 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.00 GHz

Clock speed

3.10 GHz

6

Number of cores

2

4.30 GHz

Turbo (1 core)

3.70 GHZ

12

Streams

2

No DATA

TURBO (2 Cores)

3. 10 GHZ

9000 GHz

Turbo (6 cores)

normal

Architecture

0x

A core

0x

B core

B core

processor family

0018 Internal graphics

It’s hard to compare Intel Core i5-11500 vs AMD A9-9425 when graphics card function and specifications matter only in laptops. In workstations, this is not an advantage, due to the installation of an additional graphics accelerator.

Intel Iris Xe Graphics 32 (Rocket Lake S)

GPU name

AMD Radeon R5 (Stoney Ridge)

0.40 GHz

GPU frequency

0.85 GHz

0003

GPU (Turbo)

No Turbo

12

Generation

7

12

version DirectX

12

32

9000

no data

Maximum memory

2 GB

3

Number of monitors

3

14 nm

Technology

20003

Q2/2021

Release date

Q2/2016

16 GB

Max. GPU Memory

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 / Encode

h364

Decode

Decode / Encode

JPEG

Decode / Encode

no data

h365 8bit

Decode

no data

h365 10bit

Decode

Decode / Encode

VP8

Decode

Decode / Encode

VP9

Decode

Decode

VC -1

Decode

Decode / Encode

AVC

Decode / Encode

Decode / Encode

H365 / HEVC (8 BIT)

Decode

H365 / Hev0003

Decode

AV1

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.

DDR4-3200

Type of memory

DDR4-2133

128 GB

Maximum memory

8 GB

2

memory channels

1 9,000 1

NO

ECC

NO

4. 0

version PCIe

3.0

16

PCIe Lines

8

Cryphism 9000 9000

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. Choosing between Intel Core i5-11500 and AMD A9-9425 it is better to stop at the option where there is less heat dissipation (TDP).

NO DATA

TDP

15 W

100 ° C

The maximum temperature

90 ° C

—

Maximum TDP

25 W

TDP Down

10 W

65 W

TDP (PL1)

—

TDP (PL2)

Technical details

12.00 MB

L3-Cache

004 2.00 MB

14 NM 9000 , AMD-VI

LGA 1200 9000 MB

L2-Cache

—

Part Number

Devices compatible with this processor

You probably already know which devices use processors. It can be a desktop computer or a laptop.

Unknown

Used in

Unknown

Popular CPU comparisons

one.		Intel Core i5-11500 vs. Intel Core i5-11400
2.		Intel Core i5-10500 vs. Intel Core i5-11500
3.		Intel Core i5-11500 vs. Intel Core i5-11600
four.		AMD Ryzen 5 PRO 4650G vs. Intel Core i5-11500
5.		AMD Ryzen 5 PRO 5650G vs. Intel Core i5-11500
6.		AMD A9-9425 vs. AMD A8-7650K
7.		AMD Epyc 7232P vs. AMD A9-9425
eight.		AMD Ryzen 5 5600H vs. AMD A9-9425
9.		AMD A6-9220C vs. AMD A9-9425
ten.		Intel Xeon Platinum 8160T vs. AMD A9-9425
eleven.		AMD A10-5700 vs. AMD A9-9425
12.		AMD A9-9425 vs. Intel Core i5-5257U
13.		AMD A9-9425 vs. Intel Core i9-10900KF
fourteen.		Intel Xeon W-3223 vs. AMD A9-9425
fifteen.		Intel Core i5-11500 vs. AMD A9-9425

Intel Core i5-7300U or AMD A9-9400 APU (2016 M.SR)

• Main page
• >
• 40 Processors
• >

9002u

• >
• INTEL CORETEL CORETEL CORETEL CORE -9400 APU (2016 M.SR)

Family

• Core i5-7200u
  Compare
• Core i5-7260U
  Compare
• Core I5-7300HQ (compare

Family

2016 M. SR)
Compare

A9-9420 APU (2016 M.SR)
Compare

A9-9425 APU (2016 M.SR)
Compare

A9-9430 APU (2016 M.SR)

Game Speed

Core i5-7300U

49 (+42%)

A9-9400 APU (2016 M.SR)

28.4

Performance in games and similar applications, according to our tests.

The performance of 4 cores, if any, and performance per core has the greatest impact on the result, since most games do not fully use more than 4 cores.

The speed of caches and working with RAM is also important.

Speed ​​in office use

Core i5-7300U

53.8 (+35.9%)

A9-9400 APU (2016 M.SR)

34.5 9000

The performance of 1 core has the greatest impact on the result, since most of these applications use only one, ignoring the rest.

Similarly, many professional applications such as various CADs ignore multi-threaded performance.

Speed ​​in heavy applications

Core i5-7300U

26. 5 (+43.8%)

A9-9400 APU (2016 M.SR)

14.9 maximum

The performance of all cores and their number has the greatest impact on the result, since most of these applications willingly use all the cores and increase the speed accordingly.

At the same time, some periods of work can be demanding on the performance of one or two cores, for example, applying filters in the editor.

Data obtained from tests by users who tested their systems with and without overclocking. Thus, you see the average values ​​corresponding to the processor.

Speed ​​of numerical operations

Simple household tasks

Core i5-7300U 52.3 (+38.6%) A9-9400 APU (2016 M.SR) 32.1

Demanding games and tasks

Core i5-7300U 21. 9 (+60.3%) A9-9400 APU (2016 M.SR) 8.7

Extreme

Core i5-7300U 4.3 (+60.5%) A9-9400 APU (2016 M.SR) 1.7

Different tasks require different CPU strengths. A system with few fast cores and low memory latency will be fine for the vast majority of games, but will be inferior to a system with a lot of slow cores in a rendering scenario.

We believe that a minimum of 4/4 (4 physical cores and 4 threads) processor is suitable for a budget gaming PC. At the same time, some games can load it at 100%, slow down and freeze, and performing any tasks in the background will lead to a drop in FPS.

Ideally, the budget shopper should aim for a minimum of 4/8 and 6/6. A gamer with a big budget can choose between 6/12, 8/8 and 8/16. Processors with 10 and 12 cores can perform well in games with high frequency and fast memory, but are overkill for such tasks. Also, buying for the future is a dubious undertaking, since in a few years many slow cores may not provide sufficient gaming performance.

When choosing a processor for your work, consider how many cores your programs use. For example, photo and video editors can use 1-2 cores when working with filtering, and rendering or converting in the same editors already uses all threads.

Data obtained from tests by users who tested their systems both with overclocking (maximum value in the table) and without (minimum). A typical result is shown in the middle, the more filled in the color bar, the better the average result among all tested systems.

Characteristics

The data is not yet filled in, so the tables may lack information or existing functions may be omitted.

Basic

Manufacturer	Intel	AMD
DescriptionInformation about the processor, taken from the official website of the manufacturer.	Intel® Core™ i5-7300U Processor (3M Cache, up to 3.50 GHz)
ArchitectureCode name for the microarchitecture generation.	Kaby Lake
Process The manufacturing process, measured in nanometers. The smaller the technical process, the more perfect the technology, the lower the heat dissipation and power consumption.	14	No data
Release dateMonth and year the processor was released.	10-2019	10-2019
Model Official name.	i5-7300U
Cores The number of physical cores.	2	2
ThreadsNumber of threads. The number of logical processor cores that the operating system sees.	4	2
Multi-Threading Technology With Intel’s Hyper-threading and AMD’s SMT technology, one physical core is recognized as two logical cores by the operating system, thereby increasing processor performance in multi-threaded applications.	Hyper-threading (note that some games may not work well with Hyper-threading, you can disable the technology in the BIOS of the motherboard for maximum FPS).	Missing
Base frequencyGuaranteed frequency of all processor cores at maximum load. Performance in single-threaded and multi-threaded applications and games depends on it. It is important to remember that speed and frequency are not directly related. For example, a new processor at a lower frequency may be faster than an old one at a higher one.	2.6 GHz	2.4 GHz
Turbo frequency The maximum frequency of one processor core in turbo mode. Manufacturers allow modern processors to independently increase the frequency of one or more cores under heavy load, due to which performance is noticeably increased. It may depend on the nature of the load, the number of loaded cores, temperature and the specified limits. Significantly affects the speed in games and applications that are demanding on the frequency of the CPU.	3.5 GHz	3.1 GHz
L3 cache size The third level cache acts as a buffer between the computer’s RAM and the processor’s level 2 cache. Used by all cores, the speed of information processing depends on the volume.	3	No data
Instructions	64-bit
Extended instruction set Allow to speed up calculations, processing and execution of certain operations. Also, some games require instruction support.	SSE4.1/4.2, AVX 2.0
Embedded Options Available Two enclosure versions. Standard and designed for mobile devices. In the second version, the processor can be soldered on the motherboard.	Yes	No
Bus frequency The speed of communication with the system.	4 GT/s OPI
Number of QPI links
TDPThermal Design Power is an indicator that determines heat dissipation in standard operation. The cooler or water cooling system must be rated for a larger value. Remember that with a factory bus or manual overclocking, TDP increases significantly.	15	No data
Cooling system specifications

Video core

Integrated graphics core Allows you to use your computer without a discrete graphics card. The monitor is connected to the video output on the motherboard. If earlier integrated graphics made it possible to simply work at a computer, today it can replace budget video accelerators and makes it possible to play most games at low settings.	Intel® HD Graphics 620
GPU base clockFrequency in 2D and idle.	300	No data
Maximum GPU frequencyMaximum 3D frequency.	1100	No data
Intel® Wireless Display (Intel® WiDi) Supports Wireless Display technology over Wi-Fi 802.11n. Thanks to it, a monitor or TV equipped with the same technology does not require a cable to connect.
Supported monitorsThe maximum number of monitors that can be connected to the integrated video core at the same time.	3

RAM

Maximum amount of RAMThe amount of RAM that can be installed on the motherboard with this processor.	32	No data
Supported type of RAM The type of RAM determines its frequency and timings (speed), availability, price.	DDR4-2133, LPDDR3-1866, DDR3L-1600
RAM Channels The multi-channel memory architecture increases data transfer speed. On desktop platforms, two-channel, three-channel and four-channel modes are available.	2
RAM bandwidth	34.1 GB/s
ECC memory Support for error-correcting memory that is used in servers. Usually more expensive than usual and requires more expensive server components. However, second-hand server processors, Chinese motherboards and ECC memory sticks, which are sold relatively cheaply in China, have become widespread.	No data	No data

PCI

configuration options

PCI-E The PCI Express computer bus version. The bandwidth and power limit depend on the version. There is backward compatibility.	3	No data
PCI	1×4, 2×2, 1×2+2×1 and 4×1	1×4, 2×2, 1×2+2×1 and 4×1
Number of PCI lanes	12	1×4, 2×2, 1×2+2×1 and 4×1

Data Security

AES-NI The AES command set extension speeds up applications that use appropriate encryption.	No data	No data
Intel® Secure Key An RDRAND instruction that allows you to create a high performance random number generator.	No data	No data

Decoration

Dimensions	No data	No data
Supported sockets	No data	No data
Maximum processors per motherboard	No data	No data

Which is better

Intel Core i5-7300U

• On average, gaming performance is 21% better.
• The speed of work in office applications and browsers is increased by 19%.
• In complex multi-threaded applications, faster and outperforms by 3%.
• The number of threads is increased by 2.
• The base frequency is increased by 0.2 GHz.

What are the similarities

• Prices for new processors are approximately equal.
• The number of physical cores is equal.

Amd a9 9425 analog intel

04/14/2020

The AMD A9-9425 processor is based on the Stoney Ridge architecture and is manufactured using an improved 28nm process technology. AMD A9-9425 is a 2-core processor clocked at 3.1 to 3.7 GHz with 1024 KB L2 cache and support for DDR4 memory. Compared to the AMD A9-9420, the new clock speed is increased by 100 MHz, so it’s not worth talking about a big performance boost.

APU AMD A9-9425 belongs to the seventh generation of AMD processors, therefore it has improved built-in temperature sensors with a STAPM (Skin Temperature Aware Power Management) controller and algorithms implemented using AVFS (adaptive voltage frequency scaling) provide a short-term increase in frequency and voltage, taking into account the current operating temperature of the APU. So, thanks to these improvements, performance can be increased by up to 56% compared to similar scenarios for Kaveri generation APUs, or by 10% compared to Carrizo APUs. If earlier in the category of junior solutions, to which the AMD A9 APU belongs-9425, AMD offered «cat» cores. Due to the high clock speed of 3.7 GHz, the performance of the processor in single-threaded mode is quite high, which cannot be said about multi-threading, the performance in this mode lags noticeably behind larger models based on the Bristol Ridge architecture.

AMD Radeon R5 (Stoney Ridge) integrated graphics has 3 active compute cores. Depending on the model, the maximum frequencies in our case are 900 MHz, and the performance varies depending on the TDP level and system memory. Compared to the Radeon R5 from the Bristol Ridge series, the graphics only have 3 GCN cores instead of 6. With two channels of DDR4 memory, the graphics can already compete with junior discrete graphics cards from 3-4 years ago. But manufacturers do not always use both channels and prefer to install one larger module. Because of this, the speed of processor calculations drops sharply and the graphics performance drops even more.

Specifications

Manufacturer
AMD
Series
A9
Microarchitecture
Stoney Ridge
Number of cores
22
Clock rate
3100 — 3700 MHz
Level 2 cache
1MB
Power input
10-25W
Graphics core
AMD Radeon R5 (800 MHz)
Technology
28 N.m.

CineBench R15 rendering

CINEBENCH cross-platform benchmark benchmark is widely used to evaluate the performance of Intel and AMD processors. It is based on the popular animation software CINEMA 4D of the German company MAXON, which is actively used by studios around the world to create 3D content. The CPU test involves rendering a certain scene in multi-threaded mode (all CPU cores are used). Rendering is the process of obtaining an image from a model using a computer program. Based on the result of the processor test, it is easy to calculate its speed — the faster the processor calculates the render, the more points it gets.

CineBench R15 CPU Single. Peripherals, Technology, Virtualization. Analysis of processor performance by benchmarks: PassMark — Single thread mark, PassMark — CPU mark, Geekbench 4 — Single Core, Geekbench 4 — Multi-Core, GFXBench 4.0 — Car Chase Offscreen (Frames), GFXBench 4.0 — Manhattan (Frames), GFXBench 4.0 — T-Rex (Frames), GFXBench 4.0 — Car Chase Offscreen (Fps), GFXBench 4.0 — Manhattan (Fps), GFXBench 4.0 — T-Rex (Fps).

Benefits

Reasons to choose AMD A9-9425

• About 68% more clock speed: 3. 7 GHz vs 2.2 GHz
• A newer manufacturing process for the processor allows it to be more powerful, but with lower power consumption: 28 nm vs 32 nm
• L1 cache is 2 times larger, which means more data can be stored in it for quick access
• L2 cache is 2 times larger, which means more data can be stored in it for quick access
• 2.3 times less power consumption: 15 Watt vs 35 Watt
• Performance in PassMark — Single thread mark about 41% better: 1461 vs 1039
• Performance in PassMark benchmark — CPU mark approximately 2% higher: 2436 vs 2382

Features
Maximum frequency	3.7GHz vs 2.2GHz
Process	28 nm vs 32 nm
Level 1 cache	128 KB (per core) vs 64 KB (per core)
Level 2 cache	1 MB vs 256 KB (per core)
Power consumption (TDP)	15 Watt vs 35 Watt
Benchmarks
PassMark — Single thread mark	1461 vs 1039
PassMark — CPU mark	2436 vs 2382

Benchmark comparison

CPU 1: AMD A9-9425
CPU 2: Intel Core i3-2332M

Why is AMD A9-9425 better than Intel Core i5-8250U?

• GPU frequency 500MHz over

Why is Intel Core i5-8250U better than AMD A9-9425?

• 3. 23% higher CPU clock speed
  4 x 1.6GHz vs 2 x 3.1GHz
• 267MHz higher RAM speed

What are the most popular comparisons?

3

Intel Core i5-8265u

Intel Core i5-8250U

AMD Ryzen 3 3200u

Intel Core i3-7020U

Intel Core I5-8250U

AMD Ryzen 5 3500U

9000 3 Core i5-8250U

AMD Ryzen 5 2500U

AMD Ryzen 3 3200U

Intel Core i5-8250U

AMD Athlon 300U

AMD Ryzen 3 2200U

Intel Core i5-8250U

Intel Celeron 4205U

Intel Core i5-8250U

AMD Ryzen 3 2200U

Intel Pentium Gold 5405U

Intel Core i5-8250U

Intel Core i3-1005G1

AMD Ryzen 5 2500U

Intel Core i5-8250U

AMD Ryzen 3 3300U

Intel Core i3 -6100H

Intel Core i5-8250U

Intel Core i5-8265U

General Information

The graphics processing unit (GPU) has a higher clock speed.

AMD Ryzen 7 Pro 3700U

32-bit operating system can support up to 4 GB of RAM. 64-bit allows more than 4 GB, which improves performance. It also allows you to run 64-bit applications.

Intel Core i5-8250U

With integrated graphics, you don’t need to buy a separate card.

Intel Core i5-8250U

A smaller size indicates a newer chip manufacturing process.

Qualcomm Snapdragon 765

The newer version of OpenGL, the better graphics quality in games.

AMD Ryzen 3 2300U

The heat dissipation requirement (TDP) is the maximum amount of energy that the cooling system will have to dissipate. A lower TDP also usually means less power consumption.

Intel Atom x7 Z8750

Performance

MediaTek Helio X30

2 x 2.6 & 4 x 2.2 & 4 x 1.9GHz

Intel Core i9-9980HK

When the processor is running below its limits, it can jump to a higher clock speed to increase performance.

Intel Core i5-8305G

The hour multiplier controls the speed of the processor.

Share with friends:

Tweet

Share

Share

Send

Class

Adblock detector

AMD A9-9420 vs. Intel Core i5-4200U

AMD A9-9420

AMD A9-9420 runs with 2 and 2 CPU threads It runs at 3.60 GHz base 3.00 GHz all cores while TDP is set to 15 W .CPU connects to CPU socket FP4 This version includes 2.00 MB of L3 cache on a single die, supports 1 to support DDR4-2133 RAM, and supports 3.0 PCIe Gen 8 . Tjunction keeps below 90 °C degrees C. In particular, the Stoney Ridge (Excavator) architecture has been advanced over 28 nm and supports AMD-V . The product was launched Q2/2017

Intel Core i5-4200U

Intel Core i5-4200U runs with 2 and 2 CPU threads It runs at 2.60 GHz base 2.30 GHz all cores while TDP is set to 15 W .CPU connects to BGA 1168 CPU socket This version includes 3.00 MB of L3 cache on a single die, supports 2 to support DDR3L-1600 SO-DIMM RAM, and supports 2.0 PCIe Gen 12 . Tjunction is kept below — degrees C. In particular, the Haswell U architecture is advanced beyond 22 nm and supports VT-x, VT-x EPT, VT-d . The product was launched Q3/2013

AMD A9-9420

Intel Core i5-4200U

Frequency 1.60 GHz 2 Cores 2 3.60 GHz Turbo (1 core) 2.60 GHz 3.00GHz Turbo (all cores) 2.30 GHz No. Hyper Threading Yes No. Overclocking No. normal Basic architecture normal

AMD Radeon R5 (Stoney Ridge)

GPU

Intel HD Graphics 4400

no turbo GPU (Turbo) 1.00 GHz 28nm Technology 22nm no turbo GPU (Turbo) 1. 00 GHz 12 DirectX Version 11.1 3 Max. displays 3 DDR4-2133 memory size DDR3L-1600 SO-DIMM 1 Memory channels 2 Maximum memory No ECC No. — L2 Cache — 2.00MB L3 Cache 3.00 MB 3.0 PCIe version 2.0 8 PCIe lanes 12 28nm Technology 22nm FP4 Connector BGA 1168 15 W TDP 15W AMD-V Virtualization VT-x, VT-x EPT, VT-d Q2/2017 Release date Q3/2013

Show more details

Show more details

Cinebench R20 (Single-Core)

Cinebench R20 is the successor to Cinebench R15 and is also based on the Cinema 4 Suite. Cinema 4 is software used all over the world to create 3D forms. The single-core test uses only one CPU core, the number of cores or hyper-threading capability is not taken into account.

Cinebench R20 (Multi-Core)

Cinebench R20 is the successor to Cinebench R15 and is also based on Cinema 4 Suite. Cinema 4 is software used all over the world to create 3D forms. The multi-core test uses all the CPU cores and has a big advantage of hyper-threading.

Cinebench R15 (Single-Core)

Cinebench R15 is the successor to Cinebench 11.5 and is also based on the Cinema 4 Suite. Cinema 4 is software used all over the world to create 3D forms. The single-core test uses only one CPU core, the number of cores or hyper-threading capability is not taken into account.

Cinebench R15 (Multi-Core)

Cinebench R15 is the successor to Cinebench 11.5 and is also based on Cinema 4 Suite. Cinema 4 is software used all over the world to create 3D forms. The multi-core test uses all the CPU cores and has a big advantage of hyper-threading.

Geekbench 5, 64bit (Single-Core)

Geekbench 5 is a memory-intensive cross-platform test. A fast memory will greatly push the result. The single-core test uses only one CPU core, the number of cores or hyper-threading capability is not taken into account.

Geekbench 5, 64bit (Multi-Core)

Geekbench 5 is a memory-intensive, cross-platform test. A fast memory will greatly push the result. The multi-core test uses all the CPU cores and has a big advantage of hyper-threading.

iGPU — FP32 Performance (Single-precision GFLOPS)

Theoretical processing performance of the processor’s internal graphics unit with simple precision (32 bits) in GFLOPS. GFLOPS specifies how many billions of floating point operations the iGPU can perform per second.

Geekbench 3, 64bit (Single-Core)

Geekbench 3 is a cross-platform test that is memory intensive. A fast memory will greatly push the result. The single-core test uses only one CPU core, the number of cores or hyper-threading capability is not taken into account.

Geekbench 3, 64bit (Multi-Core)

Geekbench 3 is a cross-platform benchmark that is memory intensive. A fast memory will greatly push the result. The multi-core test uses all the CPU cores and has a big advantage of hyper-threading.

Cinebench R11.5, 64bit (Single-Core)

Cinebench 11.5 is based on Cinema 4D Suite, a software that is popular for creating shapes and other things in 3D. The single-core test uses only one CPU core, the number of cores or hyper-threading capability is not taken into account.

Cinebench R11.5, 64bit (Multi-Core)

Cinebench 11.5 is based on Cinema 4D Suite, a software that is popular for creating shapes and other 3D. The multi-core test uses all the CPU cores and has a big advantage of hyper-threading.

Cinebench R11.5, 64bit (iGPU, OpenGL)

Cinebench 11.5 is based on Cinema 4D Suite, a software that is popular for creating shapes and other things in 3D. The iGPU test uses the CPU’s internal graphics unit to execute OpenGL commands.