Amd ryzen 5 3500u vs i5 8250u: AMD Ryzen 5 3500U vs Intel Core i5-8250U: What is the difference?

AMD Ryzen 5 3500U vs Intel Core i5-8250U: What is the difference?

54points

AMD Ryzen 5 3500U

49points

Intel Core i5-8250U

vs

64 facts in comparison

AMD Ryzen 5 3500U

Intel Core i5-8250U

Why is AMD Ryzen 5 3500U better than Intel Core i5-8250U?

• 31.25% faster CPU speed?
  4 x 2.1GHzvs4 x 1.6GHz
• 900MHz faster GPU clock speed?
  1200MHzvs300MHz
• 2nm smaller semiconductor size?
  12nmvs14nm
• 1MB bigger L2 cache?
  2MBvs1MB
• 19.83% higher PassMark result?
  7119vs5941
• 0.3GHz higher turbo clock speed?
  3.7GHzvs3.4GHz
• 128KB bigger L1 cache?
  384KBvs256KB
• 0.25MB/core more L2 cache per core?
  0.5MB/corevs0.25MB/core

Why is Intel Core i5-8250U better than AMD Ryzen 5 3500U?

• 2MB bigger L3 cache?
  6MBvs4MB
• 9. 05% higher single-core Geekbench 5 result?
  771vs707
• 0.5MB/core more L3 cache per core?
  1.5MB/corevs1MB/core
• 18.3 more performance per watt?
  188.0vs169.7
• 16 more GPU execution units?
  24vs8

Which are the most popular comparisons?

AMD Ryzen 5 3500U

vs

Intel Core i5-10210U

Intel Core i5-8250U

vs

Intel Core i3-1115G4

AMD Ryzen 5 3500U

vs

Intel Core i3-1115G4

Intel Core i5-8250U

vs

Intel Core i3-1005G1

AMD Ryzen 5 3500U

vs

Intel Core i3-10110U

Intel Core i5-8250U

vs

AMD Ryzen 3 2200U

AMD Ryzen 5 3500U

vs

Intel Core i5-1135G7

Intel Core i5-8250U

vs

Intel Core i7-6500U

AMD Ryzen 5 3500U

vs

AMD Ryzen 5 5500U

Intel Core i5-8250U

vs

AMD Ryzen 3 3200U

AMD Ryzen 5 3500U

vs

AMD Ryzen 3 5300U

Intel Core i5-8250U

vs

AMD Ryzen 5 2500U

AMD Ryzen 5 3500U

vs

Intel Core i5-8265U

Intel Core i5-8250U

vs

AMD Ryzen 5 5500U

AMD Ryzen 5 3500U

vs

Intel Core i5-1035G1

Intel Core i5-8250U

vs

Intel Core i7-7500U

AMD Ryzen 5 3500U

vs

AMD Ryzen 7 3700U

Intel Core i5-8250U

vs

Intel Core i5-7200U

Price comparison

User reviews

Overall Rating

AMD Ryzen 5 3500U

9 User reviews

AMD Ryzen 5 3500U

8. 7/10

9 User reviews

Intel Core i5-8250U

5 User reviews

Intel Core i5-8250U

7.4/10

5 User reviews

Features

Value for money

8.8/10

8 votes

7.4/10

5 votes

Gaming

7.9/10

8 votes

6.6/10

5 votes

Performance

8.6/10

8 votes

7.4/10

5 votes

Reliability

9.3/10

8 votes

8.8/10

5 votes

Energy efficiency

9.3/10

8 votes

6.4/10

5 votes

Performance

1.CPU speed

4 x 2.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 Ryzen 5 3500U

✖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

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

1MB/core

1.5MB/core

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

Memory

1.RAM speed

2400MHz

2400MHz

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

2.maximum memory bandwidth

35.76GB/s

34.1GB/s

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

3.DDR memory version

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

4.memory channels

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

5. maximum memory amount

The maximum amount of memory (RAM) supported.

6.bus transfer rate

Unknown. Help us by suggesting a value. (AMD Ryzen 5 3500U)

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

7.Supports ECC memory

✖AMD Ryzen 5 3500U

✖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 Ryzen 5 3500U)

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 Ryzen 5 3500U)

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

638.36seconds

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

1920.96seconds

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 Ryzen 5 3500U

✔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 Ryzen 5 3500U

✔Intel Core i5-8250U

AES is used to speed up encryption and decryption.

3.Has AVX

✔AMD Ryzen 5 3500U

✔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 Ryzen 5 3500U

✔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 Ryzen 5 3500U)

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 Ryzen 5 3500U

✔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 Ryzen 5 3500U

✖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 Ryzen 5 3500U)

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

Price comparison

Cancel

Which are the best CPUs?

Intel Core i5-8250U vs AMD Ryzen 5 3500U vs AMD Ryzen 5 2600

Performance Rating — CB R15 + R20 + 7-Zip + X265 + Blender + 3DM11 CPU — R5 3500U

log 27. 17:53:53

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

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

#2 checking url part for id 10032 +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 Sun, 25 Sep 2022 13:14:15 +0200 +0s … 0s

#5 linkCache_getLink no uid found +0.007s … 0.007s

#6 linkCache_getLink no uid found +0.003s … 0.011s

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

#8 composed specs +0s … 0.014s

#9 did output specs +0s … 0.014s

#10 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.017s

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

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

#13 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.019s

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

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

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

#17 getting avg benchmarks for device 9206 +0.001s … 0.019s

#18 linkCache_getLink using $NBC_LINKCACHE +0.004s … 0.024s

#19 got single benchmarks 9206 +0.225s … 0.249s

#20 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.252s

#21 linkCache_getLink using $NBC_LINKCACHE +0s … 0.252s

#22 linkCache_getLink using $NBC_LINKCACHE +0s … 0.252s

#23 linkCache_getLink using $NBC_LINKCACHE +0s … 0.252s

#24 linkCache_getLink using $NBC_LINKCACHE +0s … 0.252s

#25 linkCache_getLink using $NBC_LINKCACHE +0s … 0.252s

#26 linkCache_getLink using $NBC_LINKCACHE +0s … 0.252s

#27 linkCache_getLink using $NBC_LINKCACHE +0s … 0.252s

#28 linkCache_getLink using $NBC_LINKCACHE +0s … 0. 252s

#29 linkCache_getLink using $NBC_LINKCACHE +0s … 0.252s

#30 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.253s

#31 linkCache_getLink using $NBC_LINKCACHE +0s … 0.253s

#32 linkCache_getLink using $NBC_LINKCACHE +0s … 0.253s

#33 linkCache_getLink using $NBC_LINKCACHE +0s … 0.253s

#34 linkCache_getLink using $NBC_LINKCACHE +0s … 0.253s

#35 linkCache_getLink using $NBC_LINKCACHE +0s … 0.253s

#36 getting avg benchmarks for device 11161 +0s … 0.254s

#37 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.255s

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

#39 got single benchmarks 11161 +0.052s … 0.307s

#40 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.309s

#41 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.311s

#42 getting avg benchmarks for device 10032 +0s .. . 0.311s

#43 got single benchmarks 10032 +0.009s … 0.319s

#44 got avg benchmarks for devices +0s … 0.319s

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

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

#47 linkCache_getLink no uid found +0s … 0.321s

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

#49 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s

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

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

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

#53 linkCache_getLink no uid found +0.001s … 0.324s

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

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

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

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

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

#59 linkCache_getLink no uid found +0.001s … 0.326s

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

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

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

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

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

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

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

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

#68 linkCache_getLink no uid found +0s … 0.326s

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

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

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

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

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

#74 linkCache_getLink no uid found +0s … 0.326s

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

#76 linkCache_getLink no uid found +0s … 0.327s

#77 linkCache_getLink no uid found +0s … 0.327s

#78 linkCache_getLink no uid found +0.001s … 0.328s

#79 linkCache_getLink no uid found +0.001s … 0.329s

#80 linkCache_getLink no uid found +0s … 0.329s

#81 linkCache_getLink no uid found +0s … 0.329s

#82 linkCache_getLink no uid found +0s … 0.329s

#83 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s

#84 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.33s

#85 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s

#86 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.331s

#87 linkCache_getLink no uid found +0s . .. 0.331s

#88 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.332s

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

#90 linkCache_getLink no uid found +0.383s … 0.715s

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

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

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

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

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

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

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

#98 linkCache_getLink using $NBC_LINKCACHE +0s … 0.716s

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

#100 linkCache_getLink no uid found +0s … 0.716s

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

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

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

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

#105 linkCache_getLink no uid found +0.062s … 0.778s

#106 linkCache_getLink no uid found +0s … 0.778s

#107 linkCache_getLink using $NBC_LINKCACHE +0.009s … 0.787s

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

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

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

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

#112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s

#113 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s

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

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

#116 linkCache_getLink using $NBC_LINKCACHE +0s .. . 0.787s

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

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

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

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

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

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

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

#124 linkCache_getLink no uid found +0s … 0.787s

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

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

#127 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s

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

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

#130 linkCache_getLink no uid found +0s … 0.787s

#131 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.787s

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

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

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

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

#136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s

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

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

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

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

#141 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s

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

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

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

#145 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.787s

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

#147 linkCache_getLink no uid found +0s … 0.787s

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

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

#150 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s

#151 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s

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

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

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

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

#156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s

#157 linkCache_getLink no uid found +0s … 0.787s

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

#159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s

#160 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.787s

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

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

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

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

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

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

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

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

#169 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s

#170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s

#171 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s

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

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

#174 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.787s

#175 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s

#176 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s

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

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

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

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

#181 linkCache_getLink no uid found +0s … 0.787s

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

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

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

#185 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s

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

#187 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s

#188 linkCache_getLink using $NBC_LINKCACHE +0s .. . 0.787s

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

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

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

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

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

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

#195 linkCache_getLink no uid found +0s … 0.788s

#196 linkCache_getLink no uid found +0s … 0.788s

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

#198 linkCache_getLink using $NBC_LINKCACHE +0s … 0.788s

#199 linkCache_getLink using $NBC_LINKCACHE +0s … 0.788s

#200 linkCache_getLink using $NBC_LINKCACHE +0s … 0.788s

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

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

#203 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.788s

#204 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.788s

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

#206 linkCache_getLink using $NBC_LINKCACHE +0s … 0.788s

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

#208 linkCache_getLink no uid found +0s … 0.788s

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

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

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

#212 linkCache_getLink no uid found +0s … 0.788s

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

#214 linkCache_getLink using $NBC_LINKCACHE +0s … 0.788s

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

#216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.788s

#217 linkCache_getLink using $NBC_LINKCACHE +0s … 0. 788s

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

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

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

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

#222 linkCache_getLink no uid found +0.001s … 0.789s

#223 linkCache_getLink no uid found +0s … 0.789s

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

#225 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.79s

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

#227 linkCache_getLink using $NBC_LINKCACHE +0s … 0.79s

#228 linkCache_getLink using $NBC_LINKCACHE +0s … 0.79s

#229 linkCache_getLink using $NBC_LINKCACHE +0s … 0.79s

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

#231 linkCache_getLink no uid found +0s … 0.79s

#232 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.79s

#233 linkCache_getLink no uid found +0s … 0.79s

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

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

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

#237 linkCache_getLink no uid found +0s … 0.79s

#238 linkCache_getLink no uid found +0s … 0.79s

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

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

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

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

#243 linkCache_getLink using $NBC_LINKCACHE +0s … 0.79s

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

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

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

#247 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.79s

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

#249 linkCache_getLink no uid found +0s … 0.79s

#250 linkCache_getLink using $NBC_LINKCACHE +0s … 0.79s

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

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

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

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

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

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

#257 linkCache_getLink using $NBC_LINKCACHE +0s … 0.79s

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

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

#260 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.791s

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

#262 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.793s

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

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

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

#266 linkCache_getLink no uid found +0s … 0.793s

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

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

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

#270 linkCache_getLink using $NBC_LINKCACHE +0s … 0.793s

#271 linkCache_getLink using $NBC_LINKCACHE +0s … 0.793s

#272 linkCache_getLink using $NBC_LINKCACHE +0s … 0.793s

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

#274 linkCache_getLink using $NBC_LINKCACHE +0s … 0.793s

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

#276 linkCache_getLink no uid found +0s … 0. 793s

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

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

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

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

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

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

#283 linkCache_getLink using $NBC_LINKCACHE +0s … 0.793s

#284 linkCache_getLink using $NBC_LINKCACHE +0s … 0.793s

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

#286 linkCache_getLink using $NBC_LINKCACHE +0s … 0.793s

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

#288 linkCache_getLink no uid found +0s … 0.793s

#289 linkCache_getLink no uid found +0s … 0.793s

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

#291 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.793s

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

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

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

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

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

#297 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.793s

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

#299 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.795s

#300 linkCache_getLink using $NBC_LINKCACHE +0s … 0.795s

