Notebookcheck Logo

Intel Core i3-380UM vs Intel Core i3-330UM

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-330UM

► remove from comparison

The Intel Core i3-330UM is a Ultra Low Voltage dual-core processor for small and light laptops. It is clocked with 1.2 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). 

A feature of the new Core i3-330UM 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-330UM is faster than a similar clocked Core 2 Duo (1.2 GHz) in all (us known) applications and benchmarks. Therefore it should beat the 1.3 GHz Pentium SU7300. Still the gaming performance will 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).

 

ModelIntel Core i3-380UMIntel Core i3-330UM
SeriesIntel Core i3Intel Core i3
CodenameArrandaleArrandale
Series: Core i3 Arrandale
Intel Core i3-390M compare2.67 GHz2 / 43 MB
Intel Core i3-380M compare2.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-330UM1.2 GHz2 / 43 MB
Intel Core i3-390M compare2.67 GHz2 / 43 MB
Intel Core i3-380M compare2.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-330UM1.2 GHz2 / 43 MB
Clock1333 MHz1200 MHz
FSB25002500
L2 Cache512 KB512 KB
L3 Cache3 MB3 MB
Cores / Threads2 / 42 / 4
TDP18 Watt18 Watt
Transistors382+177 Million382+177 Million
Technology32 nm32 nm
Die Size81+114 mm281+114 mm2
SocketBGA1288BGA1288
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 BitIntel HD Graphics 166-500MHz, DDR3-800 Memory Controller, Hyper-Threading, Virtualization Technology VT-x, Intel 64, Idle States, Enhanced Speedstep, Thermal Monitoring, Fast Memory Access, Flex Memory Access, Execute Disable Bit
Architecturex86x86
Announced
ManufacturerIntel Core i3 380UMIntel Core i3 330UM
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
1 Points (2%)
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
min: 1268     avg: 1451     median: 1502 (13%)     max: 1530 Points
min: 1293     avg: 1297     median: 1297 (12%)     max: 1301 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
min: 3052     avg: 3385     median: 3471 (5%)     max: 3546 Points
min: 2847     avg: 2982     median: 2982 (4%)     max: 3117 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
min: 3729     avg: 4054     median: 4166 (4%)     max: 4266 Points
min: 3779     avg: 3796     median: 3796 (3%)     max: 3813 Points
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
min: 1499     avg: 1733     median: 1845 (11%)     max: 1856 Points
min: 1629     avg: 1665     median: 1664.5 (10%)     max: 1700 Points
wPrime 2.10 - wPrime 2.0 1024m *
min: 1178     avg: 1687     median: 1264.5 (15%)     max: 3039 s
min: 1310     avg: 1325     median: 1323 (16%)     max: 1341 s
wPrime 2.10 - wPrime 2.0 32m *
min: 38.2     avg: 53.6     median: 40.5 (8%)     max: 95 s
min: 42     avg: 42.6     median: 42.7 (9%)     max: 43.13 s
3DMark 06 - CPU - 3DMark 06 - CPU
min: 1314     avg: 1426     median: 1463 (3%)     max: 1464 Points
min: 1299     avg: 1310     median: 1301 (3%)     max: 1331 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
min: 35     avg: 36.1     median: 36.1 (8%)     max: 37.3 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
min: 79     avg: 81.7     median: 82.7 (4%)     max: 83.5 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
min: 1843     avg: 1876     median: 1876 (8%)     max: 1909 s
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
min: 16560     avg: 18035     median: 18035 (9%)     max: 19510 MIPS
min: 14690     avg: 16150     median: 16150 (8%)     max: 17610 MIPS
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
min: 13800     avg: 14325     median: 14325 (11%)     max: 14850 MFLOPS
min: 12400     avg: 12510     median: 12510 (10%)     max: 12620 MFLOPS
Windows 7 Experience Index - Win7 CPU
min: 4.5     avg: 4.7     median: 4.8 (62%)     max: 4.8 Points
min: 4.1     avg: 4.2     median: 4.2 (53%)     max: 4.2 Points
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
3833 Points (4%)

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

Average Benchmarks Intel Core i3-330UM → 92% 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 26. 00:22:46

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

#1 checking url part for id 997 +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 Wed, 22 Jun 2022 13:12:54 +0200 +0s ... 0s

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

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

#6 linkCache_getLink no uid found +0.001s ... 0.008s

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

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

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

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

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

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

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

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

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

#16 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.009s

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

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

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

#20 got single benchmarks 997 +0.011s ... 0.033s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#76 linkCache_getLink no uid found +0s ... 0.04s

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

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

#79 linkCache_getLink no uid found +0s ... 0.04s

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

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

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

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

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

#85 linkCache_getLink no uid found +0.001s ... 0.042s

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

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

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

#89 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.043s

#90 linkCache_getLink no uid found +0s ... 0.043s

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

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

#93 linkCache_getLink no uid found +0.001s ... 0.044s

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

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

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

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

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

#99 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#100 min, max, avg, median took s +0s ... 0.045s

#101 linkCache_getLink using $NBC_LINKCACHE +0.027s ... 0.072s

#102 return log +0.004s ... 0.076s

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)