Notebookcheck Logo

Intel Core i3-4120U vs Intel Core i3-4000M

Intel Core i3-4120U

► remove from comparison Intel 4120U

The Intel Core i3-4120U is an ULV (ultra low voltage) dual-core processor for ultrabooks launched in Q2 2014. It is based on the Haswell architecture and is manufactured in 22nm. Due to Hyper-Threading, the two cores can handle up to four threads in parallel, leading to better utilization of the CPU. Each core offers a base speed of 2.0 GHz and includes no Turbo Boost support.

Haswell is the successor to the Ivy Bridge architecture with improvements on both GPU and CPU performance. The CPUs are produced in 22nm and offer an optimized branch prediction as well as additional execution ports, improving performance per clock by almost 10 percent. Furthermore, new features like AVX2 and FMA should increase the performance in future applications.

According to the identical clock rate, the Core i3-4120U offers the same performance as the Core i3-4158U (28 W TDP). Thus, the CPU has sufficient power for office and multimedia purposes as well as most applications.

The integrated HD Graphics 4400 offers 20 Execution Units (EUs) clocked at 200 - 1000 MHz with Turbo Boost, making it somewhat faster than the former HD Graphics 4000 at similar clock speeds. However, the HD 4400 is somewhat slower than the HD 5000 of other ULV models.

The Core i3-4120U is rated at a TDP of 15 W including the graphics card, memory controller, VRMs and the integrated chipset. Therefore, the CPU is suited for small ultrabooks 11-inches or greater.

Intel Core i3-4000M

► remove from comparison Intel 4000M

The Intel Core i3-4000M is a middle-class dual-core processor for laptops launched in Q2 2013. It is based on the Haswell architecture and is manufactured in 22nm. Due to Hyper-Threading, the two cores can handle up to four threads in parallel leading to better utilization of the CPU. Each core offers a base speed of 2.4 GHz and includes no Turbo Boost support.

Haswell is the successor to the Ivy Bridge architecture with improvements on both GPU and CPU performance. The CPUs are produced in 22nm and offer an optimized branch prediction as well as additional execution ports. Furthermore, new features like AVX2 and FMA should increase the performance in future applications.

Due to these changes, the performance per clock has been improved by almost 10 percent compared to Ivy Bridge. Therefore, the i3-4000M is about as fast as the former Sandy Bridge model i5-2410M.

The integrated Intel HD Graphics 4600 offers 20 Execution Units (EUs) clocked at 400 MHz up to 1100 MHz with Turbo Boost, making it about 30 % faster than a similarly clocked HD 4000.

The i3-4000M is rated at a TDP of 37 W including the graphics card, memory controller and VRMs. Therefore, the CPU is suited for laptops 14-inches or greater.

show full text
ModelIntel Core i3-4120UIntel Core i3-4000M
SeriesIntel Core i3Intel Core i3
CodenameHaswellHaswell
Series: Core i3 Haswell
Intel Core i3-4110M compare2.6 GHz2 / 43 MB
Intel Core i3-4100M compare2.5 GHz2 / 43 MB
Intel Core i3-4000M2.4 GHz2 / 43 MB
Intel Core i3-4100E compare2.4 GHz2 / 43 MB
Intel Core i3-4158U compare2 GHz2 / 43 MB
» Intel Core i3-4120U2 GHz2 / 43 MB
Intel Core i3-4030U compare1.9 GHz2 / 43 MB
Intel Core i3-4025U compare1.9 GHz2 / 43 MB
Intel Core i3-4100U compare1.8 GHz2 / 43 MB
Intel Core i3-4010U compare1.7 GHz2 / 43 MB
Intel Core i3-4005U compare1.7 GHz2 / 43 MB
Intel Core i3-4102E compare1.6 GHz2 / 43 MB
Intel Core i3-4030Y compare1.6 GHz2 / 43 MB
Intel Core i3-4020Y compare1.5 GHz2 / 43 MB
Intel Core i3-4012Y compare1.5 GHz2 / 43 MB
Intel Core i3-4010Y compare1.3 GHz2 / 43 MB
Intel Core i3-4110M compare2.6 GHz2 / 43 MB
Intel Core i3-4100M compare2.5 GHz2 / 43 MB
» Intel Core i3-4000M2.4 GHz2 / 43 MB
Intel Core i3-4100E compare2.4 GHz2 / 43 MB
Intel Core i3-4158U compare2 GHz2 / 43 MB
Intel Core i3-4120U2 GHz2 / 43 MB
Intel Core i3-4030U compare1.9 GHz2 / 43 MB
Intel Core i3-4025U compare1.9 GHz2 / 43 MB
Intel Core i3-4100U compare1.8 GHz2 / 43 MB
Intel Core i3-4010U compare1.7 GHz2 / 43 MB
Intel Core i3-4005U compare1.7 GHz2 / 43 MB
Intel Core i3-4102E compare1.6 GHz2 / 43 MB
Intel Core i3-4030Y compare1.6 GHz2 / 43 MB
Intel Core i3-4020Y compare1.5 GHz2 / 43 MB
Intel Core i3-4012Y compare1.5 GHz2 / 43 MB
Intel Core i3-4010Y compare1.3 GHz2 / 43 MB
Clock2000 MHz2400 MHz
L1 Cache128 KB128 KB
L2 Cache512 KB512 KB
L3 Cache3 MB3 MB
Cores / Threads2 / 42 / 4
TDP15 Watt37 Watt
Technology22 nm22 nm
max. Temp.100 °C100 °C
FeaturesHD Graphics 4400 (200 - 1000 MHz), DDR3(L)-1600 Memory Controller, HyperThreading, AVX, AVX2, Quick Sync, Virtualization, AES-NIHD Graphics 4600 (400 - 1100 MHz), DDR3(L)-1600 Memory Controller, HyperThreading, AVX, AVX2, Quick Sync, Virtualization
iGPUIntel HD Graphics 4400 (200 - 1000 MHz)Intel HD Graphics 4600 (400 - 1100 MHz)
Architecturex86x86
$281 U.S.$225 U.S.
Announced
ManufacturerIntel Core i3 4120UIntel Core i3 4000M
Transistors960 Million
Die Size130 mm2
SocketrPGA