#301 linkCache_getLink using $NBC_LINKCACHE +0s … 0.795s

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

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

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

#305 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.795s

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

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

#308 linkCache_getLink no uid found +0s … 0.795s

#309 linkCache_getLink using $NBC_LINKCACHE +0s … 0.795s

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

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

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

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

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

#315 linkCache_getLink using $NBC_LINKCACHE +0s … 0.795s

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

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

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

#319 linkCache_getLink using $NBC_LINKCACHE +0s .. . 0.795s

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

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

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

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

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

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

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

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

#328 linkCache_getLink no uid found +0s … 0.795s

#329 linkCache_getLink no uid found +0s … 0.795s

#330 linkCache_getLink using $NBC_LINKCACHE +0s … 0.795s

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

#332 linkCache_getLink no uid found +0s … 0.795s

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

#334 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.795s

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

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

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

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

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

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

#341 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.796s

#342 linkCache_getLink no uid found +0s … 0.796s

#343 linkCache_getLink using $NBC_LINKCACHE +0s … 0.796s

#344 linkCache_getLink using $NBC_LINKCACHE +0s … 0.796s

#345 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.796s

#346 linkCache_getLink no uid found +0.001s … 0.797s

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

#348 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.797s

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

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

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

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

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

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

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

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

#357 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s

#358 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s

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

#360 linkCache_getLink no uid found +0s … 0.797s

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

#362 linkCache_getLink using $NBC_LINKCACHE +0s .. . 0.797s

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

#364 linkCache_getLink no uid found +0s … 0.797s

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

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

#367 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s

#368 linkCache_getLink no uid found +0s … 0.797s

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

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

#371 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s

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

#373 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s

#374 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s

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

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

#377 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.798s

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

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

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

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

#382 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s

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

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

#385 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s

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

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

#388 linkCache_getLink no uid found +0.001s … 0.798s

#389 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s

#390 linkCache_getLink using $NBC_LINKCACHE +0s … 0.798s

#391 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.798s

#392 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.799s

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

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

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

#396 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s

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

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

#399 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s

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

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

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

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

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

#405 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s

#406 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.801s

#407 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.802s

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

#409 linkCache_getLink using $NBC_LINKCACHE +0s … 0.802s

#410 linkCache_getLink using $NBC_LINKCACHE +0s … 0.802s

#411 linkCache_getLink using $NBC_LINKCACHE +0s … 0.802s

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

#413 linkCache_getLink using $NBC_LINKCACHE +0s … 0.802s

#414 linkCache_getLink using $NBC_LINKCACHE +0s … 0.802s

#415 linkCache_getLink using $NBC_LINKCACHE +0s … 0.802s

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

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

#418 linkCache_getLink using $NBC_LINKCACHE +0s … 0.802s

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

#420 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.802s

#421 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.803s

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

#423 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s

#424 linkCache_getLink using $NBC_LINKCACHE +0s … 0.803s

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

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

#427 linkCache_getLink using $NBC_LINKCACHE +0s … 0.804s

#428 linkCache_getLink no uid found +0s … 0.804s

#429 linkCache_getLink using $NBC_LINKCACHE +0s … 0.804s

#430 linkCache_getLink using $NBC_LINKCACHE +0s … 0.804s

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

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

#433 linkCache_getLink using $NBC_LINKCACHE +0s … 0.804s

#434 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.804s

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

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

#437 linkCache_getLink using $NBC_LINKCACHE +0s … 0.806s

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

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

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

#441 linkCache_getLink using $NBC_LINKCACHE +0s … 0.806s

#442 linkCache_getLink no uid found +0s … 0.806s

#443 linkCache_getLink using $NBC_LINKCACHE +0s … 0.806s

#444 linkCache_getLink using $NBC_LINKCACHE +0s … 0.806s

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

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

#447 linkCache_getLink using $NBC_LINKCACHE +0s … 0.806s

#448 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.806s

#449 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.807s

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

#451 linkCache_getLink no uid found +0.001s … 0.809s

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

#453 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.811s

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

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

#456 linkCache_getLink using $NBC_LINKCACHE +0s … 0.813s

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

#458 linkCache_getLink no uid found +0s … 0.813s

#459 linkCache_getLink using $NBC_LINKCACHE +0s … 0.813s

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

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

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

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

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

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

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

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

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

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

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

#471 linkCache_getLink no uid found +0s … 0.815s

#472 linkCache_getLink no uid found +0.001s … 0.816s

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

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

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

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

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

#478 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.817s

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

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

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

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

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

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

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

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

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

#488 linkCache_getLink no uid found +0s … 0.817s

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

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

#491 linkCache_getLink no uid found +0s … 0.818s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#509 linkCache_getLink using $NBC_LINKCACHE +0.059s … 0.882s

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

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

#512 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s

#513 linkCache_getLink no uid found +0s … 0.882s

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

#515 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s

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

#517 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s

#518 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s

#519 linkCache_getLink using $NBC_LINKCACHE +0.068s … 0.95s

#520 linkCache_getLink no uid found +0s … 0.95s

#521 linkCache_getLink using $NBC_LINKCACHE +0.015s … 0.965s

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

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

#524 linkCache_getLink no uid found +0s … 0.965s

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

#526 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.966s

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

#528 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.969s

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

#530 linkCache_getLink no uid found +0s … 0.969s

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

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

#533 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.969s

#534 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.97s

#535 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.972s

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

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

#538 linkCache_getLink no uid found +0s … 0.972s

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

#540 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.972s

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

#542 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.975s

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

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

#545 linkCache_getLink no uid found +0s … 0.975s

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

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

#548 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.975s

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

#550 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.977s

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

#552 linkCache_getLink no uid found +0s … 0.977s

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

#554 linkCache_getLink using $NBC_LINKCACHE +0s … 0.977s

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

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

#557 linkCache_getLink using $NBC_LINKCACHE +0s … 0.977s

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

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

#560 linkCache_getLink no uid found +0.001s … 0.978s

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

#562 linkCache_getLink using $NBC_LINKCACHE +0.002s . .. 0.98s

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

#564 linkCache_getLink no uid found +0s … 0.98s

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

#566 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.981s

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

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

#569 linkCache_getLink using $NBC_LINKCACHE +0s … 0.981s

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

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

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

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

#574 linkCache_getLink no uid found +0.001s … 0.982s

#575 linkCache_getLink no uid found +0.002s … 0.984s

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

#577 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.984s

#578 linkCache_getLink no uid found +0s … 0.984s

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

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

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

#582 linkCache_getLink using $NBC_LINKCACHE +0s … 0.984s

#583 linkCache_getLink using $NBC_LINKCACHE +0s … 0.984s

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

#585 linkCache_getLink no uid found +0s … 0.984s

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

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

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

#589 linkCache_getLink no uid found +0.001s … 0.985s

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

#591 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.985s

#592 linkCache_getLink no uid found +0. 002s … 0.987s

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

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

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

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

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

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

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

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

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

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

#603 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.988s

#604 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.988s

#605 linkCache_getLink no uid found +0.002s … 0.99s

#606 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.99s

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

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

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

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

#611 linkCache_getLink using $NBC_LINKCACHE +0s … 0.99s

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

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

#614 linkCache_getLink using $NBC_LINKCACHE +0s … 0.99s

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

#616 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.991s

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

#618 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.993s

#619 linkCache_getLink using $NBC_LINKCACHE +0s … 0.993s

#620 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.993s

#621 linkCache_getLink no uid found +0s … 0.993s

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

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

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

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

#626 linkCache_getLink using $NBC_LINKCACHE +0s … 0.993s

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

#628 linkCache_getLink using $NBC_LINKCACHE +0s … 0.993s

#629 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.994s

#630 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.995s

#631 linkCache_getLink no uid found +0.002s … 0.996s

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

#633 linkCache_getLink no uid found +0s … 0.996s

#634 linkCache_getLink using $NBC_LINKCACHE +0s … 0. 996s

#635 linkCache_getLink no uid found +0.001s … 0.997s

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

#637 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.999s

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

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

#640 linkCache_getLink using $NBC_LINKCACHE +0s … 0.999s

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

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

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

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

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

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

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

#648 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.999s

#649 linkCache_getLink using $NBC_LINKCACHE +0s … 0.999s

#650 linkCache_getLink using $NBC_LINKCACHE +0s … 0.999s

#651 linkCache_getLink using $NBC_LINKCACHE +0s … 0.999s

#652 linkCache_getLink using $NBC_LINKCACHE +0s … 0.999s

#653 linkCache_getLink using $NBC_LINKCACHE +0s … 0.999s

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

#655 linkCache_getLink using $NBC_LINKCACHE +0s … 0.999s

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

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

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

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

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

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

#662 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.999s

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

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

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

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

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

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

#669 linkCache_getLink using $NBC_LINKCACHE +0s … 0.999s

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

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

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

#673 linkCache_getLink no uid found +0s … 0.999s

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

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

#676 linkCache_getLink using $NBC_LINKCACHE +0s .. . 1s

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

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

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

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

#681 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

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

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

#684 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

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

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

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

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

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

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

#691 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1s

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

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

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

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

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

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

#698 linkCache_getLink no uid found +0s … 1s

#699 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#700 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#701 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#702 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#703 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#704 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#705 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#706 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1s

#707 linkCache_getLink no uid found +0s … 1s

#708 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#709 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#710 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#711 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#712 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#713 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#714 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#715 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#716 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#717 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#718 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#719 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#720 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#721 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1s

#722 linkCache_getLink no uid found +0s … 1s

#723 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#724 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#725 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#726 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#727 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#728 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#729 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#730 linkCache_getLink no uid found +0s … 1s

#731 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#732 linkCache_getLink using $NBC_LINKCACHE +0s … 1s

#733 linkCache_getLink using $NBC_LINKCACHE +0.001s … 1.001s

#734 linkCache_getLink no uid found +0s … 1.001s

#735 linkCache_getLink using $NBC_LINKCACHE +0s … 1.001s

#736 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.001s

#737 linkCache_getLink using $NBC_LINKCACHE +0s … 1.001s

#738 linkCache_getLink using $NBC_LINKCACHE +0s … 1.001s

#739 linkCache_getLink using $NBC_LINKCACHE +0s … 1.001s

#740 linkCache_getLink using $NBC_LINKCACHE +0s … 1.001s

#741 linkCache_getLink using $NBC_LINKCACHE +0s … 1.001s

#742 linkCache_getLink using $NBC_LINKCACHE +0s … 1.001s

#743 linkCache_getLink using $NBC_LINKCACHE +0s … 1.001s

#744 linkCache_getLink using $NBC_LINKCACHE +0s … 1.001s

#745 linkCache_getLink using $NBC_LINKCACHE +0s … 1.001s

#746 linkCache_getLink using $NBC_LINKCACHE +0s … 1.001s

#747 linkCache_getLink using $NBC_LINKCACHE +0s … 1.001s

#748 linkCache_getLink using $NBC_LINKCACHE +0s … 1.001s

#749 linkCache_getLink using $NBC_LINKCACHE +0.001s … 1.001s

#750 linkCache_getLink no uid found +0. 002s … 1.003s

#751 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#752 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#753 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#754 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#755 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#756 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#757 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#758 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#759 linkCache_getLink no uid found +0s … 1.003s

#760 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#761 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#762 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#763 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#764 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.003s

#765 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#766 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#767 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#768 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#769 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#770 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#771 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#772 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#773 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#774 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#775 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#776 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#777 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#778 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.003s

#779 linkCache_getLink using $NBC_LINKCACHE +0s … 1.003s

#780 linkCache_getLink no uid found +0s … 1.003s

#781 linkCache_getLink no uid found +0s … 1.003s

#782 linkCache_getLink using $NBC_LINKCACHE +0.001s … 1.004s

#783 linkCache_getLink using $NBC_LINKCACHE +0s … 1.004s

#784 linkCache_getLink using $NBC_LINKCACHE +0s … 1.004s

#785 linkCache_getLink using $NBC_LINKCACHE +0s … 1.004s

#786 linkCache_getLink using $NBC_LINKCACHE +0s … 1.004s

#787 linkCache_getLink using $NBC_LINKCACHE +0s … 1.004s

#788 linkCache_getLink using $NBC_LINKCACHE +0s … 1.004s

#789 linkCache_getLink using $NBC_LINKCACHE +0.001s … 1.005s

#790 linkCache_getLink no uid found +0.002s … 1.006s

#791 linkCache_getLink using $NBC_LINKCACHE +0s … 1.006s

#792 linkCache_getLink using $NBC_LINKCACHE +0s … 1. 006s

#793 linkCache_getLink using $NBC_LINKCACHE +0s … 1.006s

#794 linkCache_getLink using $NBC_LINKCACHE +0s … 1.006s

#795 linkCache_getLink using $NBC_LINKCACHE +0s … 1.006s

