Intel Core i3-8130U vs Intel Core i5-8250U: What is the difference?
49points
Intel Core i3-8130U
49points
Intel Core i5-8250U
vs
64 facts in comparison
Intel Core i3-8130U
Intel Core i5-8250U
Why is Intel Core i3-8130U better than Intel Core i5-8250U?
- 0.25MB/core more L2 cache per core?
0.5MB/corevs0.25MB/core - 3.4GB/s more memory bandwidth?
37.5GB/svs34.1GB/s - 0.5MB/core more L3 cache per core?
2MB/corevs1.5MB/core - Has TrustZone?
Why is Intel Core i5-8250U better than Intel Core i3-8130U?
- 45.45% faster CPU speed?
4 x 1.6GHzvs2 x 2.2GHz - 4 more CPU threads?
8vs4 - 1.61x higher PassMark result?
5941vs3688 - 2MB bigger L3 cache?
6MBvs4MB - 23.
03% higher multi-core Geekbench 5 result?
1971vs1602 - 100MHz faster GPU turbo speed?
1100MHzvs1000MHz
Which are the most popular comparisons?
Intel Core i3-8130U
vs
Intel Celeron N4020
Intel Core i5-8250U
vs
Intel Core i3-1115G4
Intel Core i3-8130U
vs
AMD A6-9225
Intel Core i5-8250U
vs
AMD Ryzen 5 3500U
Intel Core i3-8130U
vs
AMD Athlon 300U
Intel Core i5-8250U
vs
Intel Core i3-1005G1
Intel Core i3-8130U
vs
Intel Core i3-10110U
Intel Core i5-8250U
vs
AMD Ryzen 3 2200U
Intel Core i3-8130U
vs
AMD Ryzen 3 3200U
Intel Core i5-8250U
vs
Intel Core i7-6500U
Intel Core i3-8130U
vs
Intel Core i3-1115G4
Intel Core i5-8250U
vs
AMD Ryzen 3 3200U
Intel Core i3-8130U
vs
Intel Pentium Gold 5405U
Intel Core i5-8250U
vs
AMD Ryzen 5 2500U
Intel Core i3-8130U
vs
AMD A12-9720P
Intel Core i5-8250U
vs
AMD Ryzen 5 5500U
Intel Core i3-8130U
vs
AMD 3020e
Intel Core i5-8250U
vs
Intel Core i7-7500U
Intel Core i5-8250U
vs
Intel Core i5-7200U
Price comparison
User reviews
Overall Rating
Intel Core i3-8130U
1 User reviews
Intel Core i3-8130U
9.
0/10
1 User reviews
Intel Core i5-8250U
5 User reviews
Intel Core i5-8250U
7.4/10
5 User reviews
Features
Value for money
8.0/10
1 votes
7.4/10
5 votes
Gaming
5.0/10
1 votes
6.6/10
5 votes
Performance
7.0/10
1 votes
7.4/10
5 votes
Reliability
10.0/10
1 votes
8.8/10
5 votes
Energy efficiency
10.0/10
1 votes
6.4/10
5 votes
Performance
1.CPU speed
2 x 2.2GHz
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.4GHz
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
✖Intel Core i3-8130U
✖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
2MB/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
37.5GB/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
The bus is responsible for transferring data between different components of a computer or device.
7.Supports ECC memory
✖Intel Core i3-8130U
✖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. (Intel Core i3-8130U)
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.
(Intel Core i3-8130U)
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
Unknown. Help us by suggesting a value. (Intel Core i3-8130U)
Cinebench R20 is a benchmark tool that measures a CPU’s multi-core performance by rendering a 3D scene.
5.Cinebench R20 (single) result
Unknown.
Help us by suggesting a value. (Intel Core i3-8130U)
Cinebench R20 is a benchmark tool that measures a CPU’s single-core performance by rendering a 3D scene.
6.Geekbench 5 result (single)
Geekbench 5 is a cross-platform benchmark that measures a processor’s single-core performance. (Source: Primate Labs, 2022)
7.Blender (bmw27) result
Unknown. Help us by suggesting a value. (Intel Core i3-8130U)
771.41seconds
The Blender (bmw27) benchmark measures the performance of a processor by rendering a 3D scene. More powerful processors can render the scene in less time.
8.Blender (classroom) result
Unknown. Help us by suggesting a value. (Intel Core i3-8130U)
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
Unknown. Help us by suggesting a value. (Intel Core i3-8130U)
This means the CPU is more efficient, giving a greater amount of performance for each watt of power used.
Features
1.uses multithreading
✔Intel Core i3-8130U
✔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
✔Intel Core i3-8130U
✔Intel Core i5-8250U
AES is used to speed up encryption and decryption.
3.Has AVX
✔Intel Core i3-8130U
✔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
✔Intel Core i3-8130U
✔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. (Intel Core i3-8130U)
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
✔Intel Core i3-8130U
✔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
✔Intel Core i3-8130U
✖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. (Intel Core i3-8130U)
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 i3 8130U: performance comparison
VS
Intel Core i5 8250U
Intel Core i3 8130U
We compared two laptop CPUs: the 1.6 GHz Intel Core i5 8250U with 4-cores against the 2.2 GHz i3 8130U with 2-cores. On this page, you’ll find out which processor has better performance in benchmarks, games and other useful information.
- Review
- Differences
- Performance
- Specs
- Comments
Review
General overview and comparison of the processors
Single-Core Performance
Performance in single-threaded apps and benchmarks
Core i5 8250U
46
Core i3 8130U
46
Performance
Measure performance when all cores are involved
Core i5 8250U
16
Core i3 8130U
11
Power Efficiency
The efficiency score of electricity consumption
Core i5 8250U
58
Core i3 8130U
58
NanoReview Final Score
Generic CPU rating
Core i5 8250U
36
Core i3 8130U
34
Key Differences
What are the key differences between 8130U and 8250U
Advantages of Intel Core i5 8250U
- Has 2 more physical cores
- Has 2 MB larger L3 cache size
Advantages of Intel Core i3 8130U
- Newer — released 5-months later
Benchmarks
Comparing the performance of CPUs in benchmarks
Cinebench R23 (Single-Core)
Core i5 8250U
899
Core i3 8130U
899
Cinebench R23 (Multi-Core)
Core i5 8250U
+44%
3061
Core i3 8130U
2123
Passmark CPU (Single-Core)
Core i5 8250U
1919
Core i3 8130U
1924
Passmark CPU (Multi-Core)
Core i5 8250U
+64%
5920
Core i3 8130U
3616
Geekbench 5 (Single-Core)
Core i5 8250U
+2%
855
Core i3 8130U
836
Geekbench 5 (Multi-Core)
Core i5 8250U
+61%
2829
Core i3 8130U
1760
▶️ 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 i3 8130U
General
| Vendor | Intel | Intel |
| Released | August 21, 2017 | February 12, 2018 |
| Type | Laptop | Laptop |
| instruction set | x86-64 | x86-64 |
| Codename | Kaby Lake R | Kaby Lake |
| Model number | i5-8250U | i3-8130U |
| Socket | BGA-1356 | BGA-1356 |
| Integrated GPU | UHD Graphics 620 | UHD Graphics 620 |
Performance
| Cores | 4 | 2 |
| Threads | 8 | 4 |
| Base Frequency | 1. 6 GHz |
2.2 GHz |
| Turbo Boost Frequency | 3.4 GHz | 3.4 GHz |
| Bus frequency | 100 MHz | 100 MHz |
| Multiplier | 16x | 24x |
| Bus Bandwidth | 4 GT/s | 4 GT/s |
| L1 Cache | 64K (per core) | 64K (per core) |
| L2 Cache | 256K (per core) | 256K (per core) |
| L3 Cache | 6MB (shared) | 4MB (shared) |
| Unlocked Multiplier | No | No |
| Fabrication process | 14 nm | 14 nm |
| TDP | 15 W | 15 W |
| Max. temperature | 100°C | 100°C |
| Integrated Graphics | Intel UHD Graphics 620 | Intel UHD Graphics 620 |
| GPU Base Clock | 300 MHz | 300 MHz |
| GPU Boost Clock | 1100 MHz | 1000 MHz |
| Shading Units | 192 | 192 |
| TMUs | 24 | 24 |
| ROPs | 3 | 3 |
| Execution Units | 24 | 24 |
| TGP | 15 W | 15 W |
Max. Resolution |
4096×2304 — 60 Hz | 4096×2304 — 60 Hz |
iGPU FLOPS
Core i5 8250U
0.38 TFLOPS
Core i3 8130U
0.38 TFLOPS
Memory support
| Memory types | DDR4-2400, LPDDR3-2133 | DDR4-2400, LPDDR3-2133 |
| Memory Size | 32 GB | 32 GB |
| Max. Memory Channels | 2 | 2 |
| Max. Memory Bandwidth | 37.5 GB/s | 37.5 GB/s |
| ECC Support | No | No |
| Official site | Intel Core i5 8250U official page | Intel Core i3 8130U official page |
| PCI Express Version | 3.0 | 3.0 |
| PCI Express Lanes | 12 | 12 |
| Extended instructions | SSE4. 1, SSE4.2, AVX-2 |
SSE4.1, SSE4.2, AVX-2 |
Cast your vote
Choose between two processors
Core i5 8250U
13 (39.4%)
Core i3 8130U
20 (60.6%)
Total votes: 33
ompetitors
1.
Intel Core i5 8250U and i3 1115G4
2.
Intel Core i5 8250U and AMD Ryzen 5 5500U
3.
Intel Core i5 8250U and Apple M1
4.
Intel Core i5 8250U and AMD Ryzen 3 5300U
5.
Intel Core i3 8130U and i3 1115G4
Intel Core i3-8130U vs Intel Core i5-8250U
log 04. 05:59:17
#0 checking url part for id 9518 +0s … 0s
#1 checking url part for id 9206 +0s … 0s
#2 not redirecting to Ajax server +0s … 0s
#3 did not recreate cache, as it is less than 5 days old! Created at Fri, 30 Sep 2022 13:14:19 +0200 +0s .
.. 0s
#4 linkCache_getLink no uid found +0.008s … 0.009s
#5 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.01s
#6 linkCache_getLink no uid found +0.003s … 0.013s
#7 linkCache_getLink using $NBC_LINKCACHE +0s … 0.013s
#8 linkCache_getLink using $NBC_LINKCACHE +0s … 0.013s
#9 linkCache_getLink using $NBC_LINKCACHE +0s … 0.013s
#10 linkCache_getLink using $NBC_LINKCACHE +0s … 0.013s
#11 linkCache_getLink using $NBC_LINKCACHE +0s … 0.013s
#12 linkCache_getLink using $NBC_LINKCACHE +0s … 0.013s
#13 composed specs +0s … 0.013s
#14 did output specs +0s … 0.013s
#15 getting avg benchmarks for device 9518 +0s … 0.013s
#16 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.014s
#17 linkCache_getLink using $NBC_LINKCACHE +0s … 0.014s
#18 got single benchmarks 9518 +0.023s ..
. 0.037s
#19 linkCache_getLink using $NBC_LINKCACHE +0.005s … 0.042s
#20 getting avg benchmarks for device 9206 +0.001s … 0.043s
#21 linkCache_getLink using $NBC_LINKCACHE +0.004s … 0.046s
#22 got single benchmarks 9206 +0.223s … 0.269s
#23 got avg benchmarks for devices +0s … 0.269s
#24 linkCache_getLink no uid found +0s … 0.269s
#25 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.271s
#26 linkCache_getLink no uid found +0s … 0.271s
#27 linkCache_getLink no uid found +0.002s … 0.273s
#28 linkCache_getLink using $NBC_LINKCACHE +0s … 0.273s
#29 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.274s
#30 linkCache_getLink using $NBC_LINKCACHE +0s … 0.274s
#31 linkCache_getLink using $NBC_LINKCACHE +0s … 0.274s
#32 linkCache_getLink no uid found +0s … 0.274s
#33 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.274s
#34 linkCache_getLink using $NBC_LINKCACHE +0s … 0.274s
#35 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.276s
#36 linkCache_getLink using $NBC_LINKCACHE +0.017s … 0.293s
#37 linkCache_getLink no uid found +0s … 0.293s
#38 linkCache_getLink no uid found +0.001s … 0.294s
#39 linkCache_getLink no uid found +0.001s … 0.295s
#40 linkCache_getLink no uid found +0.004s … 0.298s
#41 linkCache_getLink no uid found +0.001s … 0.299s
#42 linkCache_getLink no uid found +0s … 0.299s
#43 linkCache_getLink no uid found +0s … 0.299s
#44 linkCache_getLink using $NBC_LINKCACHE +0s … 0.299s
#45 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.3s
#46 linkCache_getLink using $NBC_LINKCACHE +0s … 0.301s
#47 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.302s
#48 linkCache_getLink no uid found +0s .
.. 0.303s
#49 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.304s
#50 linkCache_getLink using $NBC_LINKCACHE +0s … 0.304s
#51 linkCache_getLink using $NBC_LINKCACHE +0.471s … 0.776s
#52 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#53 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#54 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.776s
#55 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#56 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#57 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#58 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#59 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#60 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#61 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#62 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.776s
#63 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#64 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#65 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#66 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#67 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#68 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#69 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#70 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#71 linkCache_getLink no uid found +0s … 0.776s
#72 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#73 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#74 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#75 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#76 linkCache_getLink using $NBC_LINKCACHE +0s … 0.776s
#77 linkCache_getLink no uid found +0s .
.. 0.777s
#78 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#79 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#80 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#81 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#82 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#83 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#84 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#85 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#86 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#87 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#88 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#89 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#90 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#91 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#92 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.777s
#93 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#94 linkCache_getLink no uid found +0s … 0.777s
#95 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#96 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#97 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#98 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#99 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#104 linkCache_getLink no uid found +0s … 0.777s
#105 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#107 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.777s
#108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#110 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#113 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#116 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#121 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.777s
#122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#123 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#124 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#125 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#126 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#127 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#128 linkCache_getLink no uid found +0s … 0.777s
#129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#130 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#133 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#135 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.777s
#136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#137 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#138 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#139 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#140 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#141 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#142 linkCache_getLink no uid found +0s … 0.777s
#143 linkCache_getLink no uid found +0s … 0.777s
#144 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#147 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#148 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#149 linkCache_getLink using $NBC_LINKCACHE +0s … 0.777s
#150 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.777s
#151 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.778s
#152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#153 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#154 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#155 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#157 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#158 linkCache_getLink no uid found +0s … 0.779s
#159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#160 linkCache_getLink no uid found +0s … 0.779s
#161 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#162 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#164 linkCache_getLink no uid found +0s … 0.779s
#165 linkCache_getLink no uid found +0s .
.. 0.779s
#166 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#167 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#169 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#171 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#172 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#174 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#175 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#176 linkCache_getLink no uid found +0s … 0.779s
#177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#179 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.779s
#180 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#181 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#182 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#183 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#184 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#185 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#186 linkCache_getLink using $NBC_LINKCACHE +0s … 0.779s
#187 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.78s
#188 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#189 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#191 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#192 linkCache_getLink no uid found +0s … 0.781s
#193 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.781s
#194 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#195 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#196 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#197 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#198 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#199 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#200 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#201 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#202 linkCache_getLink no uid found +0s … 0.781s
#203 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#205 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#206 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#207 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.781s
#208 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#209 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#210 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#211 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#212 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#213 linkCache_getLink no uid found +0s … 0.781s
#214 linkCache_getLink no uid found +0s … 0.781s
#215 linkCache_getLink no uid found +0s … 0.781s
#216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#217 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#218 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#219 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#220 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#221 linkCache_getLink using $NBC_LINKCACHE +0s … 0.781s
#222 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.781s
#223 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.782s
#224 linkCache_getLink using $NBC_LINKCACHE +0s … 0.782s
#225 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#226 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#227 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#228 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#229 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#230 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#231 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#232 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#233 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#234 linkCache_getLink no uid found +0s … 0.783s
#235 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#236 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.783s
#237 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#238 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#239 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#240 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#241 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#242 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#243 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#244 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#245 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#246 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#247 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#248 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#249 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#250 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.783s
#251 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#252 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#253 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#254 linkCache_getLink no uid found +0s … 0.783s
#255 linkCache_getLink no uid found +0s … 0.783s
#256 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#257 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#258 linkCache_getLink no uid found +0s … 0.783s
#259 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#260 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#261 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#262 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#263 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#264 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#265 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.783s
#266 linkCache_getLink using $NBC_LINKCACHE +0s … 0.783s
#267 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.784s
#268 linkCache_getLink using $NBC_LINKCACHE +0s … 0.784s
#269 linkCache_getLink no uid found +0s … 0.785s
#270 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#271 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#272 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#273 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#274 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#275 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#276 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#277 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#278 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#279 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.785s
#280 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#281 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#282 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#283 linkCache_getLink no uid found +0s … 0.785s
#284 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#285 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#286 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#287 linkCache_getLink no uid found +0s … 0.785s
#288 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#289 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#290 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#291 linkCache_getLink no uid found +0s … 0.785s
#292 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#293 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#294 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.785s
#295 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#296 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#297 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#298 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#299 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#300 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#301 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#302 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#303 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#304 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#305 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#306 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#307 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#308 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.785s
#309 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#310 linkCache_getLink using $NBC_LINKCACHE +0s … 0.785s
#311 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.786s
#312 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#313 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#314 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#315 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#316 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#317 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#318 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#319 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#320 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#321 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#322 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.786s
#323 linkCache_getLink using $NBC_LINKCACHE +0s … 0.786s
#324 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.787s
#325 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s
#326 linkCache_getLink using $NBC_LINKCACHE +0s … 0.787s
#327 linkCache_getLink using $NBC_LINKCACHE +0s … 0.788s
#328 linkCache_getLink using $NBC_LINKCACHE +0s … 0.788s
#329 linkCache_getLink using $NBC_LINKCACHE +0s … 0.788s
#330 linkCache_getLink using $NBC_LINKCACHE +0s … 0.788s
#331 linkCache_getLink using $NBC_LINKCACHE +0s … 0.788s
#332 linkCache_getLink using $NBC_LINKCACHE +0s … 0.788s
#333 linkCache_getLink using $NBC_LINKCACHE +0s … 0.788s
#334 linkCache_getLink using $NBC_LINKCACHE +0s … 0.788s
#335 linkCache_getLink using $NBC_LINKCACHE +0s … 0.788s
#336 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.788s
#337 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.789s
#338 linkCache_getLink using $NBC_LINKCACHE +0s … 0.789s
#339 linkCache_getLink using $NBC_LINKCACHE +0s … 0.789s
#340 linkCache_getLink using $NBC_LINKCACHE +0s … 0.789s
#341 linkCache_getLink using $NBC_LINKCACHE +0s … 0.789s
#342 linkCache_getLink using $NBC_LINKCACHE +0s … 0.789s
#343 linkCache_getLink using $NBC_LINKCACHE +0s … 0.789s
#344 linkCache_getLink using $NBC_LINKCACHE +0s … 0.789s
#345 linkCache_getLink no uid found +0s … 0.789s
#346 linkCache_getLink using $NBC_LINKCACHE +0s … 0.789s
#347 linkCache_getLink using $NBC_LINKCACHE +0s … 0.789s
#348 linkCache_getLink using $NBC_LINKCACHE +0s … 0.789s
#349 linkCache_getLink using $NBC_LINKCACHE +0s … 0.789s
#350 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.789s
#351 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.79s
#352 linkCache_getLink using $NBC_LINKCACHE +0s … 0.791s
#353 linkCache_getLink using $NBC_LINKCACHE +0s … 0.791s
#354 linkCache_getLink using $NBC_LINKCACHE +0s … 0.791s
#355 linkCache_getLink using $NBC_LINKCACHE +0s … 0.791s
#356 linkCache_getLink using $NBC_LINKCACHE +0s … 0.791s
#357 linkCache_getLink using $NBC_LINKCACHE +0s … 0.791s
#358 linkCache_getLink no uid found +0s … 0.791s
#359 linkCache_getLink using $NBC_LINKCACHE +0s … 0.791s
#360 linkCache_getLink using $NBC_LINKCACHE +0s … 0.791s
#361 linkCache_getLink using $NBC_LINKCACHE +0s … 0.791s
#362 linkCache_getLink using $NBC_LINKCACHE +0s … 0.791s
#363 linkCache_getLink using $NBC_LINKCACHE +0s … 0.791s
#364 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.791s
#365 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.792s
#366 linkCache_getLink no uid found +0s … 0.792s
#367 linkCache_getLink using $NBC_LINKCACHE +0s … 0.792s
#368 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.795s
#369 linkCache_getLink using $NBC_LINKCACHE +0s … 0.795s
#370 linkCache_getLink using $NBC_LINKCACHE +0s … 0.795s
#371 linkCache_getLink no uid found +0s … 0.795s
#372 linkCache_getLink using $NBC_LINKCACHE +0s … 0.795s
#373 linkCache_getLink using $NBC_LINKCACHE +0s … 0.795s
#374 linkCache_getLink no uid found +0.002s … 0.797s
#375 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#376 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#377 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#378 linkCache_getLink using $NBC_LINKCACHE +0s … 0.
797s
#379 linkCache_getLink using $NBC_LINKCACHE +0s … 0.797s
#380 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.798s
#381 linkCache_getLink using $NBC_LINKCACHE +0s … 0.799s
#382 linkCache_getLink using $NBC_LINKCACHE +0s … 0.799s
#383 linkCache_getLink no uid found +0s … 0.799s
#384 linkCache_getLink using $NBC_LINKCACHE +0s … 0.799s
#385 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.8s
#386 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s
#387 linkCache_getLink no uid found +0s … 0.8s
#388 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s
#389 linkCache_getLink using $NBC_LINKCACHE +0s … 0.8s
#390 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.801s
#391 linkCache_getLink using $NBC_LINKCACHE +0s … 0.801s
#392 linkCache_getLink using $NBC_LINKCACHE +0s … 0.801s
#393 linkCache_getLink no uid found +0s .
.. 0.801s
#394 linkCache_getLink using $NBC_LINKCACHE +0s … 0.801s
#395 linkCache_getLink using $NBC_LINKCACHE +0s … 0.801s
#396 linkCache_getLink using $NBC_LINKCACHE +0s … 0.801s
#397 linkCache_getLink using $NBC_LINKCACHE +0s … 0.801s
#398 linkCache_getLink using $NBC_LINKCACHE +0.058s … 0.86s
#399 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.861s
#400 linkCache_getLink using $NBC_LINKCACHE +0s … 0.861s
#401 linkCache_getLink using $NBC_LINKCACHE +0s … 0.861s
#402 linkCache_getLink no uid found +0s … 0.861s
#403 linkCache_getLink using $NBC_LINKCACHE +0s … 0.861s
#404 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.862s
#405 linkCache_getLink using $NBC_LINKCACHE +0s … 0.862s
#406 linkCache_getLink using $NBC_LINKCACHE +0s … 0.862s
#407 linkCache_getLink no uid found +0s .
.. 0.862s
#408 linkCache_getLink using $NBC_LINKCACHE +0s … 0.862s
#409 linkCache_getLink using $NBC_LINKCACHE +0s … 0.862s
#410 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.864s
#411 linkCache_getLink using $NBC_LINKCACHE +0s … 0.864s
#412 linkCache_getLink using $NBC_LINKCACHE +0s … 0.864s
#413 linkCache_getLink using $NBC_LINKCACHE +0s … 0.864s
#414 linkCache_getLink no uid found +0s … 0.864s
#415 linkCache_getLink using $NBC_LINKCACHE +0s … 0.864s
#416 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.866s
#417 linkCache_getLink using $NBC_LINKCACHE +0s … 0.866s
#418 linkCache_getLink using $NBC_LINKCACHE +0s … 0.866s
#419 linkCache_getLink no uid found +0s … 0.866s
#420 linkCache_getLink using $NBC_LINKCACHE +0s … 0.866s
#421 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.866s
#422 linkCache_getLink using $NBC_LINKCACHE +0s … 0.866s
#423 linkCache_getLink using $NBC_LINKCACHE +0s … 0.866s
#424 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.868s
#425 linkCache_getLink using $NBC_LINKCACHE +0s … 0.868s
#426 linkCache_getLink no uid found +0s … 0.868s
#427 linkCache_getLink using $NBC_LINKCACHE +0s … 0.868s
#428 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.87s
#429 linkCache_getLink no uid found +0s … 0.87s
#430 linkCache_getLink using $NBC_LINKCACHE +0s … 0.87s
#431 linkCache_getLink using $NBC_LINKCACHE +0s … 0.87s
#432 linkCache_getLink no uid found +0s … 0.87s
#433 linkCache_getLink using $NBC_LINKCACHE +0s … 0.87s
#434 linkCache_getLink using $NBC_LINKCACHE +0s … 0.87s
#435 linkCache_getLink using $NBC_LINKCACHE +0s … 0.87s
#436 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.87s
#437 linkCache_getLink using $NBC_LINKCACHE +0s … 0.87s
#438 linkCache_getLink using $NBC_LINKCACHE +0s … 0.87s
#439 linkCache_getLink no uid found +0s … 0.87s
#440 linkCache_getLink using $NBC_LINKCACHE +0s … 0.87s
#441 linkCache_getLink using $NBC_LINKCACHE +0s … 0.87s
#442 linkCache_getLink using $NBC_LINKCACHE +0s … 0.87s
#443 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.872s
#444 linkCache_getLink no uid found +0s … 0.872s
#445 linkCache_getLink using $NBC_LINKCACHE +0s … 0.872s
#446 linkCache_getLink using $NBC_LINKCACHE +0s … 0.872s
#447 linkCache_getLink using $NBC_LINKCACHE +0s … 0.872s
#448 linkCache_getLink using $NBC_LINKCACHE +0s … 0.872s
#449 linkCache_getLink using $NBC_LINKCACHE +0s … 0.872s
#450 linkCache_getLink using $NBC_LINKCACHE +0s … 0.872s
#451 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.872s
#452 linkCache_getLink using $NBC_LINKCACHE +0s … 0.872s
#453 linkCache_getLink using $NBC_LINKCACHE +0s … 0.872s
#454 linkCache_getLink using $NBC_LINKCACHE +0s … 0.872s
#455 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.874s
#456 linkCache_getLink no uid found +0s … 0.874s
#457 linkCache_getLink using $NBC_LINKCACHE +0s … 0.874s
#458 linkCache_getLink using $NBC_LINKCACHE +0s … 0.874s
#459 linkCache_getLink using $NBC_LINKCACHE +0s … 0.874s
#460 linkCache_getLink using $NBC_LINKCACHE +0s … 0.874s
#461 linkCache_getLink using $NBC_LINKCACHE +0s … 0.874s
#462 linkCache_getLink using $NBC_LINKCACHE +0s … 0.874s
#463 linkCache_getLink using $NBC_LINKCACHE +0s … 0.874s
#464 linkCache_getLink using $NBC_LINKCACHE +0s … 0.874s
#465 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.874s
#466 linkCache_getLink using $NBC_LINKCACHE +0s … 0.874s
#467 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.876s
#468 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#469 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#470 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#471 linkCache_getLink no uid found +0s … 0.876s
#472 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#473 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#474 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#475 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#476 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#477 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#478 linkCache_getLink using $NBC_LINKCACHE +0s … 0.876s
#479 linkCache_getLink no uid found +0.001s ..
. 0.878s
#480 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#481 linkCache_getLink no uid found +0s … 0.878s
#482 linkCache_getLink using $NBC_LINKCACHE +0s … 0.878s
#483 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.879s
#484 linkCache_getLink using $NBC_LINKCACHE +0s … 0.879s
#485 linkCache_getLink using $NBC_LINKCACHE +0s … 0.879s
#486 linkCache_getLink using $NBC_LINKCACHE +0s … 0.879s
#487 linkCache_getLink using $NBC_LINKCACHE +0s … 0.879s
#488 linkCache_getLink using $NBC_LINKCACHE +0s … 0.879s
#489 linkCache_getLink using $NBC_LINKCACHE +0s … 0.879s
#490 linkCache_getLink using $NBC_LINKCACHE +0s … 0.879s
#491 linkCache_getLink using $NBC_LINKCACHE +0s … 0.879s
#492 linkCache_getLink using $NBC_LINKCACHE +0s … 0.879s
#493 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.879s
#494 linkCache_getLink using $NBC_LINKCACHE +0s … 0.879s
#495 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#496 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#497 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#498 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#499 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#500 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#501 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#502 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#503 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#504 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#505 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#506 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#507 linkCache_getLink using $NBC_LINKCACHE +0s … 0.
88s
#508 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#509 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#510 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#511 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#512 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#513 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#514 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#515 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#516 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#517 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#518 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#519 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#520 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#521 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#522 linkCache_getLink no uid found +0s .
.. 0.88s
#523 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#524 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#525 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#526 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#527 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#528 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#529 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#530 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#531 linkCache_getLink no uid found +0s … 0.88s
#532 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#533 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#534 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#535 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#536 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#537 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.88s
#538 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#539 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#540 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#541 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#542 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#543 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#544 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#545 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#546 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#547 linkCache_getLink no uid found +0s … 0.88s
#548 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#549 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#550 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#551 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#552 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.88s
#553 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#554 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#555 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#556 linkCache_getLink no uid found +0s … 0.88s
#557 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#558 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#559 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#560 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#561 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#562 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#563 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#564 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#565 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#566 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#567 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.88s
#568 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#569 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#570 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#571 linkCache_getLink no uid found +0s … 0.88s
#572 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#573 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#574 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#575 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#576 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#577 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#578 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#579 linkCache_getLink no uid found +0s … 0.88s
#580 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#581 linkCache_getLink using $NBC_LINKCACHE +0s … 0.88s
#582 linkCache_getLink no uid found +0.
001s … 0.882s
#583 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#584 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#585 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#586 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#587 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#588 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#589 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#590 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#591 linkCache_getLink no uid found +0s … 0.882s
#592 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#593 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#594 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#595 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#596 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.882s
#597 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#598 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#599 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#600 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#601 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#602 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#603 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#604 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#605 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#606 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#607 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#608 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#609 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#610 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.882s
#611 linkCache_getLink using $NBC_LINKCACHE +0s … 0.882s
#612 linkCache_getLink no uid found +0s … 0.882s
#613 linkCache_getLink no uid found +0s … 0.882s
#614 linkCache_getLink no uid found +0.002s … 0.884s
#615 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#616 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#617 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#618 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#619 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#620 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#621 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#622 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#623 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#624 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#625 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.884s
#626 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#627 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#628 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#629 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#630 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#631 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#632 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#633 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#634 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#635 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#636 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#637 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#638 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#639 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.884s
#640 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#641 linkCache_getLink using $NBC_LINKCACHE +0s … 0.884s
#642 linkCache_getLink no uid found +0s … 0.884s
#643 linkCache_getLink no uid found +0s … 0.884s
#644 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.885s
#645 linkCache_getLink using $NBC_LINKCACHE +0s … 0.885s
#646 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#647 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#648 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#649 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#650 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#651 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#652 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#653 linkCache_getLink using $NBC_LINKCACHE +0s … 0.
886s
#654 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#655 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#656 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#657 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#658 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#659 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#660 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#661 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#662 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#663 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#664 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#665 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#666 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#667 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.886s
#668 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#669 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#670 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#671 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#672 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#673 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#674 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#675 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#676 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#677 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#678 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#679 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#680 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#681 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.886s
#682 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#683 linkCache_getLink no uid found +0s … 0.886s
#684 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#685 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#686 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#687 linkCache_getLink no uid found +0s … 0.886s
#688 linkCache_getLink no uid found +0s … 0.886s
#689 linkCache_getLink using $NBC_LINKCACHE +0s … 0.886s
#690 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.888s
#691 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#692 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#693 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#694 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#695 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#696 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.888s
#697 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#698 linkCache_getLink no uid found +0s … 0.888s
#699 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#700 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#701 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#702 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#703 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#704 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#705 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#706 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#707 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#708 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#709 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#710 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.888s
#711 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#712 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#713 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#714 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#715 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#716 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#717 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#718 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#719 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#720 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#721 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#722 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#723 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#724 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.888s
#725 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#726 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#727 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#728 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#729 linkCache_getLink no uid found +0s … 0.888s
#730 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#731 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#732 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#733 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#734 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#735 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#736 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#737 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#738 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.888s
#739 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#740 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#741 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#742 linkCache_getLink using $NBC_LINKCACHE +0s … 0.888s
#743 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#744 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#745 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#746 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#747 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#748 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#749 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#750 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#751 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#752 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.889s
#753 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#754 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#755 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#756 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#757 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#758 linkCache_getLink no uid found +0s … 0.889s
#759 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#760 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#761 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#762 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#763 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#764 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#765 linkCache_getLink no uid found +0s … 0.889s
#766 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#767 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.889s
#768 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#769 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#770 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#771 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#772 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#773 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#774 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#775 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#776 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#777 linkCache_getLink using $NBC_LINKCACHE +0s … 0.889s
#778 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.89s
#779 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#780 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#781 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.891s
#782 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#783 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#784 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#785 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#786 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#787 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#788 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#789 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#790 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#791 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#792 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#793 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#794 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#795 linkCache_getLink no uid found +0s ..
. 0.891s
#796 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#797 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#798 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#799 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#800 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#801 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#802 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#803 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#804 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#805 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#806 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#807 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#808 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#809 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.891s
#810 linkCache_getLink no uid found +0s … 0.891s
#811 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#812 linkCache_getLink no uid found +0s … 0.891s
#813 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#814 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#815 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#816 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#817 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#818 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#819 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#820 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#821 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#822 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#823 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#824 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.891s
#825 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#826 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#827 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#828 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#829 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#830 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#831 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#832 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#833 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#834 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#835 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#836 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#837 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#838 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.891s
#839 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#840 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#841 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#842 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#843 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#844 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#845 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#846 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#847 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#848 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#849 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#850 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#851 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#852 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.891s
#853 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#854 linkCache_getLink no uid found +0s … 0.891s
#855 linkCache_getLink using $NBC_LINKCACHE +0s … 0.891s
#856 linkCache_getLink no uid found +0s … 0.891s
#857 linkCache_getLink using $NBC_LINKCACHE +0s … 0.892s
#858 linkCache_getLink no uid found +0s … 0.892s
#859 linkCache_getLink using $NBC_LINKCACHE +0s … 0.892s
#860 linkCache_getLink using $NBC_LINKCACHE +0s … 0.892s
#861 linkCache_getLink using $NBC_LINKCACHE +0s … 0.892s
#862 linkCache_getLink using $NBC_LINKCACHE +0s … 0.892s
#863 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.893s
#864 linkCache_getLink using $NBC_LINKCACHE +0s … 0.893s
#865 linkCache_getLink no uid found +0s … 0.893s
#866 linkCache_getLink using $NBC_LINKCACHE +0s … 0.893s
#867 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.893s
#868 linkCache_getLink using $NBC_LINKCACHE +0s … 0.893s
#869 linkCache_getLink using $NBC_LINKCACHE +0s … 0.893s
#870 linkCache_getLink using $NBC_LINKCACHE +0s … 0.893s
#871 linkCache_getLink using $NBC_LINKCACHE +0s … 0.893s
#872 linkCache_getLink using $NBC_LINKCACHE +0s … 0.893s
#873 linkCache_getLink using $NBC_LINKCACHE +0s … 0.893s
#874 linkCache_getLink using $NBC_LINKCACHE +0s … 0.893s
#875 linkCache_getLink using $NBC_LINKCACHE +0s … 0.893s
#876 linkCache_getLink using $NBC_LINKCACHE +0s … 0.893s
#877 linkCache_getLink using $NBC_LINKCACHE +0s … 0.893s
#878 linkCache_getLink using $NBC_LINKCACHE +0s … 0.893s
#879 linkCache_getLink using $NBC_LINKCACHE +0s … 0.893s
#880 linkCache_getLink no uid found +0s … 0.894s
#881 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.894s
#882 linkCache_getLink using $NBC_LINKCACHE +0s … 0.894s
#883 linkCache_getLink using $NBC_LINKCACHE +0s … 0.894s
#884 linkCache_getLink no uid found +0s … 0.894s
#885 linkCache_getLink using $NBC_LINKCACHE +0s … 0.894s
#886 linkCache_getLink using $NBC_LINKCACHE +0s … 0.894s
#887 linkCache_getLink using $NBC_LINKCACHE +0s … 0.894s
#888 linkCache_getLink using $NBC_LINKCACHE +0s … 0.894s
#889 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.896s
#890 linkCache_getLink using $NBC_LINKCACHE +0s … 0.896s
#891 linkCache_getLink using $NBC_LINKCACHE +0s … 0.896s
#892 linkCache_getLink no uid found +0s … 0.896s
#893 linkCache_getLink using $NBC_LINKCACHE +0s … 0.896s
#894 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.898s
#895 linkCache_getLink using $NBC_LINKCACHE +0s …
0.898s
#896 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#897 linkCache_getLink using $NBC_LINKCACHE +0s … 0.898s
#898 linkCache_getLink no uid found +0s … 0.898s
#899 linkCache_getLink no uid found +0.002s … 0.899s
#900 linkCache_getLink using $NBC_LINKCACHE +0s … 0.899s
#901 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.902s
#902 linkCache_getLink no uid found +0s … 0.902s
#903 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.903s
#904 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#905 linkCache_getLink no uid found +0s … 0.904s
#906 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#907 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#908 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#909 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#910 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.904s
#911 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#912 linkCache_getLink no uid found +0s … 0.904s
#913 linkCache_getLink no uid found +0s … 0.904s
#914 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#915 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#916 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#917 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#918 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#919 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#920 linkCache_getLink no uid found +0s … 0.904s
#921 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#922 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#923 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#924 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#925 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.904s
#926 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#927 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#928 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#929 linkCache_getLink using $NBC_LINKCACHE +0s … 0.904s
#930 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.906s
#931 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#932 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#933 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#934 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#935 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#936 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#937 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#938 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#939 linkCache_getLink no uid found +0s .
.. 0.906s
#940 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#941 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#942 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#943 linkCache_getLink no uid found +0s … 0.906s
#944 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#945 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#946 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#947 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#948 linkCache_getLink no uid found +0s … 0.906s
#949 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#950 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#951 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#952 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#953 linkCache_getLink no uid found +0s … 0.906s
#954 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.906s
#955 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#956 linkCache_getLink using $NBC_LINKCACHE +0s … 0.906s
#957 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.908s
#958 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#959 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#960 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#961 linkCache_getLink no uid found +0s … 0.908s
#962 linkCache_getLink no uid found +0s … 0.908s
#963 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#964 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#965 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#966 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#967 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#968 linkCache_getLink using $NBC_LINKCACHE +0s … 0.
908s
#969 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#970 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#971 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#972 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#973 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#974 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#975 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#976 linkCache_getLink using $NBC_LINKCACHE +0s … 0.908s
#977 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.91s
#978 linkCache_getLink using $NBC_LINKCACHE +0s … 0.91s
#979 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#980 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#981 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#982 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.911s
#983 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#984 linkCache_getLink no uid found +0s … 0.911s
#985 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#986 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#987 linkCache_getLink no uid found +0s … 0.911s
#988 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#989 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#990 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#991 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#992 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#993 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#994 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#995 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#996 linkCache_getLink using $NBC_LINKCACHE +0s … 0.911s
#997 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.911s
#998 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.913s
#999 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1000 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1001 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1002 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1003 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1004 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1005 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1006 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1007 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1008 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1009 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1010 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1011 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.913s
#1012 linkCache_getLink no uid found +0s … 0.913s
#1013 linkCache_getLink no uid found +0s … 0.913s
#1014 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1015 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1016 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1017 linkCache_getLink using $NBC_LINKCACHE +0s … 0.913s
#1018 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.915s
#1019 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1020 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1021 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1022 linkCache_getLink no uid found +0s … 0.915s
#1023 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1024 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1025 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.915s
#1026 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1027 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1028 linkCache_getLink no uid found +0s … 0.915s
#1029 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1030 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1031 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1032 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1033 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1034 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1035 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1036 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1037 linkCache_getLink using $NBC_LINKCACHE +0s … 0.915s
#1038 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.917s
#1039 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.917s
#1040 linkCache_getLink using $NBC_LINKCACHE +0s … 0.917s
#1041 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.918s
#1042 linkCache_getLink using $NBC_LINKCACHE +0s … 0.919s
#1043 linkCache_getLink using $NBC_LINKCACHE +0s … 0.919s
#1044 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.92s
#1045 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.922s
#1046 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.923s
#1047 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.924s
#1048 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.926s
#1049 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.927s
#1050 linkCache_getLink using $NBC_LINKCACHE +0s … 0.927s
#1051 linkCache_getLink using $NBC_LINKCACHE +0s … 0.927s
#1052 linkCache_getLink using $NBC_LINKCACHE +0s … 0.927s
#1053 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.927s
#1054 linkCache_getLink using $NBC_LINKCACHE +0s … 0.927s
#1055 linkCache_getLink using $NBC_LINKCACHE +0s … 0.927s
#1056 linkCache_getLink using $NBC_LINKCACHE +0s … 0.927s
#1057 linkCache_getLink using $NBC_LINKCACHE +0s … 0.927s
#1058 linkCache_getLink no uid found +0s … 0.927s
#1059 linkCache_getLink using $NBC_LINKCACHE +0s … 0.927s
#1060 linkCache_getLink using $NBC_LINKCACHE +0s … 0.927s
#1061 linkCache_getLink no uid found +0s … 0.927s
#1062 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1063 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1064 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1065 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1066 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1067 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.928s
#1068 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1069 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1070 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1071 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1072 linkCache_getLink no uid found +0s … 0.928s
#1073 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1074 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1075 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1076 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1077 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1078 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1079 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1080 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1081 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.928s
#1082 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1083 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1084 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1085 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1086 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1087 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1088 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1089 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1090 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1091 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1092 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1093 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1094 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1095 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.928s
#1096 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1097 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1098 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1099 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1101 linkCache_getLink no uid found +0s … 0.928s
#1102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1105 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1107 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1109 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.928s
#1110 linkCache_getLink using $NBC_LINKCACHE +0s … 0.928s
#1111 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.93s
#1112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.93s
#1113 linkCache_getLink no uid found +0s … 0.93s
#1114 linkCache_getLink no uid found +0s … 0.93s
#1115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.93s
#1116 linkCache_getLink using $NBC_LINKCACHE +0s … 0.93s
#1117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.93s
#1118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.93s
#1119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.93s
#1120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.93s
#1121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.93s
#1122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.93s
#1123 linkCache_getLink using $NBC_LINKCACHE +0s … 0.
93s
#1124 linkCache_getLink using $NBC_LINKCACHE +0s … 0.93s
#1125 linkCache_getLink using $NBC_LINKCACHE +0s … 0.93s
#1126 linkCache_getLink using $NBC_LINKCACHE +0s … 0.93s
#1127 linkCache_getLink using $NBC_LINKCACHE +0s … 0.93s
#1128 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.933s
#1129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s
#1130 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s
#1131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s
#1132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s
#1133 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s
#1134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s
#1135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s
#1136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s
#1137 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.933s
#1138 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s
#1139 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s
#1140 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s
#1141 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s
#1142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s
#1143 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s
#1144 linkCache_getLink using $NBC_LINKCACHE +0s … 0.933s
#1145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1147 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1148 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1149 linkCache_getLink no uid found +0s … 0.934s
#1150 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1151 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.934s
#1152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1153 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1154 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1155 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1157 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1158 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1160 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1161 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1162 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1164 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1165 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.934s
#1166 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1167 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1169 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1171 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1172 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1174 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1175 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1176 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1177 linkCache_getLink no uid found +0s … 0.934s
#1178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1179 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.934s
#1180 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1181 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1182 linkCache_getLink no uid found +0s … 0.934s
#1183 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1184 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1185 linkCache_getLink using $NBC_LINKCACHE +0s … 0.934s
#1186 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.937s
#1187 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s
#1188 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s
#1189 linkCache_getLink no uid found +0s … 0.937s
#1190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.937s
#1191 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.94s
#1192 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.942s
#1193 linkCache_getLink no uid found +0s .
.. 0.942s
#1194 linkCache_getLink using $NBC_LINKCACHE +0s … 0.942s
#1195 linkCache_getLink using $NBC_LINKCACHE +0s … 0.942s
#1196 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.943s
#1197 linkCache_getLink no uid found +0s … 0.943s
#1198 linkCache_getLink using $NBC_LINKCACHE +0s … 0.943s
#1199 linkCache_getLink using $NBC_LINKCACHE +0s … 0.943s
#1200 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.946s
#1201 linkCache_getLink using $NBC_LINKCACHE +0s … 0.946s
#1202 linkCache_getLink no uid found +0s … 0.946s
#1203 linkCache_getLink using $NBC_LINKCACHE +0s … 0.946s
#1204 min, max, avg, median took s +0.001s … 0.947s
#1205 linkCache_getLink using $NBC_LINKCACHE +0.023s … 0.969s
#1206 return log +0.004s … 0.973s
Intel Core i5 8250U Vs Intel Core i3 8130U Comparison in India: Benchmark, Specs and Performance
Laptop Chipsets
Hide Common features
Power |
||
| Fabrication process | 14 nm | 14 nm |
| TDP | 15 W | 15 W |
Max. temperature |
100°C | 100°C |
Laptops Chipsets
-
Lenovo IdeaPad 330 (81F500GMIN) Laptop (8th Gen Ci5/ 4GB/ 1TB/ Win10 Home/ 4GB Graph)
₹ 58,999
-
Lenovo Ideapad 330 (81DE01B1IN) Laptop (8th Gen Ci5/ 8GB/ 1TB/ Win 10)
₹ 44,258
-
Dell Inspiron 5570 Laptop (8th Gen Ci5/ 8GB/ 2TB/ Win10/ 4GB Graph)
₹ 51,990
-
Dell Inspiron 5570 Laptop (8th Gen Ci5/ 8GB/ 2TB/ Win10 Home/ 2GB Graph)
₹ 67,000
-
Acer One 14 Z2-485 Laptop (8th Gen Ci5/ 4GB/ 1TB/ DOS)
₹ 40,990
-
Acer One 14 Z2-485 Laptop (8th Gen Ci5/ 4GB/ 1TB/ Win10 Home)
₹ 38,989
-
Lenovo Ideapad 520 (81BF00AWIN) Laptop (8th Gen Ci5/ 8GB/ 2TB/ Win10/ 2GB Graph)
₹ 53,999
-
Lenovo Ideapad 520 (81BL00CSIN) Laptop (8th Gen Ci5/ 8GB/ 1TB/ Win10)
₹ 55,990
-
Lenovo Ideapad 520 (81BF00KSIN) Laptop (8th Gen Ci5/ 4GB/ 1TB/ Win10)
₹ 55,139
-
Lenovo Ideapad 520 (81BF00KTIH) Laptop (8th Gen Ci5/ 4GB/ 1TB/ Win10/ 2GB Graph)
₹ 51,950
-
Acer One 14 Z2-485 Laptop (8th Gen Ci3/ 4GB/ 1TB/ Win 10 Home)
₹ 34,300
-
HP 14-ck0159tu Laptop (8th Gen Core i3/ 4GB/ 1TB/ Win10)
₹ 40,800
-
Acer Swift 3 SF313-51 NX.
h4YSI.002 Laptop (8th Gen Core i3/ 4GB/ 256GB SSD/ Win10 Home)₹ 45,990
-
HP Chromebook x360 14-da0003TU Laptop (8th Gen Core i3/ 8GB/ 64GB eMMC/ Chrome OS)
₹ 51,297
-
Asus VivoBook S14 S410UA-EB796T Laptop (8th Gen Ci3/ 8GB/ 1TB 256GB SSD/Win10)
₹ 53,990
-
Lenovo V15 81YD001MIH Laptop (8th Gen Core i3/ 4GB/ 1TB/ Win10 Home)
₹ 36,000
-
Lenovo ThinkPad E480 20KQS1FU00 Laptop (8th Gen Ci3/ 4GB/ 1TB/ Win10 Pro)
₹ 46,189
-
Asus X543UA-DM841T Laptop (8th Gen Core i3/ 4GB/ 1TB/ Win10 Home)
₹ 33,999
-
Lenovo V14 81YA002GIH Laptop (8th Gen Core i3/ 4GB/ 1TB/ Windows 10)
₹ 33,300
-
Lenovo V14 81YA002VIH Laptop (8th Gen Core i3/ 4GB/ 256GB SSD/ FreeDOS)
₹ 36,900
General |
||
| Vendor | Intel | Intel |
| Released | August 21, 2017 | February 12, 2018 |
| Type | Laptop | Laptop |
| instruction set | x86-64 | x86-64 |
| Codename | Kaby Lake R | Kaby Lake |
| Model number | i5-8250U | i3-8130U |
| Socket | BGA-1356 | BGA-1356 |
| Integrated GPU | UHD Graphics 620 | UHD Graphics 620 |
Performance |
||
| Cores | 4 | 2 |
| Threads | 8 | 4 |
| Base Frequency | 1. 6 GHz |
2.2 GHz |
| Turbo Boost Frequency | 3.4 GHz | 3.4 GHz |
| Bus frequency | 100 MHz | 100 MHz |
| Multiplier | 16x | 24x |
| Bus Bandwidth | 4 GT/s | 4 GT/s |
| L1 Cache | 64K (per core) | 64K (per core) |
| L2 Cache | 256K (per core) | 256K (per core) |
| L3 Cache | 6MB (shared) | 4MB (shared) |
| Unlocked Multiplier | No | No |
IGPU |
||
| Integrated Graphics | Intel UHD Graphics 620 | Intel UHD Graphics 620 |
| GPU Base Clock | 300 MHz | 300 MHz |
| GPU Boost Clock | 1100 MHz | 1000 MHz |
| Shading Units | 192 | 192 |
| TMUs | 24 | 24 |
| ROPs | 3 | 3 |
| Execution Units | 24 | 24 |
| TGP | 15 W | 15 W |
Max. Resolution |
4096×2304 — 60 Hz | 4096×2304 — 60 Hz |
Memory |
||
| Memory types | DDR4-2400, LPDDR3-2133 | DDR4-2400, LPDDR3-2133 |
| Memory Size | 32 GB | 32 GB |
| Max. Memory Channels | 2 | 2 |
| Max. Memory Bandwidth | 37.5 GB/s | 37.5 GB/s |
| ECC Support | No | No |
Misc |
||
| PCI Express Version | 3.0 | 3.0 |
| PCI Express Lanes | 12 | 12 |
| Extended instructions | SSE4.1, SSE4.2, AVX-2 | SSE4.1, SSE4.2, AVX-2 |
| Official page | https://ark.intel.com/content/www/us/en/ark/products/124967/intel-core-i5-8250u-processor-6m-cache-up-to-3-40-ghz.html | https://ark.intel.com/content/www/us/en/ark/products/137977/intel-core-i3-8130u-processor-4m-cache-up-to-3-40-ghz. html |
Benchmarks |
||
| Cinebench R23 (Single-Core) | 896 | 896 |
| Cinebench R23 (Multi-Core) | 3063 | 2143 |
| Passmark CPU (Single-Core) | 1937 | 1953 |
| Passmark CPU (Multi-Core) | 5914 | 3680 |
| Geekbench 5 (Single-Core) | 871 | 815 |
| Geekbench 5 (Multi-Core) | 2924 | 1767 |
| iGPU FLOPS | 0.38 TFLOPS | 0.38 TFLOPS |
Browse Chipsets By
Similar Comparison
Popular Laptops
-
Asus VivoBook 15 (2020) M515DA-EJ301T Laptop (AMD Ryzen 3/ 4GB/ 1TB HDD/ Win 10 Home)
₹ 29,890
-
Lenovo Ideapad 330 (81D2008WIN) Lpatop (Ryzen 5 Quad Core/ 8GB/ 1TB/ freeDOS)
₹ 27,877
-
Lenovo IdeaPad D330 Laptop (Intel Celeron N4100/ 4GB/ 128GB SSD/ Win10)
₹ 29,990
-
HP 245 G7 Laptop (AMD Ryzen 3/ 4GB/ 256GB SSD/ FreeDos)
₹ 28,990
-
HP 245 G7 (1S3P0PA) Laptop (AMD Ryzen 3/ 4GB/ 1TB HDD/ FreeDos)
₹ 26,990
-
Dell E7440 Laptop (4th Gen Pentium Dual Core/ 16GB/ 500GB/ Win 8)
₹ 24,000
-
HP 250 G6 (4QG14PA) Laptop (7th Gen Core i3/ 4GB/ 1TB/ FreeDOS)
₹ 29,189
-
HP 15-db1069AU (9VJ83PA) Laptop (AMD Ryzen 3/ 4GB/ 1TB/ Win10)
₹ 26,590
-
Lenovo V110 (80TCA00PIH) Laptop (7th Gen AMD A6/ 4GB/ 1TB/ Win10)
₹ 23,999
-
HP 14q-cs0009TU (5DZ92PA) Laptop (7th Gen Ci3/ 4GB/ 1TB/ FreeDOS)
₹ 25,777
-
Asus VivoBook 14 (2020) X415JA-EK302TS Laptop (10th Gen Core i3/ 4GB/ 1TB/ Win10)
₹ 34,990
-
Dell Inspiron 3511 Laptop (10th Gen Core i3/ 8GB/ 256GB SSD/ Windows 10)
₹ 37,490
-
Dell Inspiron 3511 Laptop (11th Gen Core i3/ 8GB/ 1TB 256GB SSD/ Win10)
₹ 39,490
-
Dell Latitude 3410 Laptop (10th Gen Core i3/ 8GB/ 1TB/ FreeDOS)
₹ 34,100
-
Dell Inspiron 3501 Laptop (10th Gen Core i3/ 4GB/ 1TB/ Win10 Home)
₹ 37,498
-
Lenovo Ideapad Slim 3i (81WD00JYIN) Laptop (10th Gen Core i3/ 4GB/ 1 TB/ Win10)
₹ 39,990
-
HP 15s-GR0012AU Laptop (AMD Ryzen 3 3250U/ 8GB/ 1TB 256GB SSD/ Win10 Home)
₹ 37,990
-
Dell Latitude 3400 Laptop (8th Gen Core i3/ 4GB/ 1TB/ Ubuntu)
₹ 33,390
-
HP 250 G7 (2A9A5PA) Laptop (Celeron Dual Core/ 4GB/ 1TB/ Win10)
₹ 34,899
-
HP 250 G7 (1S5F6PA) Laptop (10th Gen Core i3/ 4GB/ 1TB/ FreeDOS)
₹ 33,990
-
Asus VivoBook 15 (2020) M515DA-EJ501T Laptop (AMD Ryzen 5/ 8GB/ 1TB HDD/ Win 10)
₹ 41,460
-
Asus VivoBook 15 (2020) M515DA-EJ521T Laptop (AMD Ryzen 5/ 4GB/ 256GB SSD/ Win 10)
₹ 41,500
-
Asus VivoBook 15 (2020) M515DA-EJ511T Laptop (AMD Ryzen 5/ 8GB/ 512GB SSD/ Win 10)
₹ 44,444
-
Asus VivoBook 14 (2020) X415JA-EK092TS Laptop (10th Gen Core i3/ 8GB/ 1TB 128GB SSD/ Win10)
₹ 40,990
-
Asus VivoBook 14 (2020) M415DA-EK512TS Laptop (AMD Ryzen 5/ 8GB/ 512GB SSD/ Win 10)
₹ 45,990
-
Asus VivoBook 14 (2020) X415JA-EK094TS Laptop (10th Gen Core i5/ 8GB/ 512GB SSD/ Win10)
₹ 49,794
-
Asus VivoBook 14 (2020) M415DA-EK502TS Laptop (AMD Ryzen 5/ 8GB/ 1TB HHD/ Win 10)
₹ 41,580
-
Asus VivoBook 14 (2020) X415JA-EK312TS Laptop (10th Gen Core i3/ 4GB/ 256GB SSD/ Win10)
₹ 47,699
-
Dell Inspiron 3511 Laptop (11th Gen Core i3/ 8GB/ 1TB 256GB SSD/ Win11)
₹ 44,150
-
Dell Inspiron 3511 Laptop (11th Gen Core i3/ 8GB/ 1TB HDD/ Win11)
₹ 42,460
-
Dell Latitude 3420 Laptop (11th Gen Core i5/ 16GB/ 1TB 256GB SSD/ Win10 Pro)
₹ 81,500
-
Dell Latitude 3420 Laptop (11th Gen Core i5/ 8GB/ 1TB 512GB SSD/ Win10 Pro)
₹ 88,270
-
Dell Latitude 3420 Laptop (11th Gen Core i5/ 8GB/ 1TB 256GB SSD/ Win10 Pro)
₹ 80,750
-
Dell Latitude 3420 Laptop (11th Gen Core i5/ 4GB/ 1TB HDD/ Win10 Pro)
₹ 77,499
-
Dell Latitude 3420 Laptop (11th Gen Core i5)
₹ 78,900
-
Dell Latitude 3410 Laptop (10th Gen Core i7/ 8GB/ 1TB/ Ubuntu)
₹ 77,730
-
Dell Latitude 3410 Laptop (10th Gen Core i7/ 8GB/ 1TB/ Win10 Pro)
₹ 86,240
-
Lenovo Thinkpad E14 (20YES00900) Laptop
₹ 79,999
-
Dell Inspiron 5518 Laptop (11th Gen Core i7/ 16GB/ 1TB SSD/ Win10/ 2GB Graph)
₹ 97,990
-
Dell Alienware M15 Laptop (8th Gen Ci5/ 8GB/ 1TB/ Win10/ 6GB Graph)
₹ 99,999
User Reviews
NA out of 5
0 Ratings & 0 Review
M,R,A
Md Rafik Alam
Posted on : 20th August 2021
Great Laptop
It’s a wonderful 15-inch laptop with a solid frame and a fine keyboard, but weak performance and a short battery life hold it back.
S,S
Sunil Sharma
Posted on : 6th August 2021
Good
Worth, good performance and windows and antivirus is pre activated
D,S
Dharmender Singh
Posted on : 31st July 2021
Performance
The Idea Pad 330 is both powerful and simple to use.
p
pravin
Posted on : 29th July 2021
Battery
I’m truly satisfied with the performance of the laptop and the battery backup especially considering the cost I paid for this
G
Guddu
Posted on : 16th July 2021
Performance
The Lenovo IdeaPad 330 is a budget 15-inch laptop with a solid keyboard and a sturdy design, but it suffers from weak performance and a short battery life.
R,D
Rohini Das
Posted on : 5th July 2021
Fast
I love the design of the laptop, very fast, never slowdown in multitasking, battery life is also great.
B,J
Bisweshwar Jaigopala
Posted on : 3rd July 2021
Screen pad
A laptop with a big screen and windows 10 just for people with a good buget laptop but only for use of kids.
N,D
Navneet Dhankar
Posted on : 25th June 2021
Performance
Impressed with the battery performance & display quality is good & battery last upto 2.5 hours
X,C
Xavier Clinton
Posted on : 6th June 2021
Daily purpose
Best suited laptop for your daily needs, i am using it from last 2 years. very happy.
V,G
Veermala Grewal
Posted on : 2nd June 2021
Nice
Nice in budget laptop, light weight , easy to carry, decent sound quality, battery backup is not upto the mark.
V
Virat
Posted on : 17th May 2021
Performance
Compact, stylish 2 in 1 laptop cum tablet that gives you flexibilty of laptop and tablet both.
A,C
Ajeet Chawla
Posted on : 10th May 2021
Slim
Easy to carry & work on this laptop It has very sleek and slim body with great performance.
T,G
Telurama Gopala
Posted on : 9th May 2021
Performance
Not charged for any powerbank and betary backup is poor, rest features are not so good and not so bad.
R
Rahul
Posted on : 2nd May 2021
Best laptop
Best laptop at this price range as compare to the other brands.
P
Porush
Posted on : 24th April 2021
Under budget laptop
Good all-rounder with best features
Detailed Comparison of Intel Core i5 8250U vs Intel Core i3 8130U
Intel Core i5 8250U has been announced on August 2017 whereas Intel Core i3 8130U has been announced on February 2018. Check out detailed comparison with key specs below:
Passmark Score: Intel Core i5 8250U vs Intel Core i3 8130U
Passmark Score consists of 4 parameters: CPU, GPU, MEM, and UX. The Passmark score measures the performance of the CPU. Passmark score is that measures a processor’s single core performance and evaluates multi core performance. The Passmark score value of Intel Core i5 8250U is 5914 whereas Passmark score value of Intel Core i3 8130U is 3680.
Memory Comparison: Intel Core i5 8250U vs Intel Core i3 8130U
Coming to the Memory, Intel Core i5 8250U has a memory size of 32 GB while Intel Core i3 8130U comes up with 32 GB.
Max. Memory Channels used in the first compared laptop chipset is 2 and Max. Memory Channels used in the other laptop chipset 2.
Performance Comparison: Intel Core i5 8250U vs Intel Core i3 8130U
Intel Core i5 8250U has 4 cores with 8 threads whereas Intel Core i3 8130U has 2 cores with 8 threads. Intel Core i5 8250U has base frequency of 1.6 GHz whereas Intel Core i3 8130Uhas base frequency of 2.2 GHz.
FAQs
Q. Which model has higher Geekbench 5 (multi-core) score — Intel Core i5 8250U or Intel Core i3 8130U?
Intel Core i5 8250U has higher Geekbench 5 score with total score of 2924 compare to Intel Core i3 8130U with a score of 1767.
Q. Which model has higher Passmark CPU (multi-core) score — Intel Core i5 8250U or Intel Core i3 8130U?
Intel Core i5 8250U has higher Passmark CPU score with total score of 5914 compare to Intel Core i3 8130U with a score of 3680.
Q. Which model has higher base frequency among Intel Core i5 8250U and Intel Core i3 8130U?
Intel Core i3 8130U has a higher base frequency of 2.
2 GHz compared to Intel Core i5 8250U with 1.6 GHz base frequency.
Q. Intel Core i5 8250U vs Intel Core i3 8130U, which model has higher bandwidth?
Both Intel Core i3 8130U and Intel Core i5 8250U have same max bandwidth of 37.5 GB/s.
Q. Which model has higher number of cores — Intel Core i5 8250U or Intel Core i3 8130U?
Intel Core i5 8250U has 4 cores which is higher than Intel Core i3 8130U that has 2 cores.
Q. What are some of the best laptops having — Intel Core i5 8250U in the market?
Q. What are some of the best laptops having — Intel Core i3 8130U in the market?
Intel Core i3-8130U vs Intel Core i5-8250U
Comparative analysis of Intel Core i3-8130U and Intel Core i5-8250U processors for all known characteristics in the following categories: Essentials, Performance, Memory, Graphics, Graphics interfaces, Graphics image quality, Graphics API support, Compatibility, Peripherals, Security & Reliability, Advanced Technologies, Virtualization.
Benchmark processor performance analysis: PassMark — Single thread mark, PassMark — CPU mark, Geekbench 4 — Single Core, Geekbench 4 — Multi-Core, GFXBench 4.0 — Car Chase Offscreen (Frames), GFXBench 4.0 — Manhattan (Frames), GFXBench 4.0 — T-Rex (Frames), GFXBench 4.0 — Car Chase Offscreen (Fps), GFXBench 4.0 — Manhattan (Fps), GFXBench 4.0 — T-Rex (Fps), 3DMark Fire Strike — Physics Score, CompuBench 1.5 Desktop — Face Detection (mPixels/s), CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s), CompuBench 1.5 Desktop — T-Rex (Frames/s), CompuBench 1.5 Desktop — Video Composition (Frames/s), CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s).
Intel Core i3-8130U
Buy on Amazon
vs
Intel Core i5-8250U
Buy on Amazon
Differences
Reasons to consider the Intel Core i3-8130U
- CPU is newer: launch date 5 month(s) later
- Around 1% better performance in PassMark — Single thread mark: 1937 vs 1922
- Around 4% better performance in Geekbench 4 — Single Core: 798 vs 770
| Launch date | 15 February 2018 vs 21 August 2017 |
| PassMark — Single thread mark | 1937 vs 1922 |
| Geekbench 4 — Single Core | 798 vs 770 |
Reasons to consider the Intel Core i5-8250U
- 2 more cores, run more applications at once: 4 vs 2
- 4 more threads: 8 vs 4
- Around 50% more L3 cache; more data can be stored in the L3 cache for quick access later
- Around 63% better performance in PassMark — CPU mark: 5915 vs 3635
- Around 73% better performance in Geekbench 4 — Multi-Core: 2911 vs 1680
- Around 19% better performance in GFXBench 4.
0 — Car Chase Offscreen (Frames): 1688 vs 1419 - Around 26% better performance in GFXBench 4.0 — Manhattan (Frames): 3199 vs 2539
- Around 38% better performance in GFXBench 4.0 — T-Rex (Frames): 5401 vs 3902
- Around 19% better performance in GFXBench 4.0 — Car Chase Offscreen (Fps): 1688 vs 1419
- Around 26% better performance in GFXBench 4.0 — Manhattan (Fps): 3199 vs 2539
- Around 38% better performance in GFXBench 4.0 — T-Rex (Fps): 5401 vs 3902
| Number of cores | 4 vs 2 |
| Number of threads | 8 vs 4 |
| L3 cache | 6 MB vs 4 MB |
| PassMark — CPU mark | 5915 vs 3635 |
| Geekbench 4 — Multi-Core | 2911 vs 1680 |
GFXBench 4. 0 — Car Chase Offscreen (Frames) |
1688 vs 1419 |
| GFXBench 4.0 — Manhattan (Frames) | 3199 vs 2539 |
| GFXBench 4.0 — T-Rex (Frames) | 5401 vs 3902 |
| GFXBench 4.0 — Car Chase Offscreen (Fps) | 1688 vs 1419 |
| GFXBench 4.0 — Manhattan (Fps) | 3199 vs 2539 |
| GFXBench 4.0 — T-Rex (Fps) | 5401 vs 3902 |
Compare benchmarks
CPU 1: Intel Core i3-8130U
CPU 2: Intel Core i5-8250U
| PassMark — Single thread mark |
|
|
||
| PassMark — CPU mark |
|
|
||
| Geekbench 4 — Single Core |
|
|
||
| Geekbench 4 — Multi-Core |
|
|
||
GFXBench 4. 0 — Car Chase Offscreen (Frames) |
|
|
||
| GFXBench 4.0 — Manhattan (Frames) |
|
|
||
| GFXBench 4.0 — T-Rex (Frames) |
|
|
||
GFXBench 4. 0 — Car Chase Offscreen (Fps) |
|
|
||
| GFXBench 4.0 — Manhattan (Fps) |
|
|
||
| GFXBench 4.0 — T-Rex (Fps) |
|
|
| Name | Intel Core i3-8130U | Intel Core i5-8250U |
|---|---|---|
| PassMark — Single thread mark | 1937 | 1922 |
| PassMark — CPU mark | 3635 | 5915 |
| Geekbench 4 — Single Core | 798 | 770 |
| Geekbench 4 — Multi-Core | 1680 | 2911 |
GFXBench 4. 0 — Car Chase Offscreen (Frames) |
1419 | 1688 |
| GFXBench 4.0 — Manhattan (Frames) | 2539 | 3199 |
| GFXBench 4.0 — T-Rex (Frames) | 3902 | 5401 |
| GFXBench 4.0 — Car Chase Offscreen (Fps) | 1419 | 1688 |
| GFXBench 4.0 — Manhattan (Fps) | 2539 | 3199 |
| GFXBench 4.0 — T-Rex (Fps) | 3902 | 5401 |
| 3DMark Fire Strike — Physics Score | 2652 | |
CompuBench 1. 5 Desktop — Face Detection (mPixels/s) |
27.08 | |
| CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s) | 279.761 | |
| CompuBench 1.5 Desktop — T-Rex (Frames/s) | 1.747 | |
| CompuBench 1.5 Desktop — Video Composition (Frames/s) | 19.883 | |
| CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s) | 30.385 |
Compare specifications (specs)
| Intel Core i3-8130U | Intel Core i5-8250U | |
|---|---|---|
| Architecture codename | Kaby Lake | Kaby Lake R |
| Launch date | 15 February 2018 | 21 August 2017 |
| Place in performance rating | 840 | 559 |
| Price now | $281 | |
| Processor Number | i3-8130U | i5-8250U |
| Series | 8th Generation Intel® Core™ i3 Processors | 8th Generation Intel® Core™ i5 Processors |
| Status | Launched | Launched |
| Value for money (0-100) | 5. 33 |
|
| Vertical segment | Mobile | Mobile |
| Launch price (MSRP) | $297 | |
| 64 bit support | ||
| Base frequency | 2.20 GHz | 1.60 GHz |
| Bus Speed | 4 GT/s OPI | 4 GT/s OPI |
| Die size | 123 mm | 123 mm |
| L1 cache | 256 KB | 256 KB |
| L2 cache | 1 MB | 1 MB |
| L3 cache | 4 MB | 6 MB |
| Manufacturing process technology | 14 nm | 14 nm |
| Maximum case temperature (TCase) | 72 °C | 72 °C |
| Maximum core temperature | 100°C | 100°C |
| Maximum frequency | 3. 40 GHz |
3.40 GHz |
| Number of cores | 2 | 4 |
| Number of threads | 4 | 8 |
| Max memory channels | 2 | 2 |
| Maximum memory bandwidth | 37.5 GB/s | 34.1 GB/s |
| Maximum memory size | 32 GB | 32 GB |
| Supported memory types | DDR4-2400, LPDDR3-2133 | DDR4-2400, LPDDR3-2133 |
| Device ID | 0x5917 | 0x5917 |
| Graphics base frequency | 300 MHz | 300 MHz |
| Graphics max dynamic frequency | 1. 00 GHz |
1.10 GHz |
| Intel® Clear Video HD technology | ||
| Intel® Clear Video technology | ||
| Intel® Quick Sync Video | ||
| Max video memory | 32 GB | 32 GB |
| Processor graphics | Intel® UHD Graphics 620 | Intel® UHD Graphics 620 |
| DisplayPort | ||
| DVI | ||
| eDP | ||
| HDMI | ||
| Number of displays supported | 3 | 3 |
| 4K resolution support | ||
| Max resolution over DisplayPort | [email protected] | [email protected] |
| Max resolution over eDP | [email protected] | [email protected] |
Max resolution over HDMI 1. 4 |
[email protected] | [email protected] |
| DirectX | 12 | 12 |
| OpenGL | 4.4 | 4.4 |
| Configurable TDP-down | 10 W | 10 W |
| Configurable TDP-down Frequency | 800 MHz | 800 MHz |
| Low Halogen Options Available | ||
| Max number of CPUs in a configuration | 1 | 1 |
| Package Size | 42mm X 24mm | 42mm X 24mm |
| Sockets supported | FCBGA1356 | FC-BGA1356 |
| Thermal Design Power (TDP) | 15 Watt | 15 Watt |
| Configurable TDP-up | 25 W | |
| Configurable TDP-up Frequency | 1. 80 GHz |
|
| Max number of PCIe lanes | 12 | 12 |
| PCI Express revision | 3.0 | 3.0 |
| PCIe configurations | 1×4, 2×2, 1×2+2×1 and 4×1 | 1×4, 2×2, 1×2+2×1 and 4×1 |
| Execute Disable Bit (EDB) | ||
| Intel® Identity Protection technology | ||
| Intel® Memory Protection Extensions (Intel® MPX) | ||
| Intel® OS Guard | ||
| Intel® Secure Key technology | ||
| Intel® Software Guard Extensions (Intel® SGX) | ||
| Intel® Trusted Execution technology (TXT) | ||
| Enhanced Intel SpeedStep® technology | ||
| Idle States | ||
| Instruction set extensions | Intel® SSE4. 1, Intel® SSE4.2, Intel® AVX2 |
Intel® SSE4.1, Intel® SSE4.2, Intel® AVX2 |
| Intel 64 | ||
| Intel® Advanced Vector Extensions (AVX) | ||
| Intel® AES New Instructions | ||
| Intel® Flex Memory Access | ||
| Intel® Hyper-Threading technology | ||
| Intel® My WiFi technology | ||
| Intel® Optane™ Memory Supported | ||
| Intel® Smart Response technology | ||
| Intel® Stable Image Platform Program (SIPP) | ||
| Intel® TSX-NI | ||
| Intel® Turbo Boost technology | ||
| Intel® vPro™ Platform Eligibility | ||
| Speed Shift technology | ||
| Thermal Monitoring | ||
| Intel® Virtualization Technology (VT-x) | ||
| Intel® Virtualization Technology for Directed I/O (VT-d) | ||
| Intel® VT-x with Extended Page Tables (EPT) | ||
| AMD Virtualization (AMD-V™) |
Intel Core i3-8130U vs.
Intel Core i5-8250U
Intel Core i3-8130U
The Intel Core i3-8130U operates with 2 cores and 4 CPU threads. It run at 3.40 GHz base 2.80 GHz all cores while the TDP is set at 15 W.The processor is attached to the BGA 1356 CPU socket. This version includes 4.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 Q1/2018
Intel Core i5-8250U
The Intel Core i5-8250U operates with 4 cores and 4 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
Intel Core i3-8130U
Intel Core i5-8250U
Compare Detail
| 2.20 GHz | Frequency | 1.60 GHz |
| 2 | Cores | 4 |
| 3.40 GHz | Turbo (1 Core) | 3.40 GHz |
| 2.80 GHz | Turbo (All Cores) | 2.30 GHz |
| Yes | Hyperthreading | Yes |
| No | Overclocking | No |
| normal | Core Architecture | normal |
|
Intel UHD Graphics 620 |
GPU |
Intel UHD Graphics 620 |
| 1.00 GHz | GPU (Turbo) | 1.10 GHz |
| 14 nm | Technology | 14 nm |
| 1.00 GHz | GPU (Turbo) | 1.10 GHz |
| 12 | DirectX Version | 12 |
| 3 | Max. displays | 3 |
| DDR4-2400 SO-DIMM | Memory | DDR4-2400 SO-DIMM |
| 2 | Memory channels | 2 |
| Max memory | ||
| Yes | ECC | No |
| — | L2 Cache | — |
4. 00 MB |
L3 Cache | 6.00 MB |
| 3.0 | PCIe version | 3.0 |
| 12 | PCIe lanes | 12 |
| 14 nm | Technology | 14 nm |
| BGA 1356 | Socket | BGA 1356 |
| 15 W | TDP | 15 W |
| VT-x, VT-x EPT, VT-d | Virtualization | VT-x, VT-x EPT, VT-d |
| Q1/2018 | Release date | Q3/2017 |
|
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 i3-8130U | Intel Core i5-8250U | |
| 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
Intel Core i5 8250U vs i3 8130U:
performance comparison
VS
Intel Core i5 8250U
Intel Core i3 8130U
Which is better: 4-core Intel Core i5 8250U at 1.
6 GHz or i3 8130U with 2 cores at 2.2 GHz? To find out, read our comparative testing of these 14nm laptop processors in popular benchmarks, games and heavy applications.
- Overview
- Differences
- Performance
- Features
- Comments
Overview
Overview and comparison of the main metrics from NanoReview
Single -flow performance
Rating in tests using one nucleus
Core i5 8250u
46 46
Core i3 8130u
46
Multi -flow performance
Tests in benchmarks where all nucleus
9 9,000 9,000 9,000
Core i5 8250u
16
Core i3 8130u
11
Energy Equality
Energy Effects Chip
Core i5 8250u 9000u 9000u
Core I3 8130U
2 total
Core i5 8250U
36
Core i3 8130U
34
Key differences
What are the main differences between 8130U and 8250U
Reasons to choose Intel Core i5 8250U
- Has 2 more physical cores
- Has 2 MB more L3 cache
Reasons to choose Intel Core i3 8130U
- Appeared 5 months later than rival
Benchmark tests
Compare the results of processor tests in benchmarks
Cinebench R23 (single core)
Core i5 8250U
899
Core i3 8130U
899
Cinebench R23 (multi-core)
Core i5 8250U
+44%
3061
Core i3 8130u
2123
Passmark CPU (single -core)
Core i5 8250u
1919
Core i3 8130u
1924
CPU (multi -minor) 9000.
000 CPU (multi -minute) 9000.000 CPU (multi -minute)
+64%
5920
Core i3 8130U
3616
Geekbench 5 (single core)
Core i5 8250U
+2%
855
Core i3 8130U
836
Geekbench 5 (multi-core)
Core i5 8250U
+61%
2829
Core i3 8130U
1760
▶️ Add your score to Cinebench R23
Specifications
List of full technical specifications of Intel Core i5 8250U and i3 8130U
General information
| Manufacturer | Intel | Intel |
| Release date | August 21, 2017 | February 12, 2018 |
| Type | For laptop | For laptop |
| Instruction set architecture | x86-64 | x86-64 |
| Codename | Kaby Lake R | Kaby Lake |
| Model number | i5-8250U | i3-8130U |
| Socket | BGA-1356 | BGA-1356 |
| Integrated graphics | UHD Graphics 620 | UHD Graphics 620 |
Performance
| Cores | 4 | 2 |
| Number of threads | 8 | 4 |
| Frequency | 1. 6 GHz |
2.2 GHz |
| Max. frequency in Turbo Boost | 3.4 GHz | 3.4 GHz |
| Bus frequency | 100 MHz | 100 MHz |
| Multiplier | 16x | 24x |
| Bus speed | 4 GT/s | 4 GT/s |
| Level 1 cache | 64KB (per core) | 64KB (per core) |
| Level 2 cache | 256KB (per core) | 256KB (per core) |
| Level 3 cache | 6MB (shared) | 4MB (shared) |
| Unlocked multiplier | No | No |
Power consumption
| Process technology | 14 nanometers | 14 nanometers |
| Power consumption (TDP) | 15W | 15W |
| Critical temperature | 100°C | 100°C |
| Integrated graphics | Intel UHD Graphics 620 | Intel UHD Graphics 620 |
| GPU frequency | 300 MHz | 300 MHz |
| Boost GPU frequency | 1100 MHz | 1000 MHz |
| Shader blocks | 192 | 192 |
| TMUs | 24 | 24 |
| ROPs | 3 | 3 |
| Computer units | 24 | 24 |
| TGP | 15W | 15W |
Max. resolution |
4096×2304 — 60Hz | 4096×2304 — 60Hz |
Igpu Flops
Core i5 8250u
0.38 Teraflops
Core i3 8130u
0.38 Teraflops
9000
Type Type Type
Other
| Official site | Site Intel Core i5 8250U | Site Intel Core i3 8130U |
| PCI Express Version | 3.0 | 3.0 |
| Max. PCI Express lanes | 12 | 12 |
| Extended instructions | SSE4.1, SSE4.2, AVX-2 | SSE4.1, SSE4.2, AVX-2 |
Poll
What processor do you think is the best?
Core i5 8250U
13 (39.
4%)
Core i3 8130U
20 (60.6%)
Total votes: 33
Competitors
1.
Intel Core i5 8250U vs i3 1115G4
2.
Intel Core i5 8250U vs AMD Ryzen 5 5500U
3.
Intel Core i5 8250U vs Apple M1
4.
Intel Core i5 8250U vs AMD Ryzen 3 5300U
5.
Intel Core i3 8130U vs i3 1115G4
What will you choose: Intel Core i3 8130U or i5 8250U?
Name
Message
Intel Core i3-8130U vs Intel Core i5-8250U: What is the difference?
49 BALLLA
Intel Core i3-8130U
49 Ballla
Intel Core i5-8250U
VS
64 Facts compared to
Intel I3-8130U 9000u 9000u 9000u
Is 8130U better than Intel Core i5-8250U?
- 0.
25MB/core more L2 cache per core? more memory bandwidth?
37.5GB/s vs 34.1GB/s - 0.5MB/core more L3 cache per core?
2MB/core vs 1.5MB/core - Has TrustZone?
Why is Intel Core i5-8250U better than Intel Core i3-8130U?
- 45.45% higher CPU speed?
4 x 1.6GHz vs 2 x 2.2GHz - 4 more CPU threads?
8 vs 4 - 1.61x higher PassMark score?
5941 vs 3688 - 2MB more L3 cache?
6MB vs 4MB - 23.03% higher Geekbench 5 multi-core result?
1971 vs 1602 - 100MHz faster GPU turbo speed?
1100MHz vs 1000MHz
What are the most popular comparisons?
Intel Core i3-8130u
VS
Intel Celeron N4020
Intel Core i5-8250U
VS
Intel Core I3-115G4
INTEL Core I3-8130U
9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000u 9000 VS 9000u 9000 VS 9000u 9000 VS 9000u 9000 VS AMD Ryzen 5 3500U
Intel Core i3-8130U
vs
AMD Athlon 300U
Intel Core i5-8250U
VS
Intel Core i3-1005g1
Intel Core i3-8130U
VS
Intel Core i3-10110u 9000u
Intel Core i5-8250u 9000u
AMD Ryzen 3 2200u
AMD RYZEN 3 2200U
AMD Ryzen 3 2200u
AMD
VS
AMD Ryzen 3 3200U
Intel Core i5-8250U
VS
Intel Core i7-6500U
Intel Core I3-8130U
VS
I3-1115GA Core I3-1115g Core
vs
AMD RYZEN 3 3200U
Intel Core i3-8130U
VS
Intel Pentium Gold 5405U
Intel Core i5-8250U
VS
AMD Ryzen 5 2500u
Intel Core INTEL COREN AMD A12-9720p
Intel Core i5-8250U
VS
AMD Ryzen 5 5500U
Intel Core i3-8130u 9000u
VS
AMD 3020e
I5-8250U
VS 9000 VS 9000 VS 9000 VS 9000 VS 9000 VS 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000U 7500U
Intel Core i5-8250U
VS
Intel Core i5-7200U
Complexation prices
Users reviews
General rating
Intel Core i3-8130U
1 Reviews 9000-9000 2 Relapses 9000.
9.0 /10
1 user reviews
Intel Core i5-8250U
5 user reviews
Intel Core i5-8250U
7.4 /10Ol000 /10
5 Votes
performance
7.0 /10
1 Votes
7.4 /10
5 Votes
Reliability
10.0 /10 9 9
1 Votes
8.8 /10
5 Votes 9000
2 x 2.2GHz
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.4GHz
3.4GHz
When the processor is running below its limits, it can jump to a higher clock speed to increase performance.
4. Has unlocked multiplier
✖Intel Core i3-8130U
✖Intel Core i5-8250U
Some processors come with an unlocked multiplier and are easier to overclock, allowing you to enjoy 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
2MB/core
1.5MB/core
More data can be stored in 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
37.5GB/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 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
Maximum memory (RAM).
6.bus baud rate
The bus is responsible for transferring data between different components of a computer or device.
7. Supports memory troubleshooting code
✖Intel Core i3-8130U
✖Intel Core i5-8250U
Memory error recovery code can detect and correct 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. (Intel Core i3-8130U)
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. (Intel Core i3-8130U)
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)
Unknown. Help us offer a price. (Intel Core i3-8130U)
Cinebench R20 is a benchmark that measures the performance of a multi-core processor by rendering a 3D scene.
5.Cinebench R20 result (single core)
Unknown. Help us offer a price. (Intel Core i3-8130U)
Cinebench R20 is a test to evaluate the performance of a single core processor when rendering a 3D scene.
6.
Geekbench 5 result (single core)
Geekbench 5 is a cross-platform test that measures the single core performance of a processor. (Source: Primate Labs, 2022)
7. Blender test result (bmw27)
Unknown. Help us offer a price. (Intel Core i3-8130U)
771.41seconds
The Blender benchmark (bmw27) measures CPU performance by rendering a 3D scene. More powerful processors can render a scene in a shorter time.
8.Blender result (classroom)
Unknown. Help us offer a price. (Intel Core i3-8130U)
2852.02seconds
The Blender benchmark (classroom) measures CPU performance by rendering a 3D scene. More powerful processors can render a scene in a shorter time.
9.performance per watt
Unknown. Help us offer a price. (Intel Core i3-8130U)
This means that the processor is more efficient, resulting in more performance per watt of power used.
Functions
1.uses multithreading
✔Intel Core i3-8130U
✔Intel Core i5-8250U
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
✔Intel Core i3-8130U
✔Intel Core i5-8250U
AES is used to speed up encryption and decryption.
3. Has AVX
✔Intel Core i3-8130U
✔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
✔Intel Core i3-8130U
✔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. (Intel Core i3-8130U)
Unknown. Help us offer a price. (Intel Core i5-8250U)
NEON provides faster media processing such as MP3 listening.
7. Has MMX
✔Intel Core i3-8130U
✔Intel Core i5-8250U
MMX is used to speed up tasks such as adjusting image contrast or adjusting volume.
8. Has TrustZone
✔Intel Core i3-8130U
✖Intel Core i5-8250U
The technology is integrated into the processor to ensure device security when using features such as mobile payments and streaming video using digital rights management technology ( DRM).
9.interface width
Unknown. Help us offer a price. (Intel Core i3-8130U)
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?
I5 8250u or i3 8130u • Web cheat sheet for internet entrepreneurs!
Contents
- 1 Benefits of
- 1.
1 Reasons to choose Intel Core i3-8130U - 1.2 Reasons to choose Intel Core i5-8250U
- 1.
- 2
- benchmark comparison
- 4 Why is Intel Core i5-8250U better than Intel Core i3-8130U?
- 4.1 What are the most popular comparisons?
- 5 General information
- 6 Performance
- 7 Memory
- 8 Functions
- 9 No. 10 — Intel Pentium N5000
- 10 No. 9 — AMD A12 9720p
- 11 No. 8 — AMD RYZEN 3 2200U
- 12 No. 7 — Intel Core I3 8130U
- 13 No. 6 — AMD Ryzen 5 2500u 900u
- 9 14 #5 — Intel Core i5 8250U
- 15 #4 — AMD Ryzen 7 2700U
- 16 #3 — Intel Core i7-8550U
- 17 #2 — Intel Core i7-7700HQ
- 18 #1 — Intel Core i7- 8750H
- 18.1 Recommended reading
Comparative analysis of the Intel Core i3-8130U and Intel Core i5-8250U processors by all known characteristics in the categories: General information, Performance, Memory, Graphics, Graphic interfaces, Image quality in graphics, Graphics API Support, Compatibility, Peripherals, Security and Reliability, Technology, Virtualization. Analysis of processor performance by benchmarks: PassMark — Single thread mark, PassMark — CPU mark, Geekbench 4 — Single Core, Geekbench 4 — Multi-Core, GFXBench 4.0 — Car Chase Offscreen (Frames), GFXBench 4.0 — Manhattan (Frames), GFXBench 4.0 — T-Rex (Frames), GFXBench 4.0 — Car Chase Offscreen (Fps), GFXBench 4.0 — Manhattan (Fps), GFXBench 4.0 — T-Rex (Fps), 3DMark Fire Strike — Physics Score, CompuBench 1.5 Desktop — Face Detection ( mPixels/s), CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s), CompuBench 1.5 Desktop — T-Rex (Frames/s), CompuBench 1.5 Desktop — Video Composition (Frames/s), CompuBench 1.5 Desktop — Bitcoin Mining ( mHash/s).
Benefits
Reasons to choose Intel Core i3-8130U
- Newer processor, release date difference 5 month(s)
- Performance in Geekbench 4 — Single Core about 1% better: 3703 vs 3659
| Features | |
| Production date | 15 February 2018 vs 21 August 2017 |
| Benchmarks | |
| PassMark — Single thread mark | 1929 vs 1926 |
| Geekbench 4 — Single Core | 3703 vs 3659 |
Reasons to choose Intel Core i5-8250U
- 2 more cores, run more applications simultaneously: 4 vs 2
- 4 more threads: 8 vs 4
- The L3 cache is approximately 50% larger, meaning more data can be stored in it for quick access
- Performance in PassMark — CPU mark approximately 52% higher: 7649vs 5018
- Geekbench 4 — Multi-Core performance about 56% better: 11192 vs 7168
- Performance in GFXBench 4.
0 — Car Chase Offscreen (Frames) about 24% better: 1667 vs 1342 - Performance in GFXBench 4.0 — Manhattan (Frames) about 34% better: 3153 vs 2357
- Approximately 35% better performance in GFXBench 4.0 — T-Rex (Frames): 5259 vs 3902
- Performance in GFXBench 4.0 — Car Chase Offscreen (Fps) about 24% more: 1667 vs 1342
- About 34% more performance in GFXBench 4.0 — Manhattan (Fps): 3153 vs 2357
- Performance in GFXBench 4.0 benchmark — T-Rex (Fps) about 35% more: 5259 vs 3902
| Features | |
| Number of cores | 4 vs 2 |
| Number of threads | 8 vs 4 |
| Level 3 cache | 6MB vs 4MB |
| Benchmarks | |
| PassMark — CPU mark | 7649 vs 5018 |
| Geekbench 4 — Multi-Core | 11192 vs 7168 |
GFXBench 4. 0 — Car Chase Offscreen (Frames) |
1667 vs 1342 |
| GFXBench 4.0 — Manhattan (Frames) | 3153 vs 2357 |
| GFXBench 4.0 — T-Rex (Frames) | 5259 vs 3902 |
| GFXBench 4.0 — Car Chase Offscreen (Fps) | 1667 vs 1342 |
| GFXBench 4.0 — Manhattan (Fps) | 3153 vs 2357 |
| GFXBench 4.0 — T-Rex (Fps) | 5259 vs 3902 |
Benchmark comparison
CPU 1: Intel Core i3-8130U
CPU 2: Intel Core i5-8250U
Why is Intel Core i3-8130U better than Intel Core05-8?
- Has TrustZone
Why is Intel Core i5-8250U better than Intel Core i3-8130U?
- 45.45% higher CPU clock speed
4 x 1.6GHz vs 2 x 2.2GHz - 4 more CPU threads
What are the most popular comparisons?
Intel Core i3-8130U
AMD Ryzen 3 3200U
Intel Core i5-8250U
AMD Ryzen 3 3200U
Intel Core i3-8130U
Intel Pentium Gold 5405U
Intel Core i5-8250U
AMD Ryzen 5 2500U
Intel Core i3-8130U
AMD RYZEN 3 2200U
Intel Core i5-8250U
Intel Core i3-8130U
AMD Athlon 300u
Intel Core i5-8250u
AMD Ryzen 5 3500U
INTEL CORE I3-81302 INTEL CORE I3-81302 INTEL CORE I3-81302 INTEL CORE INTEL CORE I3-81302 INTEL CORE INTEL CORE INTEL CORE INTEL CORE CORE INTL 7020u
Intel Core i5-8250u
Intel Core i3-8130u
Intel Core i5-8250U
AMD Athlon 300u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u 9000u Core I5-8250U CORE I5-8250U CORE I5-8250U CORE I5-8250UC Intel Core i3-8130U
Intel Core i5-8250U
AMD Ryzen 3 2200u
Intel Core i3-8130u 9000u
AMD Ryzen 5 2500u
Intel Core I5-8250u
Intel Core Core INTEL Core INTEL Core INTEL CORE INTL i3-1005G1
General information
The graphics processing unit (GPU) has a higher clock speed.
AMD Ryzen 7 Pro 3700U
32-bit operating system can support up to 4 GB of RAM. 64-bit allows more than 4 GB, which improves performance. It also allows you to run 64-bit applications.
Intel Core i3-8130U
Intel Core i5-8250U
With integrated graphics, you don’t need to buy a separate card.
Intel Core i3-8130U
Intel Core i5-8250U
A smaller size indicates a newer chip manufacturing process.
Huawei HiSilicon Kirin 980
When the GPU is running below its limits, it can jump to a higher clock speed to increase performance.
Intel Core i7-3940XM
The newer version of OpenGL, the better graphics quality in games.
AMD Ryzen 3 2300U
Performance
MediaTek Helio X30
2 x 2.6 & 4 x 2.2 & 4 x 1.9GHz
Intel Core i9-9980HK
When the processor is running below its limits, it can jump to a higher clock speed to increase performance.
Intel Core i5-8305G
More L2 scratchpad memory results in faster results in CPU and system performance tuning.
More L1 scratchpad results in faster results in CPU and system performance tuning.
Intel Core i9-9980HK
More L3 scratchpad memory results in faster results in CPU and system performance tuning.
Intel Core i9-9980HK
Memory
Can support faster memory that speeds up system performance.
HiSilicon Kirin 810
This is the maximum rate at which data can be read from or stored in memory.
Qualcomm Snapdragon 8cx
More memory channels increase the speed of data transfer between memory and processor.
Qualcomm Snapdragon 8cx
Maximum memory (RAM).
Intel Core i9-9980HK
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.
Huawei HiSilicon Kirin 980
Intel Core i3-8130U
Intel Core i5-8250U
The bus is responsible for transferring data between various components of a computer or device.
Intel Core i9-9980HK
Functions
Dynamic frequency scaling is a technology that allows the processor to conserve power and reduce noise when it is under light load.
Intel Core i3-8130U
Intel Core i5-8250U
It’s easier to get better quality using virtualization if it’s hardware supported.
Intel Core i3-8130U
Intel Core i5-8250U
NX bit helps protect your computer from virus attacks.
Intel Core i3-8130U
Intel Core i5-8250U
MMX is used to speed up tasks such as adjusting image contrast or adjusting volume.
Intel Core i3-8130U
Intel Core i5-8250U
AES is used to speed up encryption and decryption.
Intel Core i3-8130U
Intel Core i5-8250U
Technology is integrated into the processor to help secure the device when using features such as mobile payments and digital rights management (DRM) video streaming.
Notebooks are mobile versions of computers and, in most cases, they have weaker technical characteristics.
But that doesn’t mean a laptop can’t be powerful. Proponents of productive hardware, when buying a laptop, first of all pay attention to what processor is installed in it. But how do you know which processor is best for a laptop? To do this, we have created a rating that will compare different processors. With the help of it, it will be possible to find out which chipset for a laptop is the most powerful.
#10 — INTEL PENTIUM N5000
The INTEL PENTIUM N5000 processor is a quad-core system announced at the end of 2017 that runs at 1.1-2.7 GHz. It is built on the Gemini Lake platform. The 14-nm technical process was used in the manufacture.
There is an integrated graphics adapter, so that this processor can be equipped with a laptop without a graphics card. In addition, there is a built-in Wi-Fi module.
INTEL PENTIUM N5000 is a processor that is equipped with not the most powerful, but rather advanced devices. If you are going to play new games on your laptop, models with this chip are best avoided, but for office work or other simple tasks, this is a great solution.
#9 — AMD A12 9720P
AMD A12 9720P is a modern low voltage processor. The device operates at a frequency of 2.7 GHz. Overclocking allows you to increase the frequency to 3.6 GHz. Provide performance 4 cores, as well as one graphics. By the way, the graphics here are represented by the Radeon R7 chip.
Optimized manufacturing processes have increased the clock speed. The performance has also increased compared to previous models.
GPU performance is average here. This figure may vary depending on the amount of RAM used. In most laptop models with this processor, the filling will be able to pull not the most demanding games.
Overall, this is a good processor for an inexpensive laptop. State employees on its hardware basis look more than confident. But you will not find such a chip in more productive devices.
#8 — AMD Ryzen 3 2200U
The AMD Ryzen 3 2200U is the benchmark for entry-level processors. It is they who are equipped with the most worthy budget laptops.
The built-in RAM controller significantly expands the capabilities of this device.
The AMD Ryzen 3 2200U is a mobile APU for thin and light laptops. Compared to the Ryzen 3 2200U, the PRO version offers additional security features.
It includes two Zen cores clocked at 2.5-3.4GHz and offers SMT (four threads simultaneously) and 4MB L3 cache.
The integrated graphics card is called the Radeon RX Vega 3 and only offers 3 CUs (192 shaders) clocked at up to 1000 MHz. TDP is configurable between 12 and 25W (15W nominal).
#7 — Intel Core i3 8130U
The eighth generation Intel Core i3-8130U is a mid-range dual-core laptop processor. The first-generation Core i3 chips are lower mid-range processors, and the i3-8130U is already noticeably faster, so this is a mid-range model.
This advancement is made possible primarily by Intel’s TurboBoost technology.
TurboBoost allows you to get an increase in clock speed — in this case from the standard 2.2 GHz to 3.4 GHz, in situations where the computing task requires it.
In terms of real-world use, the i3-8130U is a great solution for everyday computing tasks such as web browsing, MS Office and other software.
The chipset noticeably improves performance even when playing multimedia. In terms of gaming, the i3-8130U with integrated Intel UHD 620 graphics is only capable of running light games.
But many of the most popular games, such as League of Legends or Minecraft, are not particularly demanding and can run smoothly on a laptop with such a processor.
#6 — AMD Ryzen 5 2500U
The AMD Ryzen 5 2500U is a 64-bit, quad-core x86 midrange microprocessor introduced by AMD in late 2017. This processor is based on the AMD Zen microarchitecture and is manufactured using 14nm technology. The
2500U operates at a base frequency of 2GHz with a TDP of 15W and a boost frequency of 3.
6GHz. This MPU supports up to 32GB of dual-channel DDR4-2400 memory and includes Radeon Vega 8 graphics running at up to 1.1GHz. This model supports configurable 12W TDP output and 25W TDP output.
The AMD Ryzen 5 2500U does a good job of keeping temperatures fairly low. This helps to avoid overheating and, as a result, rapid wear of the device.
This type of processor indicates that the laptop is a fairly confident model of the middle class.
#5 — Intel Core i5 8250U
The Intel Core i5-8250U is a power efficient quad-core SoC for laptops and ultrabooks. The chip is equipped with four cores, with a frequency of 1.6 GHz. With the use of Turbo Boost technology, it can reach 3.4 GHz and therefore also offers good short-term single-core speeds.
The GPU is now Intel UHD Graphics 620 but is otherwise identical to Intel HD Graphics 620. The integrated memory controller supports DDR4-2400/LPDDR3-2133 and dual-channel memory.
Integrated Intel UHD Graphics 620 (Intel Gen 9.
5) with fast dual-channel memory can achieve the performance of GeForce 920M.
The chip is manufactured in an advanced 14nm process with FinFET (14nm+) transistors, the same as the 7th generation of Lake Kaby processors. Intel is still equipping TDP with 15W, which is typical for ULV chips.
Depending on the usage scenario, TDP can vary from 7.5 (cTDP Down) to 25W.
#4 — AMD Ryzen 7 2700U
The AMD Ryzen 7 2700U is a mobile SoC that was announced in October 2017. It combines four Zen cores (8 threads) at 2.2 — 3.8 GHz with a Radeon RX Vega 10 graphics card with 10 CUs (640 shaders) at up to 1300 MHz.
The TDP can be configured by the laptop manufacturer from 12W to 25W (15W nominal) and so the APU is also suitable for thin and light laptops. The integrated dual-channel memory controller supports up to DDR4-2400 memory.
Of all the models that are currently used in modern laptops of all kinds, Zen cores have one of the best performance indicators.
So if the laptop socket is occupied by an AMD Ryzen 7 2700U processor, you can be sure that this is a high-end device.
No. 3 — Intel Core i7-8550U
Whatever it was about, in terms of choosing a processor, today Intel Core i7 chips win absolutely in all matters. This line is considered the very top and these are not empty words.
i7-8550U is a 64-bit quad-core microprocessor with x86 performance developed by Intel in mid-2017. This processor, based on an improved version of the Lake Kaby microarchitecture, is manufactured on the basis of the second generation Intel with a gain of 14nm +.
The I7-8550U runs at 1.8GHz with a TDP of 15W and Turbo Boost up to 4GHz. This MPU supports up to 32GB of dual-channel DDR4-2400 memory and includes an Intel UHD Graphics 620 IGP running at 300MHz with a burst rate of 1.15GHz.
This model has a configurable 10W TDP output at 800MHz and a 25W TDP output at 2GHz.
No. 2 — Intel Core i7-7700HQ
Another variation of the Intel Core i7 climbed into second place.
Representatives of the seventh generation are the most top solutions for laptops. So the i7-7700HQ gets only the most expensive laptop models.
This is a quad-core 8-thread processor that runs at 2.8 GHz. In Turbo Boost mode, the chipset accelerates to a clock frequency of 3.8 GHz. The cache memory in this model is 6 MB.
The i7-7700HQ is based on the 14nm process, like all models from this line. The integrated graphics processor is an Intel® HD Graphics 630 chip with a base graphics frequency of 350 MHz.
This is one of the options for a truly top-end laptop. A device with such a processor will be able to pull almost all games and will not be inferior in power to most personal computers.
#1 — Intel Core i7-8750H
The highest-end laptop processor today is the Intel Core i7-8750H. This is a six-core processor running on 12 threads.
The frequency of the processor cores was 2.2 GHz. If you enable the maximum acceleration mode, the clock frequency will increase to 4.
1 GHz. Made by Intel Core i7-8750H on 14 nm process technology.
All this makes it the best and completely innovative processor of our time. But this, of course, only applies to laptops. Processors for full-fledged computers are also more powerful.
In this rating, we reviewed the most powerful laptop processors currently in use. This is a very important indicator when choosing a laptop.
The performance of 4 cores, if any, and performance per core has the greatest impact on the result, since most games do not fully use more than 4 cores.
The speed of caches and working with RAM is also important.
Speed in office use
Core i5-8250U
57.1
Core i3-8109U
62.9 (+9.2%)
Performance in everyday work, such as browsers and office programs.
The performance of 1 core has the greatest impact on the result, since most of these applications use only one, ignoring the rest.
Similarly, many professional applications such as various CADs ignore multi-threaded performance.
Speed in heavy applications
Core i5-8250U
31.5 (+1.9%)
Core i3-8109U
30.9 maximum
The performance of all cores and their number have 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, certain periods of work can be demanding on the performance of one or two cores, for example, applying filters in the editor.
Data obtained from tests by users who tested their systems with and without overclocking. Thus, you see the average values corresponding to the processor.
Speed of numerical operations
Simple household tasks |
|
Core i5-8250U 54.2 Core i3-8109U 61.1 (+11.3%) |
Demanding games and tasks |
|
Core i5-8250U 30. Core i3-8109U 25.3 |
1 (+15.9%)
Extreme |
|
Core i5-8250U 6.8 (+26.5%) Core i3-8109U 5 |
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 of 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 R20 Single Core
Intel Core i5-8250U
348
Intel Core i3-8109U
366 (+4.9%)0003
1509 (+39.3%)
Intel Core i3-8109u
916
Cinebench R15 Single Core
Intel Core i5-8250U
157 (+2.5%)
30002 Intel Core I3-8109 9000 INTEL CORE INTEL CORE INTE
Geekbench 3 Single Core
Intel Core i5-8250U
3927
Intel Core i3-8109U
3956 (+0.7%)
Geekbench 3 Multi Core
Intel Core i5-8250U
11787 (+30.5% )
Intel Core i3-8109U
8197
Cinebench R11.5
Intel Core i5-8250U
1.78 (+5.1%)
Intel Core i3-8109U
1.69
1.69
.5
Intel Core i3-8109U
4.05
Passmark
Intel Core i5-8250u
5975 (+27.2%)
Intel Core i3-8109u
4351 9000 9000 9000 9000 9000. not filled in, so the tables may be missing information or missing existing features.
Basic
| Manufacturer | Intel | Intel |
| DescriptionInformation about the processor, taken from the official website of the manufacturer. | Intel® Core™ i5-8250U Processor (6M Cache, up to 3.40 GHz) | Intel® Core™ i3-8109U Processor (4M Cache, up to 3.60 GHz) |
| ArchitectureCode name for the microarchitecture generation. | Kaby Lake R | Coffee Lake |
| Process The manufacturing process, measured in nanometers. The smaller the technical process, the more perfect the technology, the lower the heat dissipation and power consumption. | 14 nm | 14 nm |
Date of issueMonth and year of the processor’s availability. |
10-2020 | 02-2021 |
| Model Official name. | i5-8250U | i3-8109U |
| Cores The number of physical cores. | 4 | 2 |
| ThreadsNumber of threads. The number of logical processor cores that the operating system sees. | 8 | 4 |
| Multi-Threading Technology With Intel’s Hyper-threading and AMD’s SMT technology, one physical core is recognized as two logical cores by the operating system, thereby increasing processor performance in multi-threaded applications. | Hyper-threading (note that some games may not work well with Hyper-threading, for maximum FPS you can disable the technology in the BIOS of the motherboard). |
Hyper-threading (note that some games may not work well with Hyper-threading, 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. | 1.6 GHz | 3GHz |
Turbo frequencyThe maximum frequency of one processor core in turbo mode. Manufacturers allow modern processors to independently increase the frequency of one or more cores under heavy load, due to which performance is noticeably increased. It may depend on the nature of the load, the number of loaded cores, temperature and the specified limits. Significantly affects the speed in games and applications that are demanding on the frequency of the CPU. |
3.4 GHz | 3.6 GHz |
| L3 cache size The third level cache acts as a buffer between the computer’s RAM and the processor’s level 2 cache. Used by all cores, the speed of information processing depends on the volume. | 6 MB | 4 MB |
| Instructions | 64-bit | 64-bit |
| Extended instruction set Allows you to speed up calculations, processing and execution of certain operations. Also, some games require instruction support. | SSE4.1/4.2, AVX2 | Intel® SSE4.1, Intel® SSE4.2, Intel® AVX2 |
Embedded Options Available Two housing versions. Standard and designed for mobile devices. In the second version, the processor can be soldered on the motherboard. |
No | No |
| Bus frequency The speed of communication with the system. | 4 GT/s OPI | 4 GT/s OPI |
| Number of QPI links | ||
| TDPThermal Design Power is an indicator that determines heat dissipation in standard operation. The cooler or water cooling system must be rated for a larger value. Remember that with a factory bus or manual overclocking, TDP increases significantly. | 15W | 28W |
| Cooling system specifications |
Video core
Integrated graphics core Allows you to use your computer without a discrete graphics card. The monitor is connected to the video output on the motherboard. If earlier integrated graphics made it possible to simply work at a computer, today it can replace budget video accelerators and makes it possible to play most games at low settings. |
Intel® UHD Graphics 620 | Intel® Iris™ Plus Graphics 655 |
| GPU base clockFrequency in 2D and idle. | 300 MHz | 300 MHz |
| Maximum GPU frequencyMaximum 3D frequency. | 1100 MHz | 1050MHz |
| Intel® Wireless Display (Intel® WiDi) Supports Wireless Display technology using the Wi-Fi 802.11n standard. Thanks to it, a monitor or TV equipped with the same technology does not require a cable to connect. | ||
Supported monitorsThe maximum number of monitors that can be connected to the integrated video core at the same time. |
3 | 3 |
RAM
| Maximum amount of RAMThe amount of RAM that can be installed on the motherboard with this processor. | 32 GB | 32 GB |
| Supported type of RAM The type of RAM depends on its frequency and timings (speed), availability, price. | DDR4-2400, LPDDR3-2133 | DDR4-2400, LPDDR3-2133 |
| RAM Channels The multi-channel memory architecture increases data transfer speed. On desktop platforms, two-channel, three-channel and four-channel modes are available. | 2 | 2 |
| RAM bandwidth | 34.1 GB/s | 37.5 GB/s |
ECC memory Support for error-correcting memory that is used in servers. Usually more expensive than usual and requires more expensive server components. However, second-hand server processors, Chinese motherboards and ECC memory sticks, which are sold relatively cheaply in China, have become widespread. |
No data | No data |
PCI
| PCI-E The PCI Express computer bus version. The bandwidth and power limit depend on the version. There is backward compatibility. | 3 | 3 |
| PCI configuration options | 1×4, 2×2, 1×2+2×1 and 4×1 | 1×4, 2×2, 1×2+2×1 and 4×1 |
| Number of PCI lanes | 12 | 1×4, 2×2, 1×2+2×1 and 4×1 |
Data security
AES-NI The AES command set extension speeds up applications that use appropriate encryption. |
No data | No data |
| Intel® Secure Key An RDRAND instruction that allows you to create a high performance random number generator. | No data | No data |
Decoration
| Dimensions | No data | No data |
| Supported sockets | No data | No data |
| Maximum processors per motherboard | No data | No data |
Which is better
Intel Core i5-8250U
- In complex multi-threaded applications, faster and outperforms by 2%.
- 2 more physical cores.
- 4 more threads.
Intel Core i3-8109U
- On average, gaming performance is 3% better.
- The speed of work in office applications and browsers is increased by 6%.
The performance of 4 cores, if any, and performance per core has the greatest impact on the result, since most games do not fully use more than 4 cores.
The speed of caches and working with RAM is also important.
Speed in office use
Core i5-8350U
57.1 (+4.4%)
Core i3-8130U
54.6
Performance in everyday work, such as browsing and office programs.
The performance of 1 core has the greatest impact on the result, since most of these applications use only one, ignoring the rest.
Similarly, many professional applications such as various CADs ignore multi-threaded performance.
Speed in heavy applications
Core i5-8350U
32.1 (+19.6%)
Core i3-8130U
25.8
maximum
The performance of all cores and their number have 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, certain periods of work can be demanding on the performance of one or two cores, for example, applying filters in the editor.
Data obtained from tests by users who tested their systems with and without overclocking. Thus, you see the average values corresponding to the processor.
Speed of numerical operations
Simple household tasks
Core i5-8350U
55.7 (+6.3%)
Core i3-8130U
52.2
Demanding games and tasks
Core i5-8350U
31.7 (+36%)
Core i3-8130U
20.3
Extreme
Core i5-8350U
7.
3 (+45.2%)
Core i3-8130U
4
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 of 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
Intel Core i5-8350U
886 (+37.2%)
Intel Core i3-8130U
9000
550
9000 9000 Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core Core
003
3002 (+53.
7%)
Intel Core i3-8130u
1391
Cinebench R15 Single Core
Intel Core i5-8350U
167 (+15.6%)
Intel Core I3-83303
Intel Core I3-000.1302 INTEL CORE INTE
Geekbench 3 Single Core
Intel Core i5-8350U
4157 (+13.4%)
Intel Core i3-8130U
3600
Geekbench 3 Multi Core
Intel Core i5-8350U
12257 (+42.3% )
Intel Core i3-8130U
7070
Cinebench R11.5
Intel Core i5-8350U
1.88 (+14.4%)
Intel Core i3-8130u
1.61
Cinebench R11.5
2 RETEL CORE (+39.4%) Intel Core i3-8130U
3.79
Passmark
Intel Core i5-8350U
6318 (+41.9%)
Intel Core i3-8130u
3672 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000 9000. not filled in, so the tables may be missing information or missing existing features.
Basic
Manufacturer Intel Intel DescriptionInformation about the processor, taken from the official website of the manufacturer. Intel® Core™ i5-8350U Processor (6M Cache, up to 3.60 GHz) Intel® Core™ i3-8130U Processor (4M Cache, up to 3.40 GHz) ArchitectureCode name for the microarchitecture generation. Kaby Lake R Kaby Lake Process The manufacturing process, measured in nanometers. The smaller the technical process, the more perfect the technology, the lower the heat dissipation and power consumption. 14 nm 14 nm Date of issueMonth and year of the processor’s availability. 10-2020 10-2020 Model Official name. i5-8350U i3-8130U Cores The number of physical cores. 4 2 ThreadsNumber of threads. The number of logical processor cores that the operating system sees. 8 4 Multi-Threading Technology With Intel’s Hyper-threading and AMD’s SMT technology, one physical core is recognized as two logical cores by the operating system, thereby increasing processor performance in multi-threaded applications. Hyper-threading (note that some games may not work well with Hyper-threading, for maximum FPS you can disable the technology in the BIOS of the motherboard). Hyper-threading (note that some games may not work well with Hyper-threading, 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. 1.7 GHz 2.2 GHz Turbo frequencyThe maximum frequency of one processor core in turbo mode. Manufacturers allow modern processors to independently increase the frequency of one or more cores under heavy load, due to which performance is noticeably increased. It may depend on the nature of the load, the number of loaded cores, temperature and the specified limits. Significantly affects the speed in games and applications that are demanding on the frequency of the CPU.
3.6 GHz 3.4 GHz L3 cache size The third level cache acts as a buffer between the computer’s RAM and the processor’s level 2 cache. Used by all cores, the speed of information processing depends on the volume. 6 MB 4 MB Instructions 64-bit 64-bit Extended instruction set Allows you to speed up calculations, processing and execution of certain operations. Also, some games require instruction support. SSE4.1/4.2, AVX2 Intel® SSE4.1, Intel® SSE4.2, Intel® AVX2 Embedded Options Available Two housing versions. Standard and designed for mobile devices. In the second version, the processor can be soldered on the motherboard.
No No Bus frequency The speed of communication with the system. 4 GT/s OPI 4 GT/s OPI Number of QPI links TDPThermal Design Power is an indicator that determines heat dissipation in standard operation. The cooler or water cooling system must be rated for a larger value. Remember that with a factory bus or manual overclocking, TDP increases significantly. 15W 15W Cooling system specifications Video core
Integrated graphics core Allows you to use your computer without a discrete graphics card. The monitor is connected to the video output on the motherboard. If earlier integrated graphics made it possible to simply work at a computer, today it can replace budget video accelerators and makes it possible to play most games at low settings.
Intel® UHD Graphics 620 Intel® UHD Graphics 620 GPU base clockFrequency in 2D and idle. 300 MHz 300 MHz Maximum GPU frequencyMaximum 3D frequency. 1100 MHz 1000 MHz Intel® Wireless Display (Intel® WiDi) Supports Wireless Display technology using the Wi-Fi 802.11n standard. Thanks to it, a monitor or TV equipped with the same technology does not require a cable to connect. Supported monitorsThe maximum number of monitors that can be connected to the integrated video core at the same time. 3 3 RAM
Maximum amount of RAMThe amount of RAM that can be installed on the motherboard with this processor. 32 GB 32 GB Supported type of RAM The type of RAM depends on its frequency and timings (speed), availability, price. DDR4-2400, LPDDR3-2133 DDR4-2400, LPDDR3-2133 RAM Channels The multi-channel memory architecture increases data transfer speed. On desktop platforms, two-channel, three-channel and four-channel modes are available. 2 2 RAM bandwidth 34.1 GB/s 34.1 GB/s ECC memory Support for error-correcting memory that is used in servers. Usually more expensive than usual and requires more expensive server components. However, second-hand server processors, Chinese motherboards and ECC memory sticks, which are sold relatively cheaply in China, have become widespread.
No data No data PCI
PCI-E The PCI Express computer bus version. The bandwidth and power limit depend on the version. There is backward compatibility. 3 3 PCI configuration options 1×4, 2×2, 1×2+2×1 and 4×1 1×4, 2×2, 1×2+2×1 and 4×1 Number of PCI lanes 12 1×4, 2×2, 1×2+2×1 and 4×1 Data security
AES-NI The AES command set extension speeds up applications that use appropriate encryption. No data No data Intel® Secure Key An RDRAND instruction that allows you to create a high performance random number generator. No data No data Decoration
Dimensions No data No data Supported sockets No data No data Maximum processors per motherboard No data No data Which is better
Intel Core i5-8350U
- On average, gaming performance is 6% better.
- Work speed in office applications and browsers is increased by 3%.
- In complex multi-threaded applications, faster and outperforms by 3%.
- The number of physical cores is 2 more.
- The number of threads is 4 more.
Intel Core i3-8130U
- The base clock is 0.5 GHz higher.
What are similar
- Prices for new processors are approximately equal.
I5 8250u or i3 8130u — Dudom
Comparative analysis of Intel Core i3-8130U and Intel Core i5-8250U processors by all known characteristics in the categories: General information, Performance, Memory, Graphics, Graphic interfaces, Image quality in graphics, Graphics API Support, Compatibility, Peripherals, Security and Reliability, Technology, Virtualization. Analysis of processor performance by benchmarks: PassMark — Single thread mark, PassMark — CPU mark, Geekbench 4 — Single Core, Geekbench 4 — Multi-Core, GFXBench 4.0 — Car Chase Offscreen (Frames), GFXBench 4.0 — Manhattan (Frames), GFXBench 4.0 — T-Rex (Frames), GFXBench 4.0 — Car Chase Offscreen (Fps), GFXBench 4.0 — Manhattan (Fps), GFXBench 4.
0 — T-Rex (Fps), 3DMark Fire Strike — Physics Score, CompuBench 1.5 Desktop — Face Detection ( mPixels/s), CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s), CompuBench 1.5 Desktop — T-Rex (Frames/s), CompuBench 1.5 Desktop — Video Composition (Frames/s), CompuBench 1.5 Desktop — Bitcoin Mining ( mHash/s).
Benefits
Reasons to choose Intel Core i3-8130U
- Newer processor, release date difference 5 month(s)
- Approximately 20% better performance in Geekbench 4 — Single Core benchmark: 796 vs 661
Features Production date 15 February 2018 vs 21 August 2017 Benchmarks Geekbench 4 — Single Core 796 vs 661 Reasons to choose Intel Core i5-8250U
- 2 more cores, the ability to run more applications simultaneously: 4 vs 2
- 4 more threads: 8 vs 4
- The L3 cache is approximately 50% larger, meaning more data can be stored in it for quick access
- Performance in PassMark benchmark — CPU mark about 53% higher: 7644 vs 5005
- Approximately 62% improvement in Geekbench 4 — Multi-Core benchmark: 2713 vs 1672
- Performance in GFXBench 4.
0 — Car Chase Offscreen (Frames) about 24% better: 1670 vs 1342
- Performance in GFXBench 4.0 — Manhattan (Frames) about 34% better: 3169 vs 2357
- About 38% better performance in GFXBench 4.0 — T-Rex (Frames): 5386 vs 3902
- Performance in GFXBench 4.0 benchmark — Car Chase Offscreen (Fps) about 24% more: 1670 vs 1342
- Approximately 34% more performance in GFXBench 4.0 — Manhattan (Fps): 3169vs 2357
- Performance in GFXBench 4.0 benchmark — T-Rex (Fps) about 38% more: 5386 vs 3902
Features Number of cores 4 vs 2 Number of threads 8 vs 4 Level 3 cache 6MB vs 4MB Benchmarks PassMark — CPU mark 7644 vs 5005 Geekbench 4 — Multi-Core 2713 vs 1672 GFXBench 4. 0 — Car Chase Offscreen (Frames)
1670 vs 1342 GFXBench 4.0 — Manhattan (Frames) 3169 vs 2357 GFXBench 4.0 — T-Rex (Frames) 5386 vs 3902 GFXBench 4.0 — Car Chase Offscreen (Fps) 1670 vs 1342 GFXBench 4.0 — Manhattan (Fps) 3169 vs 2357 GFXBench 4.0 — T-Rex (Fps) 5386 vs 3902 Benchmark comparison
CPU 1: Intel Core i3-8130U
CPU 2: Intel Core i5-8250Uis better than Intel0 Core i3-823?
- Has TrustZone
Why is Intel Core i5-8250U better than Intel Core i3-8130U?
- 45.45% higher CPU clock speed
4 x 1.6GHz vs 2 x 2.2GHz - 4 more CPU threads
What are the most popular comparisons?
Intel Core i3-8130u
Intel Core i5-8250U
AMD Ryzen 3 3200U
Intel Core i3-8130U
AMD Ryzen 3 3200U
Intel Core I5-8250U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U 9000U RY i3-8130U
Intel Pentium Gold 5405U
Intel Core i5-8250U
AMD Ryzen 5 2500U
Intel Core i3-8130u
Intel Core i5-8250u
Intel Core i3-8130U
AMD Ryzen 5 3500U
Intel Core
AMD AMD ATHOLON 300000 INTEL CORETEL CORETEL CORETEL COREN 300u
Intel Core i5-8250u
Intel Core i3-8130U
AMD Ryzen 3 2200u
Intel Core i5-8250U 9000u
AMD Ryzen 3 2200U
Intel Core I3-8130U
9000u 9000u
I Intel Core i5-8250U
AMD RYZEN 3 3300U
Intel Core i3-8130U
Intel Core i5-8250u 9000u
Intel Core i5-8265U
Intel Core 9000u
AMD Ryzen 5 2500U
INTEL CORE Core i5-10210U
The graphics processing unit (GPU) has a higher clock speed.
AMD Ryzen 7 Pro 3700U
32-bit operating system can support up to 4 GB of RAM. 64-bit allows more than 4 GB, which improves performance. It also allows you to run 64-bit applications.
Intel Core i3-8130U
Intel Core i5-8250U
With integrated graphics, you don’t need to buy a separate card.
Intel Core i3-8130U
Intel Core i5-8250U
A smaller size indicates a newer chip manufacturing process.
Qualcomm Snapdragon 765
When the GPU is running below its limits, it can jump to a higher clock speed to increase performance.
Intel Core i7-3940XM
The newer version of OpenGL, the better graphics quality in games.
AMD Ryzen 3 2300U
Performance
MediaTek Helio X30
2 x 2.6 & 4 x 2.2 & 4 x 1.9GHz
Intel Core i9-9980HK
When the processor is running below its limits, it can jump to a higher clock speed to increase performance.
Intel Core i5-8305G
More L1 scratchpad memory results in faster results in CPU and system performance tuning.
Intel Core i9-9980HK
More L3 scratchpad memory results in faster results in CPU and system performance tuning.
Intel Core i9-9980HK
More L2 scratchpad memory results in faster results in CPU and system performance tuning.
Memory
Can support faster memory that speeds up system performance.
HiSilicon Kirin 810
This is the maximum rate at which data can be read from or stored in memory.
Qualcomm Snapdragon 8cx
More memory channels increase the speed of data transfer between memory and processor.
Qualcomm Snapdragon 8cx
Maximum memory (RAM).
Intel Core i9-9980HK
Memory error recovery code can detect and correct data corruption. It is used when necessary to avoid distortion, such as in scientific computing or when starting a server.
Qualcomm Snapdragon 730G
Intel Core i3-8130U
Intel Core i5-8250U
The bus is responsible for transferring data between various components of a computer or device.
Intel Core i9-9980HK
Features
Dynamic frequency scaling is a technology that allows the processor to conserve power and reduce noise when it is under light load.
Intel Core i3-8130U
Intel Core i5-8250U
It’s easier to get better quality using virtualization if it’s hardware supported.
Intel Core i3-8130U
Intel Core i5-8250U
MMX is used to speed up tasks such as adjusting image contrast or adjusting volume.
Intel Core i3-8130U
Intel Core i5-8250U
NX bit helps protect your computer from virus attacks.
Intel Core i3-8130U
Intel Core i5-8250U
AES is used to speed up encryption and decryption.
Intel Core i3-8130U
Intel Core i5-8250U
Technology is integrated into the processor to help secure the device when using features such as mobile payments and digital rights management (DRM) video streaming.
No. Model Frequency (MHz) Turbo (MHz) L2+L3 cache (Kb) FSB (MHz) Cores / Threads TDP (W) Process (nm) 64-bit SuperPI 1M SuperPI 2M SuperPI 32M 3DMark06 Cinebench R11. 5 CPU
1 1600 3400 1024 + 6144 0 4/8 15 14 + 10.9 24.9 0.0 6002 6.0 2 2500 3100 512 + 3072 0 2/4 15 14 + 12.3 28.3 642.8 4225 3.6 3 2200 3400 1024 + 4096 0 2/4 15 14 + 0.0 0.0 0.0 0 0.0 Toshiba Satellite L850-C6S processor replacement
Hello SERGEI25! I have exactly the same laptop. I would like to know if V.
A brief overview of MSI GP65
In fact, for a long time in MSI laptops, PWM was used only at brightnesses below 30%, and those.
Notebook HP x360 11nr
Either *** cable, or hard dropped, do not agree .. theoretically still possible.
Question about compatibility and supported memory modules
I want to increase the RAM on my laptop: HP Pavilion 17-f260ur S/N: 5CD5068RGZ P/N.
Toshiba Satellite L300
Who put T9600/T9400 in it and so on? I want to upgrade
Acer Aspire 5553G
Hello everyone, what a powerful processor to put on the Aspire 5553G P544G50Miks (AMD)
Dell Vostro 13 5390 is the best in the business
An excellent combination of parameters and the absence of marketing quirks, such as erg.
Acer Aspire 5551G
I have an acer v3-551g-10466g75makk, I need to replace the motherboard with which one.
Acer Aspire 5742G-386G32Mnkk
user Sasha277, and how did it get better, what changes? I also thought about appr.
Acer Aspire 5100
My computer. 5100 (5101 is what the BIOS shows).