Notebookcheck Logo

Intel Core i3-380UM vs Intel Core i3-380M

Intel Core i3-380UM

► remove from comparison

The Intel Core i3-380UM is a Ultra Low Voltage dual-core processor for small and light laptops. It is clocked with 1.3 GHz and does not feature Turbo Boost to overclock the CPU cores. Another feature missing compared to the i5 and i7 lineup is the AES function block. Each core is based on the Nehalem (Westmere) micro-architecture. Hyperthreading enables the Dual Core CPU to handle 4 threads at once (for a better usage of the pipeline). 

The similar Core i5-470UM, i5-560UM, and i7-660UM are also clocked at a base speed of 1.3 GHz, but feature Turbo Boost and are therefore faster.

A feature of the new Core i3-380UM is the integrated graphics card (called Intel HD Graphics) and memory controller. Both are on a separate die that is still manufactured in 45nm whereas the CPU die is already manufactured in the new 32nm process. The also called GMA HD is able to use Turbo Boost to overclock from 133 to 500 MHz.

Due to the integrated memory controller and HyperThreading, the  Core i3-380UM is faster than a similar clocked Core 2 Duo (1.3 GHz) in all (us known) applications and benchmarks. Therefore it beats the 1.3 GHz Pentium SU7300 and performs in some areas even as fast as a 2 GHz Core 2 Duo. Still the gaming performance can suffer from the low clock speed.

The power consumption of 18 Watt TDP (max.) counts for the whole package and therefore it is clearly better than the 17 Watt TDP of the Core 2 Duo SL-series (CPU alone).

Intel Core i3-380M

► remove from comparison Intel 380M

The Intel Core i3-380M is a middle class dual core CPU for laptops and clocks with 2.53 GHz. The difference to the Core i5 and i7 series is the lacking TurboBoost overclocking, and the missing AES, VT-d and Trusted Execution functions. Each core is based on the Nehalem (Westmere) micro-architecture. Hyperthreading enables the Dual Core CPU to handle 4 threads at once (for a better usage of the pipeline). It is part of the Arrandale refresh and successor to the 2.4 GHz i3-370M.

A feature of the new Core i3-380M is the integrated graphics card called GMA HD and the memory controller. Both are on a separate die that is still manufactured in 45nm whereas the CPU die is already manufactured in the new 32nm process.

The performance of the Core i3-380M should be at a level of a 2.6-2.7 GHz Core 2 Duo (upper class CPUs in the last year). This is mainly due to the efficient HyperThreading function and the integrated memory controller. In single threaded applications it should be at least as fast, as a similar clocked Core 2 Duo.

The integrated Intel Graphics Media Accelerator HD (GMA HD) graphics card is known to be clocked up to 500-667 MHz (due to Turbo Boost) and should be clearly faster than the old GMA 4500MHD. The Core i5 and i7 models should still be a bit faster because of the higher max. clock speed of the GPU. The performance of the graphics in 3D should be on par with a Radeon HD 4200 but the driver support is usually worse.

The power consumption of 35 Watt TDP (max.) counts for the whole package and therefore it is clearly better than the 35 Watt TDP of the Core 2 Duo T-series (CPU alone).