#796 linkCache_getLink using $NBC_LINKCACHE +0s … 1.006s

#797 linkCache_getLink using $NBC_LINKCACHE +0s … 1.006s

#798 linkCache_getLink using $NBC_LINKCACHE +0s … 1.006s

#799 linkCache_getLink using $NBC_LINKCACHE +0s … 1.006s

#800 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#801 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#802 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#803 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#804 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#805 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#806 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.007s

#807 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#808 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#809 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#810 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#811 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#812 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#813 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#814 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#815 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#816 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#817 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#818 linkCache_getLink no uid found +0s … 1.007s

#819 linkCache_getLink no uid found +0s … 1.007s

#820 linkCache_getLink using $NBC_LINKCACHE +0.001s … 1. 007s

#821 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#822 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#823 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#824 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#825 linkCache_getLink using $NBC_LINKCACHE +0s … 1.007s

#826 linkCache_getLink using $NBC_LINKCACHE +0s … 1.008s

#827 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.009s

#828 linkCache_getLink using $NBC_LINKCACHE +0s … 1.009s

#829 linkCache_getLink using $NBC_LINKCACHE +0s … 1.009s

#830 linkCache_getLink using $NBC_LINKCACHE +0s … 1.009s

#831 linkCache_getLink using $NBC_LINKCACHE +0s … 1.009s

#832 linkCache_getLink using $NBC_LINKCACHE +0s … 1.009s

#833 linkCache_getLink using $NBC_LINKCACHE +0s … 1.009s

#834 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.009s

#835 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#836 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#837 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#838 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#839 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#840 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#841 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#842 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#843 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#844 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#845 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#846 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#847 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#848 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#849 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.01s

#850 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#851 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#852 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#853 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#854 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#855 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#856 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#857 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#858 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#859 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#860 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#861 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#862 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#863 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#864 linkCache_getLink no uid found +0s . .. 1.01s

#865 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#866 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#867 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#868 linkCache_getLink no uid found +0s … 1.01s

#869 linkCache_getLink no uid found +0s … 1.01s

#870 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#871 linkCache_getLink using $NBC_LINKCACHE +0.001s … 1.01s

#872 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#873 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#874 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#875 linkCache_getLink using $NBC_LINKCACHE +0s … 1.01s

#876 linkCache_getLink using $NBC_LINKCACHE +0s … 1.011s

#877 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.013s

#878 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#879 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.013s

#880 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#881 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#882 linkCache_getLink no uid found +0s … 1.013s

#883 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#884 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#885 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#886 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#887 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#888 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#889 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#890 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#891 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#892 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#893 linkCache_getLink using $NBC_LINKCACHE +0s .. . 1.013s

#894 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#895 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#896 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#897 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#898 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#899 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#900 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#901 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#902 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#903 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#904 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#905 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#906 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#907 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.013s

#908 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#909 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#910 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#911 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#912 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#913 linkCache_getLink no uid found +0s … 1.013s

#914 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#915 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#916 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#917 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#918 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#919 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#920 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#921 linkCache_getLink using $NBC_LINKCACHE +0s .. . 1.013s

#922 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#923 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#924 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#925 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#926 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#927 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#928 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#929 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#930 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#931 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#932 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#933 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#934 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#935 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.013s

#936 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#937 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#938 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#939 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#940 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#941 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#942 linkCache_getLink no uid found +0s … 1.013s

#943 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#944 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#945 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#946 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#947 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#948 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#949 linkCache_getLink no uid found +0s … 1.013s

#950 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.013s

#951 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#952 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#953 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#954 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#955 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#956 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#957 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#958 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#959 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#960 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#961 linkCache_getLink using $NBC_LINKCACHE +0s … 1.013s

#962 linkCache_getLink no uid found +0.001s … 1.014s

#963 linkCache_getLink using $NBC_LINKCACHE +0s … 1.014s

#964 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.014s

#965 linkCache_getLink using $NBC_LINKCACHE +0s … 1.014s

#966 linkCache_getLink using $NBC_LINKCACHE +0s … 1.014s

#967 linkCache_getLink using $NBC_LINKCACHE +0s … 1.014s

#968 linkCache_getLink using $NBC_LINKCACHE +0s … 1.014s

#969 linkCache_getLink using $NBC_LINKCACHE +0s … 1.014s

#970 linkCache_getLink using $NBC_LINKCACHE +0s … 1.014s

#971 linkCache_getLink using $NBC_LINKCACHE +0s … 1.014s

#972 linkCache_getLink using $NBC_LINKCACHE +0s … 1.014s

#973 linkCache_getLink using $NBC_LINKCACHE +0s … 1.014s

#974 linkCache_getLink using $NBC_LINKCACHE +0s … 1.014s

#975 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.016s

#976 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#977 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#978 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.016s

#979 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#980 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#981 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#982 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#983 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#984 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#985 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#986 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#987 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#988 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#989 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#990 linkCache_getLink no uid found +0s … 1.016s

#991 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#992 linkCache_getLink using $NBC_LINKCACHE +0s .. . 1.016s

#993 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#994 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#995 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#996 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#997 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#998 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#999 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#1000 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#1001 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#1002 linkCache_getLink using $NBC_LINKCACHE +0s … 1.016s

#1003 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1004 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1005 linkCache_getLink no uid found +0s … 1.017s

#1006 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.017s

#1007 linkCache_getLink no uid found +0s … 1.017s

#1008 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1009 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1010 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1011 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1012 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1013 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1014 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1015 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1016 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1017 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1018 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1019 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1020 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.017s

#1021 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1022 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1023 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1024 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1025 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1026 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1027 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1028 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1029 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1030 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1031 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1032 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1033 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1034 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.017s

#1035 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1036 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1037 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1038 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1039 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1040 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1041 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1042 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1043 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1044 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1045 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1046 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1047 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1048 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.017s

#1049 linkCache_getLink no uid found +0s … 1.017s

#1050 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1051 linkCache_getLink no uid found +0s … 1.017s

#1052 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1053 linkCache_getLink no uid found +0s … 1.017s

#1054 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1055 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1056 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1057 linkCache_getLink using $NBC_LINKCACHE +0s … 1.017s

#1058 linkCache_getLink no uid found +0.001s … 1.018s

#1059 linkCache_getLink using $NBC_LINKCACHE +0s … 1.018s

#1060 linkCache_getLink using $NBC_LINKCACHE +0s … 1.018s

#1061 linkCache_getLink using $NBC_LINKCACHE +0s … 1.018s

#1062 linkCache_getLink using $NBC_LINKCACHE +0s … 1.018s

#1063 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.018s

#1064 linkCache_getLink using $NBC_LINKCACHE +0s … 1.018s

#1065 linkCache_getLink using $NBC_LINKCACHE +0s … 1.018s

#1066 linkCache_getLink using $NBC_LINKCACHE +0s … 1.018s

#1067 linkCache_getLink using $NBC_LINKCACHE +0s … 1.018s

#1068 linkCache_getLink using $NBC_LINKCACHE +0s … 1.018s

#1069 linkCache_getLink using $NBC_LINKCACHE +0s … 1.018s

#1070 linkCache_getLink using $NBC_LINKCACHE +0s … 1.018s

#1071 linkCache_getLink using $NBC_LINKCACHE +0s … 1.018s

#1072 linkCache_getLink using $NBC_LINKCACHE +0s … 1.018s

#1073 linkCache_getLink using $NBC_LINKCACHE +0s … 1.019s

#1074 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.021s

#1075 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1076 linkCache_getLink no uid found +0s … 1.021s

#1077 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.021s

#1078 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1079 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1080 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1081 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1082 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1083 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1084 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1085 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1086 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1087 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1088 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1089 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1090 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1091 linkCache_getLink no uid found +0s . .. 1.021s

#1092 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1093 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1094 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1095 linkCache_getLink no uid found +0s … 1.021s

#1096 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1097 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1098 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1099 linkCache_getLink using $NBC_LINKCACHE +0s … 1.021s

#1100 linkCache_getLink using $NBC_LINKCACHE +0s … 1.022s

#1101 linkCache_getLink no uid found +0s … 1.022s

#1102 linkCache_getLink using $NBC_LINKCACHE +0s … 1.022s

#1103 linkCache_getLink using $NBC_LINKCACHE +0s … 1.022s

#1104 linkCache_getLink using $NBC_LINKCACHE +0s … 1.022s

#1105 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.022s

#1106 linkCache_getLink using $NBC_LINKCACHE +0s … 1.022s

#1107 linkCache_getLink using $NBC_LINKCACHE +0s … 1.022s

#1108 linkCache_getLink using $NBC_LINKCACHE +0s … 1.022s

#1109 linkCache_getLink using $NBC_LINKCACHE +0s … 1.022s

#1110 linkCache_getLink using $NBC_LINKCACHE +0.004s … 1.026s

#1111 linkCache_getLink using $NBC_LINKCACHE +0s … 1.026s

#1112 linkCache_getLink using $NBC_LINKCACHE +0s … 1.026s

#1113 linkCache_getLink no uid found +0s … 1.026s

#1114 linkCache_getLink using $NBC_LINKCACHE +0s … 1.026s

#1115 linkCache_getLink using $NBC_LINKCACHE +0.001s … 1.027s

#1116 linkCache_getLink using $NBC_LINKCACHE +0s … 1.027s

#1117 linkCache_getLink using $NBC_LINKCACHE +0s … 1.027s

#1118 linkCache_getLink using $NBC_LINKCACHE +0s … 1.027s

#1119 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.027s

#1120 linkCache_getLink using $NBC_LINKCACHE +0s … 1.027s

#1121 linkCache_getLink using $NBC_LINKCACHE +0s … 1.027s

#1122 linkCache_getLink using $NBC_LINKCACHE +0s … 1.027s

#1123 linkCache_getLink no uid found +0s … 1.027s

#1124 linkCache_getLink no uid found +0s … 1.027s

#1125 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.03s

#1126 linkCache_getLink using $NBC_LINKCACHE +0s … 1.03s

#1127 linkCache_getLink using $NBC_LINKCACHE +0s … 1.03s

#1128 linkCache_getLink using $NBC_LINKCACHE +0s … 1.03s

#1129 linkCache_getLink no uid found +0s … 1.03s

#1130 linkCache_getLink using $NBC_LINKCACHE +0s … 1.03s

#1131 linkCache_getLink using $NBC_LINKCACHE +0s … 1.03s

#1132 linkCache_getLink using $NBC_LINKCACHE +0s … 1.03s

#1133 linkCache_getLink using $NBC_LINKCACHE +0s … 1.03s

#1134 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.03s

#1135 linkCache_getLink using $NBC_LINKCACHE +0s … 1.03s

#1136 linkCache_getLink using $NBC_LINKCACHE +0s … 1.03s

#1137 linkCache_getLink using $NBC_LINKCACHE +0s … 1.03s

#1138 linkCache_getLink no uid found +0s … 1.031s

#1139 linkCache_getLink no uid found +0s … 1.031s

#1140 linkCache_getLink no uid found +0.002s … 1.033s

#1141 linkCache_getLink using $NBC_LINKCACHE +0s … 1.033s

#1142 linkCache_getLink using $NBC_LINKCACHE +0.001s … 1.034s

#1143 linkCache_getLink no uid found +0s … 1.034s

#1144 linkCache_getLink using $NBC_LINKCACHE +0s … 1.034s

#1145 linkCache_getLink using $NBC_LINKCACHE +0s … 1.034s

#1146 linkCache_getLink using $NBC_LINKCACHE +0s … 1.034s

#1147 linkCache_getLink using $NBC_LINKCACHE +0s … 1.034s

#1148 linkCache_getLink using $NBC_LINKCACHE +0s … 1.034s

#1149 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.034s

#1150 linkCache_getLink no uid found +0s … 1.035s

#1151 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.037s

#1152 linkCache_getLink no uid found +0s … 1.037s

#1153 linkCache_getLink using $NBC_LINKCACHE +0.001s … 1.038s

#1154 linkCache_getLink no uid found +0s … 1.038s

#1155 linkCache_getLink using $NBC_LINKCACHE +0s … 1.038s

#1156 linkCache_getLink using $NBC_LINKCACHE +0s … 1.038s

#1157 linkCache_getLink using $NBC_LINKCACHE +0s … 1.038s

#1158 linkCache_getLink using $NBC_LINKCACHE +0s … 1.038s

#1159 linkCache_getLink using $NBC_LINKCACHE +0s … 1.038s

#1160 linkCache_getLink using $NBC_LINKCACHE +0s … 1.038s

#1161 linkCache_getLink no uid found +0s … 1.038s

#1162 linkCache_getLink no uid found +0.002s … 1.04s

#1163 linkCache_getLink using $NBC_LINKCACHE +0s … 1.04s

#1164 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.041s

#1165 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1166 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1167 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1168 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1169 linkCache_getLink no uid found +0s … 1.041s