Benchmarks

Cinebench R15 - Cinebench R15 CPU Multi 64 Bit
100%
1 4000M +
min: 236     avg: 239.8     median: 240 (2%)     max: 243 Points
Cinebench R15 - Cinebench R15 CPU Single 64 Bit
100%
1 4000M +
min: 91     avg: 94.2     median: 95 (33%)     max: 96 Points
Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
100%
1 4000M +
min: 2.55     avg: 2.6     median: 2.6 (5%)     max: 2.62 Points
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
100%
1 4000M +
min: 1     avg: 1.1     median: 1.1 (3%)     max: 1.08 Points
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
100%
1 4000M +
min: 3542     avg: 3570     median: 3581 (32%)     max: 3588 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
100%
1 4000M +
min: 7994     avg: 8049     median: 8042 (11%)     max: 8111 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
100%
1 4000M +
min: 10239     avg: 10315     median: 10329 (9%)     max: 10361 Points
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
100%
1 4000M +
min: 4651     avg: 4662     median: 4664 (28%)     max: 4669 Points
wPrime 2.10 - wPrime 2.0 1024m *
100%
1 4000M +
min: 631     avg: 649     median: 635 (8%)     max: 682 s
wPrime 2.10 - wPrime 2.0 32m *
100%
1 4000M +
min: 19.91     avg: 20.6     median: 20 (4%)     max: 22 s
X264 HD Benchmark 4.0 - x264 Pass 2
100%
1 4000M +
min: 15     avg: 15.2     median: 15.2 (7%)     max: 15.3 fps
X264 HD Benchmark 4.0 - x264 Pass 1
100%
1 4000M +
min: 78     avg: 79.1     median: 79.1 (21%)     max: 80.2 fps
3DMark 06 - CPU - 3DMark 06 - CPU
100%
1 4000M +
3098 Points (7%)
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
100%
1 4000M +
min: 15.78     avg: 16     median: 16 (3%)     max: 16.1 s
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
100%
1 4000M +
min: 35.79     avg: 35.8     median: 35.8 (2%)     max: 35.84 s
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
100%
1 4000M +
min: 799     avg: 808     median: 802 (4%)     max: 824 s
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
100%
1 4000M +
41500 MIPS (20%)
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
100%
1 4000M +
31000 MFLOPS (24%)
Windows 7 Experience Index - Win7 CPU
100%
1 4000M +
6.9 Points (88%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
100%
1 4000M +
min: 8115     avg: 8398     median: 8398 (9%)     max: 8681 Points
3DMark 11 - 3DM11 Performance Physics
100%
1 4000M +
min: 3054     avg: 3176     median: 3161 (11%)     max: 3304 Points
3DMark - 3DMark Ice Storm Physics
100%
1 4000M +
min: 25742     avg: 28030     median: 27649 (18%)     max: 30127 Points
3DMark - 3DMark Cloud Gate Physics
100%
1 4000M +
min: 2404     avg: 2484     median: 2496 (6%)     max: 2525 Points
3DMark - 3DMark Fire Strike Standard Physics
100%
1 4000M +
min: 3405     avg: 3491     median: 3526 (9%)     max: 3576 Points
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
100%
1 4000M +
4298 Points (8%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
100%
1 4000M +
2024 Points (40%)

Average Benchmarks Intel Core i3-4000M → NAN% n=

- Range of benchmark values for this graphics card
- Average benchmark values for this graphics card
* Smaller numbers mean a higher performance
1 This benchmark is not used for the average calculation

Add one or more devices and compare

In the following list you can select (and also search for) devices that should be added to the comparison. You can select more than one device.

restrict list:

show all (including archived), 2022, 2021
v1.17
log 11. 11:29:20

#0 checking url part for id 5860 +0s ... 0s

#1 checking url part for id 4216 +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 Sat, 06 Aug 2022 13:13:32 +0200 +0.001s ... 0.001s

#4 linkCache_getLink no uid found +0.006s ... 0.006s

#5 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.008s

#6 linkCache_getLink no uid found +0.004s ... 0.012s

#7 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.012s

#8 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.012s

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

#10 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.012s

#11 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.012s

#12 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.012s

#13 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.012s

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

#15 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.012s

#16 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.012s

#17 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.012s

#18 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.012s

#19 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.012s

#20 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.012s

#21 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.012s

#22 composed specs +0s ... 0.012s

#23 did output specs +0s ... 0.013s

#24 getting avg benchmarks for device 5860 +0s ... 0.013s

#25 got single benchmarks 5860 +0s ... 0.013s

#26 getting avg benchmarks for device 4216 +0s ... 0.013s

#27 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.014s

#28 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.015s

#29 got single benchmarks 4216 +0.014s ... 0.029s

#30 got avg benchmarks for devices +0s ... 0.029s

#31 linkCache_getLink no uid found +0s ... 0.029s

#32 linkCache_getLink no uid found +0s ... 0.029s

#33 linkCache_getLink no uid found +0s ... 0.029s

#34 linkCache_getLink no uid found +0s ... 0.03s

#35 linkCache_getLink no uid found +0s ... 0.03s

#36 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.03s

#37 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.03s

#38 linkCache_getLink no uid found +0s ... 0.03s

#39 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.03s

#40 linkCache_getLink no uid found +0s ... 0.03s

#41 linkCache_getLink no uid found +0s ... 0.03s

#42 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.03s

#43 linkCache_getLink no uid found +0s ... 0.03s

#44 linkCache_getLink no uid found +0s ... 0.03s

#45 linkCache_getLink no uid found +0s ... 0.031s

#46 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#47 linkCache_getLink no uid found +0s ... 0.031s

#48 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#49 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#50 linkCache_getLink no uid found +0s ... 0.031s

#51 linkCache_getLink no uid found +0s ... 0.031s

#52 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#53 linkCache_getLink no uid found +0s ... 0.031s

#54 linkCache_getLink no uid found +0s ... 0.031s

#55 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#56 linkCache_getLink no uid found +0s ... 0.031s

#57 linkCache_getLink no uid found +0s ... 0.031s

#58 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.032s

#59 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.032s

#60 linkCache_getLink no uid found +0s ... 0.032s

#61 linkCache_getLink no uid found +0s ... 0.032s

#62 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.032s

#63 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.032s

#64 linkCache_getLink no uid found +0s ... 0.032s

#65 linkCache_getLink no uid found +0s ... 0.032s

#66 linkCache_getLink no uid found +0s ... 0.033s

#67 linkCache_getLink no uid found +0s ... 0.033s

#68 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.033s

#69 linkCache_getLink no uid found +0s ... 0.033s

#70 linkCache_getLink no uid found +0s ... 0.033s

#71 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.033s

#72 linkCache_getLink no uid found +0s ... 0.034s

#73 linkCache_getLink no uid found +0s ... 0.034s

#74 linkCache_getLink no uid found +0s ... 0.034s

#75 linkCache_getLink no uid found +0s ... 0.034s

#76 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.034s

#77 linkCache_getLink no uid found +0s ... 0.035s

#78 linkCache_getLink no uid found +0s ... 0.035s

#79 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#80 linkCache_getLink no uid found +0s ... 0.035s

#81 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#82 linkCache_getLink no uid found +0s ... 0.035s

#83 linkCache_getLink no uid found +0s ... 0.036s

#84 linkCache_getLink no uid found +0s ... 0.036s

#85 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#86 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#87 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#88 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#89 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#90 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#91 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#92 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#93 linkCache_getLink no uid found +0s ... 0.037s

#94 linkCache_getLink no uid found +0s ... 0.037s

#95 linkCache_getLink no uid found +0s ... 0.037s

#96 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#97 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#98 linkCache_getLink no uid found +0s ... 0.038s

#99 linkCache_getLink no uid found +0s ... 0.038s

#100 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#101 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

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

#103 linkCache_getLink no uid found +0s ... 0.038s

#104 linkCache_getLink no uid found +0s ... 0.038s

#105 linkCache_getLink no uid found +0s ... 0.038s

#106 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#107 linkCache_getLink no uid found +0s ... 0.038s

#108 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#109 linkCache_getLink no uid found +0s ... 0.038s

#110 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#111 linkCache_getLink no uid found +0s ... 0.038s

#112 linkCache_getLink no uid found +0s ... 0.038s

#113 linkCache_getLink no uid found +0s ... 0.039s

#114 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#115 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#116 linkCache_getLink no uid found +0s ... 0.039s

#117 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#118 linkCache_getLink no uid found +0s ... 0.039s

#119 linkCache_getLink no uid found +0s ... 0.039s

#120 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#121 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#122 min, max, avg, median took s +0s ... 0.04s

#123 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#124 return log +0.004s ... 0.044s

Please share our article, every link counts!
> Notebook / Laptop Reviews and News > Benchmarks / Tech > Processor Comparison - Head 2 Head
Redaktion, 2017-09- 8 (Update: 2017-09-11)