ModelIntel Core i3-380UMIntel Core i3-380M
SeriesIntel Core i3Intel Core i3
CodenameArrandaleArrandale
Series: Core i3 Arrandale
Intel Core i3-390M compare2.67 GHz2 / 43 MB
Intel Core i3-380M2.53 GHz2 / 43 MB
Intel Core i3-370M compare2.4 GHz2 / 43 MB
Intel Core i3-350M compare2.26 GHz2 / 43 MB
Intel Core i3-330M compare2.13 GHz2 / 43 MB
» Intel Core i3-380UM1.33 GHz2 / 43 MB
Intel Core i3-330UM compare1.2 GHz2 / 43 MB
Intel Core i3-390M compare2.67 GHz2 / 43 MB
» Intel Core i3-380M2.53 GHz2 / 43 MB
Intel Core i3-370M compare2.4 GHz2 / 43 MB
Intel Core i3-350M compare2.26 GHz2 / 43 MB
Intel Core i3-330M compare2.13 GHz2 / 43 MB
Intel Core i3-380UM1.33 GHz2 / 43 MB
Intel Core i3-330UM compare1.2 GHz2 / 43 MB
Clock1333 MHz2533 MHz
FSB25002500
L2 Cache512 KB512 KB
L3 Cache3 MB3 MB
Cores / Threads2 / 42 / 4
TDP18 Watt35 Watt
Transistors382+177 Million382+177 Million
Technology32 nm32 nm
Die Size81+114 mm281+114 mm2
SocketBGA1288BGA1288, PGA988
FeaturesIntel HD Graphics 166-500MHz, DDR3-800 Memory Controller (max 8GB), Hyper-Threading, Virtualization Technology VT-x, Intel 64, Idle States, Enhanced Speedstep, Thermal Monitoring, Fast Memory Access, Flex Memory Access, Execute Disable BitHyper Threading, Enhanced Speedstep, integrierte GMA HD 500-667MHz,
Architecturex86x86
Announced
ManufacturerIntel Core i3 380UMIntel Core i3 380M
max. Temp.105 °C