#1170 linkCache_getLink no uid found +0s … 1.041s

#1171 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1172 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1173 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1174 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1175 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1176 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1177 linkCache_getLink no uid found +0s … 1.041s

#1178 linkCache_getLink using $NBC_LINKCACHE +0s … 1. 041s

#1179 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1180 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1181 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1182 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1183 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1184 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1185 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1186 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1187 linkCache_getLink no uid found +0.001s … 1.041s

#1188 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1189 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1190 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1191 linkCache_getLink no uid found +0s … 1.041s

#1192 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.041s

#1193 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1194 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1195 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1196 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1197 linkCache_getLink using $NBC_LINKCACHE +0s … 1.041s

#1198 linkCache_getLink using $NBC_LINKCACHE +0s … 1.042s

#1199 linkCache_getLink no uid found +0s … 1.042s

#1200 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.044s

#1201 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1202 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1203 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1204 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1205 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1206 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.044s

#1207 linkCache_getLink no uid found +0s … 1.044s

#1208 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1209 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1210 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1211 linkCache_getLink no uid found +0s … 1.044s

#1212 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1213 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1214 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1215 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1216 linkCache_getLink no uid found +0s … 1.044s

#1217 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1218 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1219 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1220 linkCache_getLink using $NBC_LINKCACHE +0s … 1. 044s

#1221 linkCache_getLink no uid found +0s … 1.044s

#1222 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1223 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1224 linkCache_getLink using $NBC_LINKCACHE +0s … 1.044s

#1225 linkCache_getLink no uid found +0.001s … 1.045s

#1226 linkCache_getLink using $NBC_LINKCACHE +0s … 1.045s

#1227 linkCache_getLink no uid found +0s … 1.045s

#1228 linkCache_getLink using $NBC_LINKCACHE +0s … 1.045s

#1229 linkCache_getLink using $NBC_LINKCACHE +0s … 1.045s

#1230 linkCache_getLink using $NBC_LINKCACHE +0s … 1.045s

#1231 linkCache_getLink using $NBC_LINKCACHE +0s … 1.045s

#1232 linkCache_getLink using $NBC_LINKCACHE +0s … 1.045s

#1233 linkCache_getLink using $NBC_LINKCACHE +0s … 1.045s

#1234 linkCache_getLink using $NBC_LINKCACHE +0s … 1. 045s

#1235 linkCache_getLink using $NBC_LINKCACHE +0s … 1.045s

#1236 linkCache_getLink using $NBC_LINKCACHE +0s … 1.045s

#1237 linkCache_getLink no uid found +0s … 1.045s

#1238 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.048s

#1239 linkCache_getLink using $NBC_LINKCACHE +0s … 1.048s

#1240 linkCache_getLink using $NBC_LINKCACHE +0s … 1.048s

#1241 linkCache_getLink no uid found +0s … 1.048s

#1242 linkCache_getLink no uid found +0s … 1.048s

#1243 linkCache_getLink using $NBC_LINKCACHE +0s … 1.048s

#1244 linkCache_getLink using $NBC_LINKCACHE +0s … 1.048s

#1245 linkCache_getLink using $NBC_LINKCACHE +0s … 1.048s

#1246 linkCache_getLink using $NBC_LINKCACHE +0s … 1.048s

#1247 linkCache_getLink using $NBC_LINKCACHE +0s … 1.048s

#1248 linkCache_getLink using $NBC_LINKCACHE +0s … 1. 048s

#1249 linkCache_getLink using $NBC_LINKCACHE +0s … 1.048s

#1250 linkCache_getLink using $NBC_LINKCACHE +0s … 1.048s

#1251 linkCache_getLink using $NBC_LINKCACHE +0s … 1.048s

#1252 linkCache_getLink using $NBC_LINKCACHE +0s … 1.048s

#1253 linkCache_getLink using $NBC_LINKCACHE +0s … 1.048s

#1254 linkCache_getLink using $NBC_LINKCACHE +0s … 1.048s

#1255 linkCache_getLink using $NBC_LINKCACHE +0s … 1.048s

#1256 linkCache_getLink using $NBC_LINKCACHE +0s … 1.048s

#1257 linkCache_getLink using $NBC_LINKCACHE +0.001s … 1.049s

#1258 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.051s

#1259 linkCache_getLink using $NBC_LINKCACHE +0s … 1.051s

#1260 linkCache_getLink using $NBC_LINKCACHE +0s … 1.051s

#1261 linkCache_getLink using $NBC_LINKCACHE +0s … 1.051s

#1262 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.051s

#1263 linkCache_getLink no uid found +0s … 1.051s

#1264 linkCache_getLink using $NBC_LINKCACHE +0s … 1.052s

#1265 linkCache_getLink using $NBC_LINKCACHE +0s … 1.052s

#1266 linkCache_getLink no uid found +0s … 1.052s

#1267 linkCache_getLink using $NBC_LINKCACHE +0s … 1.052s

#1268 linkCache_getLink using $NBC_LINKCACHE +0s … 1.052s

#1269 linkCache_getLink using $NBC_LINKCACHE +0s … 1.052s

#1270 linkCache_getLink using $NBC_LINKCACHE +0s … 1.052s

#1271 linkCache_getLink using $NBC_LINKCACHE +0s … 1.052s

#1272 linkCache_getLink using $NBC_LINKCACHE +0s … 1.052s

#1273 linkCache_getLink using $NBC_LINKCACHE +0s … 1.052s

#1274 linkCache_getLink using $NBC_LINKCACHE +0s … 1.052s

#1275 linkCache_getLink using $NBC_LINKCACHE +0s … 1.052s

#1276 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.052s

#1277 linkCache_getLink using $NBC_LINKCACHE +0.001s … 1.053s

#1278 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.055s

#1279 linkCache_getLink using $NBC_LINKCACHE +0s … 1.055s

#1280 linkCache_getLink using $NBC_LINKCACHE +0s … 1.055s

#1281 linkCache_getLink using $NBC_LINKCACHE +0s … 1.055s

#1282 linkCache_getLink using $NBC_LINKCACHE +0s … 1.055s

#1283 linkCache_getLink using $NBC_LINKCACHE +0s … 1.055s

#1284 linkCache_getLink using $NBC_LINKCACHE +0s … 1.055s

#1285 linkCache_getLink using $NBC_LINKCACHE +0s … 1.055s

#1286 linkCache_getLink using $NBC_LINKCACHE +0s … 1.055s

#1287 linkCache_getLink using $NBC_LINKCACHE +0s … 1.055s

#1288 linkCache_getLink using $NBC_LINKCACHE +0s … 1.055s

#1289 linkCache_getLink using $NBC_LINKCACHE +0s … 1.055s

#1290 linkCache_getLink no uid found +0s . .. 1.055s

#1291 linkCache_getLink no uid found +0s … 1.055s

#1292 linkCache_getLink using $NBC_LINKCACHE +0s … 1.055s

#1293 linkCache_getLink using $NBC_LINKCACHE +0s … 1.055s

#1294 linkCache_getLink using $NBC_LINKCACHE +0s … 1.055s

#1295 linkCache_getLink using $NBC_LINKCACHE +0s … 1.055s

#1296 linkCache_getLink no uid found +0s … 1.056s

#1297 linkCache_getLink using $NBC_LINKCACHE +0s … 1.056s

#1298 linkCache_getLink using $NBC_LINKCACHE +0s … 1.056s

#1299 linkCache_getLink using $NBC_LINKCACHE +0s … 1.056s

#1300 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.058s

#1301 linkCache_getLink using $NBC_LINKCACHE +0s … 1.058s

#1302 linkCache_getLink no uid found +0s … 1.058s

#1303 linkCache_getLink using $NBC_LINKCACHE +0s … 1.058s

#1304 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.058s

#1305 linkCache_getLink using $NBC_LINKCACHE +0s … 1.058s

#1306 linkCache_getLink using $NBC_LINKCACHE +0s … 1.058s

#1307 linkCache_getLink using $NBC_LINKCACHE +0s … 1.058s

#1308 linkCache_getLink no uid found +0s … 1.058s

#1309 linkCache_getLink using $NBC_LINKCACHE +0s … 1.058s

#1310 linkCache_getLink using $NBC_LINKCACHE +0s … 1.058s

#1311 linkCache_getLink using $NBC_LINKCACHE +0s … 1.058s

#1312 linkCache_getLink using $NBC_LINKCACHE +0s … 1.058s

#1313 linkCache_getLink using $NBC_LINKCACHE +0s … 1.058s

#1314 linkCache_getLink using $NBC_LINKCACHE +0s … 1.058s

#1315 linkCache_getLink using $NBC_LINKCACHE +0s … 1.058s

#1316 linkCache_getLink using $NBC_LINKCACHE +0s … 1.058s

#1317 linkCache_getLink using $NBC_LINKCACHE +0s … 1.058s

#1318 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.059s

#1319 linkCache_getLink no uid found +0s … 1.059s

#1320 linkCache_getLink using $NBC_LINKCACHE +0s … 1.059s

#1321 linkCache_getLink using $NBC_LINKCACHE +0s … 1.059s

#1322 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.061s

#1323 linkCache_getLink using $NBC_LINKCACHE +0s … 1.061s

#1324 linkCache_getLink using $NBC_LINKCACHE +0s … 1.062s

#1325 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.064s

#1326 linkCache_getLink using $NBC_LINKCACHE +0s … 1.064s

#1327 linkCache_getLink using $NBC_LINKCACHE +0s … 1.065s

#1328 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.067s

#1329 linkCache_getLink using $NBC_LINKCACHE +0.003s … 1.07s

#1330 linkCache_getLink using $NBC_LINKCACHE +0.003s … 1.072s

#1331 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.075s

#1332 linkCache_getLink using $NBC_LINKCACHE +0. 003s … 1.077s

#1333 linkCache_getLink using $NBC_LINKCACHE +0.003s … 1.08s

#1334 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1335 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1336 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1337 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1338 linkCache_getLink no uid found +0s … 1.08s

#1339 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1340 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1341 linkCache_getLink no uid found +0s … 1.08s

#1342 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1343 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1344 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1345 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1346 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.08s

#1347 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1348 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1349 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1350 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1351 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1352 linkCache_getLink no uid found +0s … 1.08s

#1353 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1354 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1355 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1356 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1357 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1358 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1359 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1360 linkCache_getLink using $NBC_LINKCACHE +0s .. . 1.08s

#1361 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1362 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1363 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1364 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1365 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1366 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1367 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1368 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1369 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1370 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1371 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1372 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1373 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1374 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.08s

#1375 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1376 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1377 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1378 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1379 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1380 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1381 linkCache_getLink no uid found +0s … 1.08s

#1382 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1383 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1384 linkCache_getLink using $NBC_LINKCACHE +0s … 1.08s

#1385 linkCache_getLink using $NBC_LINKCACHE +0s … 1.081s

#1386 linkCache_getLink using $NBC_LINKCACHE +0s … 1.081s

#1387 linkCache_getLink using $NBC_LINKCACHE +0s … 1.081s

#1388 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.081s

#1389 linkCache_getLink using $NBC_LINKCACHE +0s … 1.081s

#1390 linkCache_getLink using $NBC_LINKCACHE +0s … 1.081s

#1391 linkCache_getLink using $NBC_LINKCACHE +0.001s … 1.081s

#1392 linkCache_getLink using $NBC_LINKCACHE +0s … 1.081s

#1393 linkCache_getLink using $NBC_LINKCACHE +0s … 1.081s

#1394 linkCache_getLink using $NBC_LINKCACHE +0s … 1.081s

#1395 linkCache_getLink using $NBC_LINKCACHE +0s … 1.081s

#1396 linkCache_getLink using $NBC_LINKCACHE +0s … 1.081s

#1397 linkCache_getLink using $NBC_LINKCACHE +0s … 1.081s

#1398 linkCache_getLink no uid found +0s … 1.081s

#1399 linkCache_getLink using $NBC_LINKCACHE +0s … 1.081s

#1400 linkCache_getLink using $NBC_LINKCACHE +0s … 1.081s

#1401 linkCache_getLink using $NBC_LINKCACHE +0s … 1.081s

#1402 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.081s

#1403 linkCache_getLink using $NBC_LINKCACHE +0s … 1.081s

#1404 linkCache_getLink using $NBC_LINKCACHE +0s … 1.081s

#1405 linkCache_getLink no uid found +0s … 1.082s

#1406 linkCache_getLink no uid found +0.003s … 1.084s

#1407 linkCache_getLink no uid found +0s … 1.084s

#1408 linkCache_getLink using $NBC_LINKCACHE +0s … 1.084s

#1409 linkCache_getLink using $NBC_LINKCACHE +0s … 1.084s

#1410 linkCache_getLink using $NBC_LINKCACHE +0s … 1.084s

#1411 linkCache_getLink using $NBC_LINKCACHE +0s … 1.084s

#1412 linkCache_getLink using $NBC_LINKCACHE +0s … 1.084s

#1413 linkCache_getLink using $NBC_LINKCACHE +0s … 1.084s

#1414 linkCache_getLink using $NBC_LINKCACHE +0s … 1.084s

#1415 linkCache_getLink using $NBC_LINKCACHE +0s … 1.084s

#1416 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.084s

#1417 linkCache_getLink using $NBC_LINKCACHE +0s … 1.084s

#1418 linkCache_getLink using $NBC_LINKCACHE +0s … 1.084s

#1419 linkCache_getLink using $NBC_LINKCACHE +0s … 1.084s

#1420 linkCache_getLink using $NBC_LINKCACHE +0s … 1.084s

#1421 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.086s

#1422 linkCache_getLink using $NBC_LINKCACHE +0.003s … 1.089s

#1423 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1424 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1425 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1426 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1427 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1428 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1429 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1430 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.089s

#1431 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1432 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1433 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1434 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1435 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1436 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1437 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1438 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1439 linkCache_getLink no uid found +0s … 1.089s

#1440 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1441 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1442 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1443 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1444 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.089s

#1445 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1446 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1447 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1448 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1449 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1450 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1451 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1452 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1453 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1454 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1455 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1456 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1457 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1458 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.089s

#1459 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1460 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1461 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1462 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1463 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1464 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1465 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1466 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1467 linkCache_getLink no uid found +0s … 1.089s

#1468 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1469 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1470 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1471 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1472 linkCache_getLink no uid found +0s . .. 1.089s

#1473 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1474 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1475 linkCache_getLink using $NBC_LINKCACHE +0s … 1.089s

#1476 linkCache_getLink using $NBC_LINKCACHE +0.002s … 1.091s

#1477 linkCache_getLink using $NBC_LINKCACHE +0s … 1.091s

#1478 linkCache_getLink using $NBC_LINKCACHE +0s … 1.091s

#1479 linkCache_getLink using $NBC_LINKCACHE +0s … 1.091s

#1480 linkCache_getLink no uid found +0s … 1.091s

#1481 linkCache_getLink using $NBC_LINKCACHE +0s … 1.091s

#1482 linkCache_getLink using $NBC_LINKCACHE +0s … 1.091s

#1483 linkCache_getLink using $NBC_LINKCACHE +0s … 1.091s

#1484 linkCache_getLink using $NBC_LINKCACHE +0s … 1.091s

#1485 linkCache_getLink using $NBC_LINKCACHE +0s … 1.091s

#1486 linkCache_getLink using $NBC_LINKCACHE +0s . .. 1.091s

#1487 linkCache_getLink using $NBC_LINKCACHE +0.003s … 1.094s

#1488 linkCache_getLink using $NBC_LINKCACHE +0s … 1.094s

#1489 linkCache_getLink no uid found +0s … 1.094s

#1490 linkCache_getLink using $NBC_LINKCACHE +0s … 1.094s

#1491 linkCache_getLink using $NBC_LINKCACHE +0.001s … 1.095s

#1492 linkCache_getLink using $NBC_LINKCACHE +0s … 1.095s

#1493 linkCache_getLink using $NBC_LINKCACHE +0s … 1.095s

#1494 linkCache_getLink using $NBC_LINKCACHE +0s … 1.095s

#1495 linkCache_getLink using $NBC_LINKCACHE +0s … 1.095s

#1496 linkCache_getLink no uid found +0s … 1.095s

#1497 linkCache_getLink using $NBC_LINKCACHE +0s … 1.095s

#1498 linkCache_getLink no uid found +0.001s … 1.097s

#1499 linkCache_getLink using $NBC_LINKCACHE +0.003s … 1.099s

#1500 linkCache_getLink using $NBC_LINKCACHE +0. 003s … 1.102s

#1501 linkCache_getLink no uid found +0s … 1.102s

#1502 linkCache_getLink using $NBC_LINKCACHE +0s … 1.102s

#1503 linkCache_getLink using $NBC_LINKCACHE +0s … 1.102s

#1504 linkCache_getLink no uid found +0s … 1.103s

#1505 linkCache_getLink using $NBC_LINKCACHE +0s … 1.103s

#1506 linkCache_getLink using $NBC_LINKCACHE +0s … 1.103s

#1507 linkCache_getLink using $NBC_LINKCACHE +0s … 1.103s

#1508 linkCache_getLink using $NBC_LINKCACHE +0.001s … 1.104s

#1509 linkCache_getLink no uid found +0s … 1.104s

#1510 linkCache_getLink using $NBC_LINKCACHE +0s … 1.104s

#1511 linkCache_getLink using $NBC_LINKCACHE +0s … 1.104s

#1512 linkCache_getLink using $NBC_LINKCACHE +0s … 1.105s

#1513 linkCache_getLink no uid found +0s … 1.105s

#1514 linkCache_getLink using $NBC_LINKCACHE +0s .. . 1.105s

#1515 linkCache_getLink using $NBC_LINKCACHE +0s … 1.105s

#1516 linkCache_getLink using $NBC_LINKCACHE +0.003s … 1.108s

#1517 linkCache_getLink using $NBC_LINKCACHE +0s … 1.108s

#1518 linkCache_getLink no uid found +0s … 1.108s

#1519 linkCache_getLink using $NBC_LINKCACHE +0s … 1.108s

#1520 linkCache_getLink using $NBC_LINKCACHE +0.001s … 1.109s

#1521 linkCache_getLink using $NBC_LINKCACHE +0s … 1.109s

#1522 linkCache_getLink using $NBC_LINKCACHE +0s … 1.11s

#1523 min, max, avg, median took s +0.001s … 1.111s

#1524 return log +0.001s … 1.112s

Intel Core i5 8250U vs AMD Ryzen 5 3500U: performance comparison

VS

Intel Core i5 8250U

AMD Ryzen 5 3500U

We compared two 4-core laptop CPUs: the 1.6 GHz Intel Core i5 8250U against the 2.1 GHz AMD Ryzen 5 3500U. On this page, you’ll find out which processor has better performance in benchmarks, games and other useful information.

1. Review
2. Differences
3. Performance
4. Specs
5. Comments

Review

General overview and comparison of the processors

Single-Core Performance

Performance in single-threaded apps and benchmarks

Core i5 8250U

46

Ryzen 5 3500U

39

Performance

Measure performance when all cores are involved

Core i5 8250U

16

Ryzen 5 3500U

17

Power Efficiency

The efficiency score of electricity consumption

Core i5 8250U

58

Ryzen 5 3500U

59

NanoReview Final Score

Generic CPU rating

Core i5 8250U

36

Ryzen 5 3500U

36

Key Differences

What are the key differences between 3500U and 8250U

Advantages of Intel Core i5 8250U

• Consumes up to 57% less energy than the Ryzen 5 3500U – 15 vs 35 Watt
• 55% faster in a single-core Geekbench v5 test — 860 vs 554 points
• Has 2 MB larger L3 cache size
• Around 1. 74 GB/s (5%) higher theoretical memory bandwidth

Advantages of AMD Ryzen 5 3500U

• Newer — released 1-year and 5-months later
• More modern manufacturing process – 12 versus 14 nanometers
• 9% higher Turbo Boost frequency (3.7 GHz vs 3.4 GHz)

Benchmarks

Comparing the performance of CPUs in benchmarks

Cinebench R23 (Single-Core)

Core i5 8250U
+18%

905

Ryzen 5 3500U

766

Cinebench R23 (Multi-Core)

Core i5 8250U
+12%

3093

Ryzen 5 3500U

2763

Passmark CPU (Single-Core)

Core i5 8250U

1934

Ryzen 5 3500U
+3%

1997

Passmark CPU (Multi-Core)

Core i5 8250U

5970

Ryzen 5 3500U
+19%

7105

Geekbench 5 (Single-Core)

Core i5 8250U
+55%

865

Ryzen 5 3500U

557

Geekbench 5 (Multi-Core)

Core i5 8250U

2878

Ryzen 5 3500U

2890

▶️ Submit your Cinebench R23 result

By purchasing through links on this site, we may receive a commission from Amazon. This does not affect our assessment methodology.

Specifications

Full technical specification of Intel Core i5 8250U and AMD Ryzen 5 3500U

General

Vendor	Intel	AMD
Released	August 21, 2017	January 6, 2019
Type	Laptop	Laptop
instruction set	x86-64	x86-64
Codename	Kaby Lake R	Picasso
Model number	i5-8250U	—
Socket	BGA-1356	FP5
Integrated GPU	UHD Graphics 620	Radeon Vega 8

Performance

Cores	4	4
Threads	8	8
Base Frequency	1. 6 GHz	2.1 GHz
Turbo Boost Frequency	3.4 GHz	3.7 GHz
Bus frequency	100 MHz	100 MHz
Multiplier	16x	21x
Bus Bandwidth	4 GT/s	—
L1 Cache	64K (per core)	96K (per core)
L2 Cache	256K (per core)	512K (per core)
L3 Cache	6MB (shared)	4MB (shared)
Unlocked Multiplier	No	No

Transistors	—	4.9 billions
Fabrication process	14 nm	12 nm
TDP	15 W	12-35 W
Max. temperature	100°C	105°C

Integrated Graphics	Intel UHD Graphics 620	Radeon Vega 8
GPU Base Clock	300 MHz	300 MHz
GPU Boost Clock	1100 MHz	1200 MHz
Shading Units	192	512
TMUs	24	32
ROPs	3	8
Execution Units	24	8
TGP	15 W	65 W
Max. Resolution	4096×2304 — 60 Hz	3840×2160 — 60 Hz

iGPU FLOPS

Core i5 8250U

0.38 TFLOPS

Ryzen 5 3500U

1.13 TFLOPS

Memory support

Memory types	DDR4-2400, LPDDR3-2133	DDR4-2400
Memory Size	32 GB	32 GB
Max. Memory Channels	2	2
Max. Memory Bandwidth	37.5 GB/s	35.76 GB/s
ECC Support	No	Yes

Official site	Intel Core i5 8250U official page	AMD Ryzen 5 3500U official page
PCI Express Version	3.0	3.0
PCI Express Lanes	12	12
Extended instructions	SSE4.1, SSE4.2, AVX-2	—

Cast your vote

Choose between two processors

Core i5 8250U

64 (34.8%)

Ryzen 5 3500U

120 (65.2%)

Total votes: 184

ompetitors

1.
Intel Core i3 1115G4 and Intel Core i5 8250U

2.
AMD Ryzen 5 5500U and Intel Core i5 8250U

3.
Apple M1 and Intel Core i5 8250U

4.
AMD Ryzen 3 5300U and Intel Core i5 8250U

5.
Intel Core i5 1135G7 and AMD Ryzen 5 3500U

6.
Intel Core i3 1115G4 and AMD Ryzen 5 3500U

7.
AMD Ryzen 5 5500U and AMD Ryzen 5 3500U

8.
Intel Core i5 10210U and AMD Ryzen 5 3500U

9.
AMD Ryzen 3 5300U and AMD Ryzen 5 3500U

Intel Core i5-8250U vs AMD Ryzen 5 3500U

Intel Core i5-8250U vs AMD Ryzen 5 3500U

Comparison of the technical characteristics between the processors, with the Intel Core i5-8250U on one side and the AMD Ryzen 5 3500U on the other side. The first is dedicated to the notebook sector, It has 4 cores, 8 threads, a maximum frequency of 3,4GHz. The second is used on the mainstream-class laptop segment, it has a total of 4 cores, 8 threads, its turbo frequency is set to 3,7 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		Intel Core i5-8250U				AMD Ryzen 5 3500U
Market (main)		Notebook				Mainstream-class laptop
ISA		x86-64 (64 bit)				x86-64 (64 bit)
Microarchitecture		Kaby Lake				Zen+
Core name		Kaby Lake Refresh				Picasso
Family		Core i5-8000				Ryzen 5 3000
Part number(s), S-Spec		FJ8067703282221, SR3LA				YM3500C4T4MFG
Release date		Q3 2017				Q1 2019
Lithography		14 nm+				12 nm
Transistors		—				4. 940.000.000
Cores		4				4
Threads		8				8
Base frequency		1,6 GHz				2,1 GHz
Turbo frequency		3,4 GHz				3,7 GHz
Cache memory		6 MB				4 MB
Max memory capacity		32 GB				32 GB
Memory types		DDR4-2400, LPDDR3-2133				DDR4-2400
Max # of memory channels		2				2
Max memory bandwidth		37,5 GB/s				35,76 GB/s
Max PCIe lanes		12				12
TDP		15 W				15 W
GPU integrated graphics		Intel UHD Graphics 620 (Kaby Lake)				AMD Radeon Vega 8 (Picasso)
GPU cores		—				8
GPU execution units		24				—
GPU shading units		192				512
GPU base clock		300 MHz				300 MHz
GPU boost clock		1100 MHz				1200 MHz
GPU FP32 floating point		441,6 GFLOPS				1. 229 GFLOPS
Socket		BGA1356				FP5
Maximum temperature		100°C				105°C
CPU-Z single thread		381				366
CPU-Z multi thread		1.979				1.991
Cinebench R15 single thread		146				140
Cinebench R15 multi-thread		538				658
Cinebench R23 single thread		831				784
Cinebench R23 multi-thread		3.182				3. 451
PassMark single thread		1.931				2.112
PassMark CPU Mark		5.930				7.915
(Windows 64-bit) Geekbench 4 single core		3.718				3.218
(Windows 64-bit) Geekbench 4 multi-core		11.054				9.297
(SGEMM) GFLOPS performance		163,2 GFLOPS				117,3 GFLOPS
(Multi-core / watt performance) Performance / watt ratio		737 pts / W				620 pts / W
Amazon
eBay