Benchmarks

Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
min: 0.99     avg: 1.1     median: 1.1 (2%)     max: 1.11 Points
187%
380M +
min: 2.07     avg: 2.1     median: 2.1 (4%)     max: 2.2 Points
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
min: 1268     avg: 1451     median: 1502 (13%)     max: 1530 Points
187%
380M +
min: 2719     avg: 2788     median: 2808 (25%)     max: 2830 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
min: 3052     avg: 3385     median: 3471 (5%)     max: 3546 Points
189%
380M +
min: 6512     avg: 6558     median: 6554 (9%)     max: 6602 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
min: 3729     avg: 4054     median: 4166 (4%)     max: 4266 Points
187%
380M +
min: 7602     avg: 7797     median: 7810.5 (7%)     max: 7966 Points
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
min: 1499     avg: 1733     median: 1845 (11%)     max: 1856 Points
187%
380M +
min: 3349     avg: 3434     median: 3457.5 (21%)     max: 3472 Points
wPrime 2.10 - wPrime 2.0 1024m *
min: 1178     avg: 1687     median: 1264.5 (15%)     max: 3039 s
109%
380M +
min: 620     avg: 621     median: 621 (7%)     max: 623 s
wPrime 2.10 - wPrime 2.0 32m *
min: 38.2     avg: 53.6     median: 40.5 (8%)     max: 95 s
104%
380M +
min: 19.7     avg: 20.1     median: 20 (4%)     max: 20.5 s
3DMark 06 - CPU - 3DMark 06 - CPU
min: 1314     avg: 1426     median: 1463 (3%)     max: 1464 Points
184%
380M +
min: 2671     avg: 2697     median: 2699 (6%)     max: 2731 Points
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
min: 31.92     avg: 32     median: 32 (7%)     max: 32 s
103%
380M +
min: 14     avg: 16.5     median: 17.3 (4%)     max: 17.5 s
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
min: 72     avg: 72.9     median: 72.9 (3%)     max: 73.6 s
101%
380M +
min: 41     avg: 42.2     median: 41.8 (2%)     max: 44.3 s
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
min: 1676     avg: 1719     median: 1695 (8%)     max: 1786 s
104%
380M +
min: 947     avg: 954     median: 951 (4%)     max: 964 s
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
min: 16560     avg: 18035     median: 18035 (9%)     max: 19510 MIPS
172%
380M +
31000 MIPS (15%)
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
min: 13800     avg: 14325     median: 14325 (11%)     max: 14850 MFLOPS
183%
380M +
min: 26160     avg: 26285     median: 26285 (20%)     max: 26410 MFLOPS
Windows 7 Experience Index - Win7 CPU
min: 4.5     avg: 4.7     median: 4.8 (62%)     max: 4.8 Points
142%
380M +
6.8 Points (87%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
3833 Points (4%)
189%
380M +
min: 7240     avg: 7262     median: 7246 (7%)     max: 7300 Points
3DMark 11 - 3DM11 Performance Physics
100%
1 380M +
min: 2073     avg: 2338     median: 2391.5 (8%)     max: 2497 Points

Average Benchmarks Intel Core i3-380UM → 100% n=15

Average Benchmarks Intel Core i3-380M → 155% n=15

- 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 30. 16:33:11

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

#1 checking url part for id 1264 +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 Mon, 27 Jun 2022 13:12:58 +0200 +0s ... 0s

#4 linkCache_getLink no uid found +0.004s ... 0.005s

#5 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.006s

#6 linkCache_getLink no uid found +0.003s ... 0.009s

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

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

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

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

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

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

#13 composed specs +0s ... 0.009s

#14 did output specs +0s ... 0.009s

#15 getting avg benchmarks for device 1232 +0s ... 0.009s

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

#17 got single benchmarks 1232 +0.011s ... 0.021s

#18 getting avg benchmarks for device 1264 +0s ... 0.021s

#19 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.022s

#20 got single benchmarks 1264 +0.025s ... 0.047s

#21 got avg benchmarks for devices +0s ... 0.047s

#22 linkCache_getLink no uid found +0s ... 0.047s

#23 linkCache_getLink no uid found +0.001s ... 0.048s

#24 linkCache_getLink no uid found +0s ... 0.048s

#25 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#26 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#27 linkCache_getLink no uid found +0s ... 0.048s

#28 linkCache_getLink no uid found +0s ... 0.048s

#29 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#30 linkCache_getLink no uid found +0s ... 0.048s

#31 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

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

#33 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.049s

#34 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.049s

#35 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.049s

#36 linkCache_getLink no uid found +0s ... 0.049s

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

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

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

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

#41 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.049s

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

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

#44 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.049s

#45 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

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

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

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

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

#50 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

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

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

#53 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

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

#55 linkCache_getLink no uid found +0s ... 0.05s

#56 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

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

#58 linkCache_getLink no uid found +0s ... 0.05s

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

#60 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

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

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

#63 linkCache_getLink no uid found +0s ... 0.051s

#64 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.051s

#65 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.051s

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

#67 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.051s

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

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

#70 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.051s

#71 linkCache_getLink no uid found +0s ... 0.051s

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

#73 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.052s

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

#75 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.052s

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

#77 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.052s

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

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

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

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

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

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

#84 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

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

#86 linkCache_getLink no uid found +0s ... 0.053s

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

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

#89 linkCache_getLink no uid found +0s ... 0.053s

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

#91 linkCache_getLink no uid found +0s ... 0.053s

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

#93 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#94 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#95 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#96 linkCache_getLink no uid found +0s ... 0.053s

#97 linkCache_getLink no uid found +0s ... 0.053s

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

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

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

#101 linkCache_getLink no uid found +0s ... 0.054s

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

#103 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.054s

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

#105 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.054s

#106 linkCache_getLink no uid found +0s ... 0.054s

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

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

#109 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.054s

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

#111 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.055s

#112 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.055s

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

#114 linkCache_getLink no uid found +0s ... 0.055s

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

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

#117 linkCache_getLink no uid found +0s ... 0.055s

#118 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

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

#120 linkCache_getLink no uid found +0s ... 0.056s

#121 linkCache_getLink no uid found +0s ... 0.056s

#122 linkCache_getLink no uid found +0s ... 0.056s

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

#124 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#125 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#126 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

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

#128 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#129 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

#130 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

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

#132 linkCache_getLink no uid found +0s ... 0.057s

#133 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

#134 linkCache_getLink no uid found +0s ... 0.057s

#135 linkCache_getLink no uid found +0s ... 0.057s

#136 linkCache_getLink no uid found +0s ... 0.057s

#137 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

#138 min, max, avg, median took s +0s ... 0.058s

#139 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#140 return log +0.004s ... 0.062s

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)