Note: Commissions may be earned from the links above.

We can better compare what are the technical differences between the two processors.

Price: For technical reasons, we cannot currently display a price less than 24 hours, or a real-time price. This is why we prefer for the moment not to show a price. You should refer to the respective online stores for the latest price, as well as availability.

We see that the two processors have an equivalent number of cores, the turbo frequency of AMD Ryzen 5 3500U is bigger, that their respective TDP are of the same order. The AMD Ryzen 5 3500U was started more recently.

Performances :

Performance comparison between the two processors, for this we consider the results generated on benchmark software such as Geekbench 4.

	CPU-Z — Multi-thread & single thread score
AMD Ryzen 5 3500U	366 1. 991
Intel Core i5-8250U	381 1.979

In single core, the difference is 4%. In multi-core, the difference in terms of gap is 1%.

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 Ryzen 5 3500U	140 658
Intel Core i5-8250U	146 538

In single core, the difference is 4%. In multi-core, the difference in terms of gap is 22%.

Note: Commissions may be earned from the links above. These scores are only an
average of the performances got with these processors, you may get different results.

Cinebench R15 evaluates the performance of CPU calculations by restoring a photorealistic 3D scene. The scene has 2,000 objects, 300,000 polygons, uses sharp and fuzzy reflections, bright areas, shadows, procedural shaders, antialiasing, and so on. The faster the rendering of the scene is created, the more powerful the PC is, with a high number of points.

	Cinebench R23 — Multi-thread & single thread score
AMD Ryzen 5 3500U	784 3.451
Intel Core i5-8250U	831 3.182

In single core, the difference is 6%. In multi-core, the difference in terms of gap is 8%.

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 R23 is cross-platform testing software that allows you to assess the hardware capabilities of a device such as a computer, tablet, server. This version of Cinebench takes into account recent developments in processors with multiple cores and the latest improvements in rendering techniques. The evaluation is ultimately even more relevant. The test scene contains no less than 2,000 objects and more than 300,000 polygons in total.

	PassMark — CPU Mark & single thread
AMD Ryzen 5 3500U	2.112 7.915
Intel Core i5-8250U	1.931 5. 930

In single core, the difference is 9%. In multi-core, the difference in terms of gap is 33%.

Note: Commissions may be earned from the links above. These scores are only an
average of the performances got with these processors, you may get different results.

PassMark is a benchmarking software that performs several performance tests including prime numbers, integers, floating point, compression, physics, extended instructions, encoding, sorting. The higher the score is, the higher is the device capacity.

On Windows 64-bit:

	Geekbench 4 — Multi-core & single core score — Windows 64-bit
Intel Core i5-8250U	3.718 11.054
AMD Ryzen 5 3500U	3.218 9.297

In single core, the difference is 16%. In multi-core, the differential gap is 19%.

On Linux 64-bit:

	Geekbench 4 — Multi-core & single core score — Linux 64-bit
Intel Core i5-8250U	3.735 8.808
AMD Ryzen 5 3500U	2.765 6.011

In single core, the difference is 35%. In multi-core, the differential gap is 47%.

On Android 64-bit:

	Geekbench 4 — Multi-core & single core score — Android 64-bit
Intel Core i5-8250U	4.221 13.834
AMD Ryzen 5 3500U	3.112 7.308

In single core, the difference is 36%. In multi-core, the differential gap is 89%.

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.

Equivalence:

Intel Core i5-8250U AMD equivalentAMD Ryzen 5 3500U Intel equivalent

See also:

AMD Ryzen 5 3500AMD Ryzen 5 3500CAMD Ryzen 5 3500X

Intel Core i5-8250U vs. AMD Ryzen 5 3500U

Intel Core i5-8250U

The Intel Core i5-8250U operates with 4 cores and 8 CPU threads. It run at 3.40 GHz base 2.30 GHz all cores while the TDP is set at 15 W. The processor is attached to the BGA 1356 CPU socket. This version includes 6.00 MB of L3 cache on one chip, supports 2 memory channels to support DDR4-2400 SO-DIMM RAM and features 3.0 PCIe Gen 12 lanes. Tjunction keeps below — degrees C. In particular, Kaby Lake U Refresh Architecture is enhanced with 14 nm technology and supports VT-x, VT-x EPT, VT-d. The product was launched on Q3/2017

AMD Ryzen 5 3500U

The AMD Ryzen 5 3500U operates with 4 cores and 8 CPU threads. It run at 3.70 GHz base 3.00 GHz all cores while the TDP is set at 15 W.The processor is attached to the FP5 CPU socket. This version includes 4.00 MB of L3 cache on one chip, supports 2 memory channels to support DDR4-2400 RAM and features 3.0 PCIe Gen 12 lanes. Tjunction keeps below 105 °C degrees C. In particular, Picasso (Zen+) Architecture is enhanced with 12 nm technology and supports AMD-V, SVM. The product was launched on Q1/2019

Intel Core i5-8250U

AMD Ryzen 5 3500U

Compare Detail

1. 60 GHz	Frequency	2.10 GHz
4	Cores	4
3.40 GHz	Turbo (1 Core)	3.70 GHz
2.30 GHz	Turbo (All Cores)	3.00 GHz
Yes	Hyperthreading	Yes
No	Overclocking	No
normal	Core Architecture	normal
Intel UHD Graphics 620	GPU	AMD Radeon Vega 8 Graphics
1.10 GHz	GPU (Turbo)	No turbo
14 nm	Technology	12 nm
1.10 GHz	GPU (Turbo)	No turbo
12	DirectX Version	12
3	Max. displays	3
DDR4-2400 SO-DIMM	Memory	DDR4-2400
2	Memory channels	2
	Max memory
No	ECC	Yes
—	L2 Cache	—
6. 00 MB	L3 Cache	4.00 MB
3.0	PCIe version	3.0
12	PCIe lanes	12
14 nm	Technology	12 nm
BGA 1356	Socket	FP5
15 W	TDP	15 W
VT-x, VT-x EPT, VT-d	Virtualization	AMD-V, SVM
Q3/2017	Release date	Q1/2019
Show more data		Show more data

Cinebench R23 (Single-Core)

Cinebench R23 is the successor of Cinebench R20 and is also based on the Cinema 4 Suite. Cinema 4 is a worldwide used software to create 3D forms. The single-core test only uses one CPU core, the amount of cores or hyperthreading ability doesn’t count.

Cinebench R23 (Multi-Core)

Cinebench R23 is the successor of Cinebench R20 and is also based on the Cinema 4 Suite. Cinema 4 is a worldwide used software to create 3D forms. The multi-core test involves all CPU cores and taks a big advantage of hyperthreading.

Cinebench R20 (Single-Core)

Cinebench R20 is the successor of Cinebench R15 and is also based on the Cinema 4 Suite. Cinema 4 is a worldwide used software to create 3D forms. The single-core test only uses one CPU core, the amount of cores or hyperthreading ability doesn’t count.

Cinebench R20 (Multi-Core)

Cinebench R20 is the successor of Cinebench R15 and is also based on the Cinema 4 Suite. Cinema 4 is a worldwide used software to create 3D forms. The multi-core test involves all CPU cores and taks a big advantage of hyperthreading.

Cinebench R15 (Single-Core)

Cinebench R15 is the successor of Cinebench 11.5 and is also based on the Cinema 4 Suite. Cinema 4 is a worldwide used software to create 3D forms. The single-core test only uses one CPU core, the amount of cores or hyperthreading ability doesn’t count.

Cinebench R15 (Multi-Core)

Cinebench R15 is the successor of Cinebench 11. 5 and is also based on the Cinema 4 Suite. Cinema 4 is a worldwide used software to create 3D forms. The multi-core test involves all CPU cores and taks a big advantage of hyperthreading.

Geekbench 5, 64bit (Single-Core)

Geekbench 5 is a cross plattform benchmark that heavily uses the systems memory. A fast memory will push the result a lot. The single-core test only uses one CPU core, the amount of cores or hyperthreading ability doesn’t count.

Geekbench 5, 64bit (Multi-Core)

Geekbench 5 is a cross plattform benchmark that heavily uses the systems memory. A fast memory will push the result a lot. The multi-core test involves all CPU cores and taks a big advantage of hyperthreading.

iGPU — FP32 Performance (Single-precision GFLOPS)

The theoretical computing performance of the internal graphics unit of the processor with simple accuracy (32 bit) in GFLOPS. GFLOPS indicates how many billion floating point operations the iGPU can perform per second.

Blender 2.81 (bmw27)

Blender is a free 3D graphics software for rendering (creating) 3D bodies, which can also be textured and animated in the software. The Blender benchmark creates predefined scenes and measures the time (s) required for the entire scene. The shorter the time required, the better. We selected bmw27 as the benchmark scene.

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-8250U		AMD Ryzen 5 3500U
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 Ryzen 5 3500U vs Intel Core i5-8250U

Laptoppages

July 12, 2022

SaveSavedRemoved 0

AMD Ryzen 5 3500U vs Intel Core i5-8250U? You might be wondering which processor is best among these for you. from a price point of view devices having this processor are competitors of each other. Intel’s i5 processor is designed for mid-range gamer, and programmers. Similarly, AMD’s has made Ryzen 5 for mid range computing.

Hence these two ultra technology processors are making confusion among the buyer. Here i have tried to compare them.

Comparison between AMD Ryzen 5 3500U vs Intel Core i5-8250U

Features	Intel I5 processor 8th gen	AMD Ryzen 5 3500
CPU Speed	1.6 GHz each with 4 core	2.1 GHz each with 4 core
Integrated GPU speed	300MHz	1200 MHz
Cache Memory Size L2	1 MB	2 MB
Turbo Boost Speed	3. 4 GHz	3.7 GHz
Cache Memory size L1	256KB	384 KB
Cache memory L3	6 MB	4 MB
Singer Core performance	771	701
CPU Semiconductor Size	14nm	12nm

From the above comparison we can see the AMD Ryzen 5 has more clock speed in compared to intel. Both the processor have 4 core and 8 thread. As we know CPU speed shows that how many cycles can complete in a second. Clearly from the above AMD has beaten Intel.

Both AMD Ryzen 5 and Intel i5 CPU have 15 watt TDP. TDP is the thermal design power. Lesser will be the power consumption in lesser TDP. TDP is the power consumption at a critical load.

The tubo boost performance of both processors is 3.7 GHz for AMD and 3.4 GHz for Intel. That AMD performed well for Turbo boost performance.

Earlier AMD processors are not so good, but now a day AMD has changed the game. In some cases, AMD processors performed better than Intel processors. AMD 5th Generation processors are power efficient and a better player than Intel in comparison to the price.

Some AMD processors are costlier than Intel processor models.

Both the processor comes with integrated graphics. GPU speed of AMD is 900 MHz higher than intel. For gaming, AMD processor is the winner. With it, we can play mid-range games like CS GO, far Cry 4, and Asphalt 9 smoothly without any lag at high settings.

I have seen one of my friends was playing call of duty without any issue.

L1, L2 Cache memory of AMD Ryzen 5 is bigger in size than Intel i5 while L3 cache memory is bigger in Intel processor.

The size of CPU semiconductor is less in AMD processor compared to Intel. 12 nm in AMD and 14 nm in intel. So power consumption in AMD processors is less in comparison to intel.

Lesser the CPU size, less power consumption, and speed in communication between transistors and electronic components in the CPU.

For example in an office or bank employees’ seats are made by a small cabin with a thin wall separator. if the wall will be short in height or thin then file movement or communication between the employees will be fast.

Similarly, communication between components of CPU will be fast in a 12nm devices.

You can check benchmark results for multi-core performance AMD is the winner. In singer core performance Intel is the winner. Companies like Greekbench 5 are testing CPU performance at multi-core and sing core.

Conclusion is that over Intel i5 Processor, the winner is AMD Ryzen 5.

Buy AMD Ryzen 5

Related Post

Best Ryzen 5 laptop under 40000

Previous

best ryzen 5 laptop under 40000

Next

HP Laptop 15S-Eq2143Au review

AMD Ryzen 5 3500U vs Intel Core i5-8250U: What is the difference?

54 BALLLA

AMD Ryzen 5 3500U

49 BALLLA

Intel Core i5-8250U

VS

64 Facts compared to

AMD Ryzen 5 3500U

Intel Core I5-8250U 9000U 9000U 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u, Intel Core i5-8250U?

• 31.25% higher CPU speed?
  4 x 2.1GHz vs 4 x 1.6GHz
• GPU frequency 900MHz more?
  1200MHz vs 300MHz
• Semiconductor size 2nm smaller?
  12nm vs 14nm
• 1MB more L2 cache?
  2MB vs 1MB
• 19. 83% higher PassMark score?
  7119 vs 5941
• 0.3GHz higher turbo clock speed?
  3.7GHz vs 3.4GHz
• 128KB more L1 cache?
  384KB vs 256KB
• 0.25MB/core more L2 cache per core?
  0.5MB/core vs 0.25MB/core

• 2MB more L3 cache?
  6MB vs 4MB
• 9.05% higher single core Geekbench 5 result?
  771 vs 707
• 0.5MB/core more L3 cache per core?
  1.5MB/core vs 1MB/core
• 18.3 higher performance per watt?
  188.0 vs 169.7
• 16 more GPU execution units?
  24 vs 8

Which comparisons are the most popular?

AMD RYZEN 5 3500U

VS

Intel Core i5-10210U

Intel Core i5-8250U

VS

Intel Core i3-1115G4

AMD Ryzen 5 3500U

9000 VS 9000 ITEL 9000 ITEL

Intel Core i5-8250U

vs

Intel Core i3-1005G1

AMD RYZEN 5 3500U

VS

Intel Core i3-10110u

Intel Core i5-8250U

VS

AMD Ryzen 3 2200u

AMD RYZEN 5 3500U

VS

9000 INTEL CORE CORETEL CORE CORETEL CORE IS Intel Core i5-8250u

VS

Intel Core i7-6500U

AMD Ryzen 5 3500U

AMD Ryzen 5 5500u

Intel Core I5-8250U

AMD RYEEN 3200UE AMD RYEN 5 3500U

VS

AMD Ryzen 3 5300U

Intel Core i5-8250U

VS

AMD Ryzen 5 2500u

AMD Ryzen 5 3500u

VS

Intel Core I5-8265U

vs

AMD RYZEN 5 5500U

AMD Ryzen 5 3500u

VS

Intel Core i5-1035g1

Intel Core i5-8250U

VS

-0003

AMD Ry

AMD Ry

AMD RYUS

AMD RYZEN 7 3700U

Intel Core i5-8250u 9000u

VS

Intel Core i5-7200u

Costs

Reviews Users

9000 AMISE 9 SUSEDERS 5 3500U 9000 9000 Reviews Users

5 User reviews0003

5 Reviews of users

Functions

Price and quality ratio

8. 8 /10

8 VOTES

7.4 /10

5 VOTES

9000 9000 9000 9

6.6 /10

5 Votes

performance

8.6 /10

8 Votes

7.4 /10

5 Votes

003

9.3 /10

8 Votes

8.8 /10

5 Votes 9000

1.CPU speed

4 x 2.1GHz

4 x 1.6GHz

CPU speed indicates how many processing cycles per second a processor can perform, considering all its cores (processors). It is calculated by adding the clock speeds of each core or, in the case of multi-core processors, each group of cores.

2nd processor thread

More threads result in better performance and better multitasking.

3.speed turbo clock

3.7GHz

3.4GHz

When the processor is running below its limits, it can jump to a higher clock speed to increase performance.

4. Has an unlocked multiplier

✖AMD Ryzen 5 3500U

✖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

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.core L3

1MB/core

1.5MB/core

More data can be stored in the L3 scratchpad for access by each processor core.

Memory

1.RAM speed

2400MHz

2400MHz

Can support faster memory which speeds up system performance.

2.max memory bandwidth

35.76GB/s

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.maximum memory capacity

Maximum memory capacity (RAM).

6.bus baud rate

Unknown. Help us offer a price. (AMD Ryzen 5 3500U)

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

7.Supports memory troubleshooting code

✖AMD Ryzen 5 3500U

✖Intel Core i5-8250U

Memory error recovery code can detect and repair data corruption. It is used when necessary to avoid distortion, such as in scientific computing or when starting a server.

8.eMMC version

Unknown. Help us offer a price. (AMD Ryzen 5 3500U)

Unknown. Help us offer a price. (Intel Core i5-8250U)

The newer version of eMMC — built-in flash memory card — speeds up the memory interface, has a positive effect on device performance, for example, when transferring files from a computer to internal memory via USB.

9.bus frequency

Unknown. Help us offer a price. (AMD Ryzen 5 3500U)

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 test measures processor performance using multi-threading.

2. PassMark result (single)

This test measures processor performance using a thread of execution.

3.Geekbench 5 result (multi-core)

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

4.Cinebench R20 result (multi-core)

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)

638.36seconds

771.41seconds

The Blender test (bmw27) measures CPU performance by rendering a 3D scene. More powerful processors can render a scene in a shorter time.

8.Blender result (classroom)

1920.96seconds

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.

Features

1.uses multithreading

✔AMD Ryzen 5 3500U

✔Intel Core i5-8250U

Multithreading technology (such as Intel’s Hyperthreading or AMD’s Simultaneous Multithreading) provides better performance by dividing each physical processor core into logical cores, also known as threads. Thus, each core can run two instruction streams at the same time.

2. Has AES

✔AMD Ryzen 5 3500U

✔Intel Core i5-8250U

AES is used to speed up encryption and decryption.

3. Has AVX

✔AMD Ryzen 5 3500U

✔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 Ryzen 5 3500U

✔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 Ryzen 5 3500U)

Unknown. Help us offer a price. (Intel Core i5-8250U)

NEON provides faster media processing such as MP3 listening.

7. Has MMX

✔AMD Ryzen 5 3500U

✔Intel Core i5-8250U

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

8.Has TrustZone

✖AMD Ryzen 5 3500U

✖Intel Core i5-8250U

Technology is integrated into the processor to ensure device security when using features such as mobile payments and video streaming through Digital Rights Management (DRM) ).

9.interface width

Unknown. Help us offer a price. (AMD Ryzen 5 3500U)

Unknown. Help us offer a price. (Intel Core i5-8250U)

The processor can decode more instructions per clock (IPC), which means the processor performs better

Price comparison

Cancel

Which CPUs are better?

Intel Core i5 8250U vs AMD Ryzen 5 3500U:

performance comparison

VS

Intel Core i5 8250U

AMD Ryzen 5 3500U

Which is better: Intel Core i5 8250U at 1. 6 GHz (with Turbo Boost up to 3.4) or AMD Ryzen 5 3500U at 2.1 GHz (with Turbo Core up to 3.7)? To find out, read our comparative testing of these 4-core laptop processors in popular benchmarks, games and heavy applications.

1. Overview
2. Differences
3. Performance
4. Features
5. Comments

Overview

Overview and comparison of the main metrics from NanoReview

Single -flow performance

Rating in tests using one kernel

Core i5 8250u

46

Ryzen 5 3500u

39

Multi -flow performance

Tests in benchmarks, where all nucleus

Core Core 85000 16

Ryzen 5 3500U

17

Energy efficiency

Efficiency of energy consumption by chip

Core i5 8250u 9000u

58

Ryzen 5 3500u

9000

Key differences

What are the main differences between 3500U and 8250U

Reasons to choose Intel Core i5 8250U

• 57% lower than Ryzen 5 3500U peak power consumption — 15 vs 35 Watts
• 55% faster in single core Geekbench v5 — 860 and 554 points
• Has 2MB more L3 cache

At 1 /c (5%) higher maximum memory bandwidth

Reasons to choose AMD Ryzen 5 3500U

• Appeared 1 year and 5 months later than the rival% higher frequency in Turbo Boost (3. 7 GHz vs 3.4 GHz)

Benchmark tests

Compare the results of processor tests in benchmarks

Cinebench R23 (single core)

Core i5 8250U
+18%

905

Ryzen 5 3500U

766

Cinebench R23 (multi-core)

Core i5 8250U
+12%

3093

Ryzen 5 3500U

2763

Passmark CPU (single core)

Core i5 8250U

1934

Ryzen 5 3500U
+3%

1997

Passmark CPU (multi-core)

Core i5 8250U

5970

Ryzen 5 3500U
+19%

7105

Geekbench 5 (single core)

Core i5 8250U
+55%

865

Ryzen 5 3500U

557

Geekbench 5 (multi -core)

Core i5 8250u

2878

Ryzen 5 3500U

2890

▶️ Add your score to Cinebench R23

Specifications

List of full specifications for Intel Core i5 8250U and AMD Ryzen 5 3500U

General information

Manufacturer	Intel	AMD
Release date	August 21, 2017	January 6, 2019
Type	For laptop	For laptop
Instruction set architecture	x86-64	x86-64
Codename	Kaby Lake R	Picasso
Model number	i5-8250U	—
Socket	BGA-1356	FP5
Integrated graphics	UHD Graphics 620	Radeon Vega 8

Performance

Number of cores	4	4
Number of threads	8	8
Frequency	1. 6 GHz	2.1 GHz
Max. frequency in Turbo Boost	3.4 GHz	3.7 GHz
Bus frequency	100 MHz	100 MHz
Multiplier	16x	21x
Tire speed	4 GT/s	—
Level 1 cache	64KB (per core)	96KB (per core)
Level 2 cache	256KB (per core)	512KB (per core)
Level 3 cache	6MB (shared)	4MB (shared)
Unlocked multiplier	No	No

Energy consumption

Number of transistors	—	4.9 billion
Process	14 nanometers	12 nanometers
Power consumption (TDP)	15W	12-35W
Critical temperature	100°C	105°C

Integrated graphics	Intel UHD Graphics 620	Radeon Vega 8
GPU frequency	300 MHz	300 MHz
Boost GPU frequency	1100 MHz	1200 MHz
Shader blocks	192	512
TMUs	24	32
ROPs	3	8
Computer units	24	8
TGP	15W	65 W
Max. resolution	4096×2304 — 60Hz	3840×2160 — 60Hz

IGPU Flops

Core i5 8250U

0.38 Teraflops

Ryzen 5 3500u

1.13 Teraflops

Memory Support

Type of memory type DDR4-2400, LPDDR3-2133 DDR4-2400 Max. size 32 GB 32 GB Number of channels 2 2 Max. bandwidth 37.5 GB/s 35.76 GB/s ECC support No Yes

Other

website

Official site	Site Intel Core i5 8250U	AMD Ryzen 5 3500U
PCI Express version	3.0	3.0
Max. PCI Express lanes	12	12
Extended instructions	SSE4.1, SSE4.2, AVX-2	—

Poll

What processor do you think is the best?

Core i5 8250U

64 (34. 8%)

Ryzen 5 3500U

120 (65.2%)

Total votes: 184

Competitors

1.
Intel Core i3 1115G4 and Intel Core i5 8250U

2.
AMD Ryzen 5 5500U and Intel Core i5 8250U

3.
Apple M1 and Intel Core i5 8250U

4.
AMD Ryzen 3 5300U and Intel Core i5 8250U

5.
Intel Core i5 1135G7 and AMD Ryzen 5 3500U

6.
Intel Core i3 1115G4 and AMD Ryzen 5 3500U

7.
AMD Ryzen 5 5500U and AMD Ryzen 5 3500U

8.
Intel Core i5 10210U and AMD Ryzen 5 3500U

9.
AMD Ryzen 3 5300U and AMD Ryzen 5 3500U

What will you choose: AMD Ryzen 5 3500U or Intel Core i5 8250U?

Name

Message

AMD Ryzen 5 3500U Specs, Price, Test, Competitors

Main Page
• >
• Processors
• >
• AMD
• >
• Ryzen 5 3500u

processor Ryzen 5 3500u

Number Number — 4 performance of multi-threaded applications and games.

Ryzen 5 3500U base clock — 2.1 GHz. The maximum frequency in AMD Turbo Core mode reaches 2.8 GHz.

Price in Russia

Want to buy Ryzen 5 3500U cheaply? Look at the list of stores that already sell the processor in your city.

Family

• Ryzen 3 3200u
• Ryzen 3 3300U
• Ryzen 7 3700u
• Athlon 300u

AMD Ryzen 5 3500u 900u

9000

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

Performance in everyday work such as browsers and office applications.

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

Performance in resource-intensive tasks loading a maximum of 8 cores.

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
Minimum	Average	Maximum
34	Memory: 58	72
Memory 61.2
52	1 core: 85	109
1 core 41.5
107	2 cores: 159	207
2 cores 39.5

Demanding games and tasks
Minimum	Average	Maximum
188	4 cores: 274	358
4 cores 34. 5
282	8 cores: 435	534
8 cores 28.1

Extreme
Minimum	Average	Maximum
248	All cores: 437	526
All cores 8

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.

Benchmarks

Benchmarks were run on stock hardware, that is, without overclocking and with factory settings. Therefore, on overclocked systems, the points can noticeably differ upwards. Also, small performance changes may be due to the BIOS version.

Cinebench R23 Single Core

AMD Ryzen 5 1600

900

Intel Core i5-8250U

897

Intel Core i7-6700HQ

896

Intel Core i5-8350U

886

AMD Athlon 3000G

877

AMD Ryzen 5 3500u

876

Intel Core i7-4930K

857

Intel Xeon E3-1231 V3

AMD RYZEN 7 2700U

0000003

820

Intel Core i3-8100T

818

Cinebench R23 Multi Core

Intel Core i7-3770

3650

Intel Core i3-8100

3618

AMD Ryzen 3 2200G

3587

Intel Core i7-8650u

3576

Intel Core i5-4690

3549

AMD Ryzen 5 3500U

3544

Intel Core i5-4670

3389

Intel Core INTEL Core INTEL CORE INTEL CORE

Intel Core i5-7400

3359

Intel Core i7-3635QM

3301

Intel Core i7-2600

3289

Cinebench R20 Single Core

Intel Core i7-8650U

365

Intel Core i3-8100

364

Intel Core i7-4770k

361

AMD Ryzen 3 1300x

360

AMD Ryzen 5 3550H

AMD Ryzen 5 3500U

9000 3000 9000 9000 AM0003

360

AMD Ryzen 3 1300X

360

Intel Celeron G5900

358

Intel Core i7-7800X

358

AMD Ryzen 5 1600

357

Cinebench R20 Multi Core

Intel Core i7 -10510U

1523

Intel Core i7-8565U

1518

AMD Ryzen 7 3700U

Intel Core i5-8250U

1509

AMD Ryzen 3 4300U 9000u 9000 150003

AMD RYZEN 5 3500U

1483

AMD Ryzen 3 3200G

1481

Intel Core i7-4810MQ

1476

Intel Core I5-4670K

1456

INTEL XEN ENTEL XEN

Intel Core i3-8100

1444

Cinebench R15 Single Core

Intel Core i3-8130U

141

Intel Core i7-4820K

141

AMD Ryzen 5 3550H

141

Intel Core i5- 7500T

141

Intel Core i7-47903

141

AMD RYZEN 5 3500U

141

Intel Core i5-7500T

141

Intel Core i7-47770k

141 9000

141

Intel Core i7-4790T

141

AMD Ryzen 5 3550H

141

Cinebench R15 Multi Core

Intel Core i7-4770HQ

634

Intel Core i3-8300

633

Intel Core i7-4720HQ

630

Intel Pentium G3220

625

Intel Core i5-1035G1

624

AMD Ryzen 5 3500U

620

Intel Core i5-7500

617

AMD FX -8370e

616

Intel Core i3-8100

616

Intel Core i7-8650U

614

Intel Core i7-4770T

613

BLENDER 2.

81 BMW218

623.6

Intel Core i7-3770

597.8

Intel Core i7-3770K

597.4

Intel Core i5-4670K

581

AMD Ryzen 7 2700U

576.6

AMD Ryzen 5 3500U

574.1

Intel Core i7-1065g7

566.3

Intel Core i7-4710HQ

561.8

Intel Core i5-4690k

561.1

I5-6600

0003

540.3

Geekbench 3 Single Core

Intel Pentium G4600

3686

Intel Core i5-7300U

3686

AMD Ryzen 7 2700U

3679

Intel Xeon E5-1620 v2

3640

AMD Ryzen 5 3550h

3625

AMD RYZEN 5 3500U

3625

AMD Ryzen 5 3550H

3625

Intel Core i7-4770t

3618

Intel Core I7-57003 9610003

Intel Core i3-8130U

3600

Intel Core i7-6600U

3600

Geekbench 3 Multi Core

Intel Core i5-8250U

11787

Intel Core i5-8265U

11787

Intel Xeon E3-1265L V3

11740

Intel Core i5-7600t

11701

AMD Ryzen 5 3550H

11645

AMD Ryzen 5 3500U

11645 9000 9000

AMD Ryzen 5,000410002 AMD Ryzen 3 2300U

11475

Intel Core i7-4700MQ

11452

Intel Core i7-4700HQ

11452

Intel Core i5-6500

11448

Cinebench R11.

5

Intel Core i7- 4900MQ

1.71

Intel Core i5-4690

1.71

Intel Core i5-4690k

1.71

Intel Core i7-6700HQ

1.7

9000 9000 9000 9000 9000 AMD0003

1.7

AMD Ryzen 7 2700U

1.69

Intel Core i3-8109U

1.69

Intel Pentium G4500

1.69

Intel Core i7-7500U

1.69

Intel Core i5-7300U

1.69

Cinebench R11.5

Intel Xeon E3-1275 V3

7.99

Intel Xeon E3-1240 V3

7.94

Intel Xeon E3-1245 V3 9000 9000) Intel Xeon ENTEL XEON ENTEL XEON ENTL3

AMD RYZEN 5 1500X

7. 85

AMD Ryzen 5 3500u

7.8

Intel Core i7-5850HQ

7.76

Intel Xeon E3-1230 V3

7.73

AMD Ry

Intel Core i5-7640X

7.64

Intel Core i5-7600K

7.61

iGPU — FP32 Performance GFLOPS

AMD Ryzen 7 4700U

1433

Intel Core i5-1130G7

1406

AMD Ryzen 3 5300G

1306

AMD Ryzen 3 3200G

1280

AMD Ryzen 5 5600H

1229

AMD Ryzen 5 3500U

1229

AMD Ryzen 5 5600H

1229

AMD Ryzen 5 4600U

1152

AMD Ryzen 5 4500U

1152

AMD Ryzen 5 4600hs

1152

AMD Ryzen 5 4600h

1152

Passmark

AMD Ryzen 3 32230003

Intel Core i7-4790

7195

Intel Core i7-7820HQ

7191

Intel Xeon E3-1246 V3

7181

Intel E3-1270 V3

71777 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 AMD 7151

Intel Core i7-5775R

7150

Intel Xeon W3690

7145

Intel Xeon E3-1241 v3

7126

Intel Core i5-8305G

7073

Intel Core i7-4770K

7071

Game benchmarks

Our measured FPS in popular games on AMD Ryzen 5 3500U and system requirements. Please note that the official requirements of developers in games do not always match the data of real tests. Also, the result is strongly influenced by the overclocking of the system and the graphic settings in the game. We test at high settings in FullHD resolution to get numbers close to real gameplay.

On average for all gaming tests, the processor scored 46.6 points out of 100, where 100 is the fastest gaming processor to date.

• n.a.

SSD

• n.a. Also with these components, the best results in tests and stable operation are achieved.

  Most popular config: motherboard for AMD Ryzen 5 3500U — Lenovo 81SS.

  Characteristics

  The data is not yet filled in, so the tables may lack information or existing functions may be omitted.

  Basic

  Manufacturer	AMD
  Release dateMonth and year of the processor’s availability.	06-2021
  Cores The number of physical cores.	4
  ThreadsNumber of threads. The number of logical processor cores that the operating system sees.	8
  Multi-Threading Technology With Intel’s Hyper-threading and AMD’s SMT technology, one physical core is recognized as two logical cores in the operating system, thereby increasing processor performance in multi-threaded applications.	SMT (note that some games may not work well with SMT, for maximum FPS, you can disable the technology in the BIOS of the motherboard).
  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.1 GHz
  Turbo Frequency The maximum frequency of a single 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.	2.8 GHz
  Embedded Options Available Two enclosure versions. Standard and designed for mobile devices. In the second version, the processor can be soldered on the motherboard.	No

  Video core

  RAM

  PCI

  Data protection

  Appearance

  Competitors

  Please note that competitors are automatically selected based on performance in a specific task. Therefore, some may puzzle you. We are improving our selection algorithm, treat with understanding.

  Compare

  AMD Ryzen 5 3500U vs Intel Core i7 Q 840

  AMD Ryzen 5 3500U vs Intel Core i7-10510Y

  AMD Ryzen 5 3500U vs Intel Core i5-3330S

  AMD Ryzen 5 3500U vs Intel Xeon X5472

  AMD Ryzen 5 3500U vs Intel Core i7 Q 840

  AMD Ryzen 5 3500U vs Intel Core i3-4330

  Finding out all the security features of AMD Ryzen PRO

  My series of articles about the very business laptop Lenovo ThinkPad T495 continues. And this time I will talk about what is so unusual about its processor, AMD Ryzen 5 PRO 3500U . Obviously, this is an ordinary quad-core with Vega 8, which I even ran through benchmarks. But is it really so?

  To begin with, let me remind you what kind of animal this is in general. The AMD Ryzen 5 PRO 3500U is a 12nm Zen+ mobile processor with four cores and eight threads. The base frequency is 2.1 GHz, bustsky — up to 3.7 GHz. Caches — 384 KB, 2 MB and 4 MB L1/2/3 respectively.

  TDP — 15V, upgradeable up to 25W. The maximum temperature is 95 degrees Caesar. Or caesia? Possibly Celsius, but this is inaccurate. The processor also has a video core, Vega 8, with eight graphics cores and a Boost frequency of up to 1200 MHz.

  In tests and a review of the laptop itself, we have already found out that the main problem of the Ryzen 5 3500U is the Vega 8 video core, which does not boost up to the promised 1200 MHz even on pain of death, and in games sometimes it lowers frequencies to 200 MHz. Which, of course, does not have a very positive effect on FPS.

  But even with such conventions and problems, the Ryzen 5 3500U wipes its feet on the nearest price competitors in total power, slightly surpassing the Core i5-8250U in processor power and winding circles around it in games. Still, Intel UHD Graphics caught up with Vega only in the very latest processors, which did not really enter our market.

  But well, the processor is not bad, and the video core, although it could be better, is also nothing like that. But this is Ryzen 5, not Ryzen 5 PRO. What is good about the last one?

  AMD Ryzen 5 PRO 3500U Q&A

  I was so worried about this question that I took the risk of writing directly to AMD representatives. And got answers. Not to the full extent, but my curiosity was satisfied, at least partially. So:

  Question : How much more expensive is Ryzen PRO on average than the non-PRO version? Obviously, a super-secure processor must cost more, both in chips and in smaller batches. Or does the batch size not affect the price?

  Answer : Not at all. The CCD die is the same for all CPUs, including EPYC. For PRO, security features are just officially announced.

  Q : Is Ryzen PRO able to protect against things that the user can pick up, say, from a phishing email in the mail, or by downloading an unverified exe file from a dubious site? Or is the protection of the processor aimed more at hacking attempts directly by another user?

  O : Technologies are rather focused on protection against day0 vulnerabilities that allow access to «foreign» areas of memory. A good additional layer of security, but it is unlikely to save you from a user who runs all suspicious executables with admin rights. Ryzen PRO This is not about the desktop version, but rather about laptop ones, where there is a limit in TDP for all components on a chip.

  O : Depends on the enabled security technologies, but in most cases the difference will be subtle (2-3% with full memory encryption, for example).

  Q : Does it make any sense for an ordinary, ordinary and non-corporate user to buy Ryzen PRO? And if not, what should the user do in order for him to need Ryzen PRO?

  O : It is unlikely that the average user will succeed. PRO-processors do not go to the channel. But if you want, for example, official support for ECC memory — why not?

  Q : Are hardware security solutions considered more reliable than software ones? And why exactly?

  O : It hardly makes sense to compare them directly. Additional features of Ryzen hardware security will not replace antivirus, but they will help close from freshly found exploits.

  Q : In your opinion, what is the most effective and useful protection tool available with the Ryzen PRO? And which of the tools, according to statistics (if any), works most often?

  O : No statistics — security features are not monitored over the internet for obvious reasons. The most “frequently used” tool is “root of trust” technology, there are frequent reports of complaints about a PC refusing to boot due to the lack of a digital signature of the boot partition. As a rule, this happens due to the ransomware trying to intercept the download, which, fortunately, did not have time to start working due to the stopped download process.

  B : What is the most powerful processor with the PRO index? Are there Threadripper PRO or EPYC PRO?

  About : Threadripper — all are considered PRO, EPYC — a completely different segment.

  B : Question from a reader. Quote: “What does the undocumented bit in the CPUID of the AMD Threadripper 3970X processor mean in the context of the MCA (Machine Check Architecture) error control subsystem?”

  I never received an answer to this question.

  AMD Ryzen 5 PRO 3500U 9 Chip Totals0019

  The obviously business-oriented model, whose security chips are aimed at the vulnerabilities of the most basic levels, turns out to be much more interesting.