Notebookcheck Logo

Intel Celeron N2940 vs Intel Celeron N2910 vs Intel Celeron N2810

Intel Celeron N2940

► remove from comparison Intel N2940

The Intel Celeron N2940 is a power efficient quad-core SoC for entry-level notebooks. It is clocked at 1.83 - 2.25 GHz and part of the Bay Trail-M platform. Thanks to the specially optimized 22 nanometer low-power process (P1271) with tri-gate transistors, performance and energy efficiency have been significantly improved compared to previous Intel Atom CPUs. The N2940 supports Quick Sync as well as Wireless Display.

Architecture

The processor cores are based on the new Silvermont architecture, which is an out-of-order design for the first time. The increased utilization of the pipeline and many other improvements (optimized branch prediction, increased buffers, enhanced decoders) have increased the performance per clock by about 50 percent. At the same time, however, the Hyper-Threading feature of the previous generation has been removed. Other major changes are the support for new instruction set extensions such as SSE 4.1 and 4.2 as well as AES-NI (depending on the model).

Performance

Thanks to the improved performance per clock and the 4 cores, the Celeron N2940 is significantly faster than previous Intel Atoms, e.g. the N2800. Depending on the benchmark, the N2940 is similar to or slightly faster than the AMD Kabini APU A4-5000. For most everyday tasks such as Internet or Office the performance is adequate, but not for complex software or modern games.

Graphics

The HD Graphics (Bay Trail) is based on the Intel Gen7 architecture, which supports DirectX 11 and is also found in the Ivy Bridge series (e.g. HD Graphics 4000). With only 4 EUs (Execution Units) and a relatively low clock speed of 313 - 854 MHz, the GPU is even slower than the HD Graphics (Ivy Bridge). Therefore, only older and less demanding games will run fluently.

Power Consumption

The entire SoC is rated at a TDP of 7.5 watts (4.5 W SDP - Scenario Design Power). Thus, the chip can be used in compact (and sometimes even passively cooled) subnotebooks and tablets.

Intel Celeron N2910

► remove from comparison Intel N2910

The Intel Celeron N2910 is a power efficient quad-core SoC for entry-level notebooks. It is clocked at up to 1.6 GHz and part of the Bay Trail-M platform. Thanks to the specially optimized 22 nanometer low-power process (P1271) with tri-gate transistors, performance and energy efficiency have been significantly improved compared to previous Intel Atom CPUs.

Architecture

The processor cores are based on the new Silvermont architecture, which is an out-of-order design for the first time. The increased utilization of the pipeline and many other improvements (optimized branch prediction, increased buffers, enhanced decoders) have increased the performance per clock by about 50 percent. At the same time, however, the Hyper-Threading feature of the previous generation has been removed. Other major changes are the support for new instruction set extensions such as SSE 4.1 and 4.2 as well as AES-NI (depending on the model).

Performance

Thanks to the improved performance per clock, the Celeron N2910 is significantly faster than previous Intel Atoms, e.g. the N2800. According to our benchmarks, the N2910 competes with AMD Kabini APUs like the A6-1450. For simple everyday tasks such as Internet or Office the performance is adequate, but not for complex software or modern games.

Graphics

The graphics unit of Bay Trail is based on the Intel Gen7 architecture, which supports DirectX 11 and is also found in the Ivy Bridge series (e.g. HD Graphics 4000). With only 4 EUs (Execution Units) and a relatively low clock speed of up to 756 MHz, the GPU is even slower than the HD Graphics (Ivy Bridge). Therefore, only older and less demanding games will run fluently.

Power Consumption

The entire SoC is rated at a TDP of 7.5 watts. Thus, the chip can be used in compact subnotebooks.

Intel Celeron N2810

► remove from comparison Intel N2810

The Intel Celeron N2810 is a power efficient dual-core SoC for entry-level notebooks. It is clocked at up to 2.0 GHz and part of the Bay Trail-M platform. Thanks to the specially optimized 22 nanometer low-power process (P1271) with tri-gate transistors, performance and energy efficiency have been significantly improved compared to previous Intel Atom CPUs.

Architecture

The processor cores are based on the new Silvermont architecture, which is an out-of-order design for the first time. The increased utilization of the pipeline and many other improvements (optimized branch prediction, increased buffers, enhanced decoders) have increased the performance per clock by about 50 percent. At the same time, however, the Hyper-Threading feature of the previous generation has been removed. Other major changes are the support for new instruction set extensions such as SSE 4.1 and 4.2 as well as AES-NI (depending on the model).

Performance

Thanks to the improved performance per clock, the Celeron N2810 is faster than previous Intel Atoms, e.g. the N2800. According to out benchmarks, the N2810 even competes with AMD APUs like the AMD A4-4355M. For simple everyday tasks such as Internet or Office the performance is adequate, but not for complex software or modern games.

Graphics

The graphics unit of Bay Trail is based on the Intel Gen7 architecture, which supports DirectX 11 and is also found in the Ivy Bridge series (e.g. HD Graphics 4000). With only 4 EUs (Execution Units) and a relatively low clock speed of up to 756 MHz, the GPU is even slower than the HD Graphics (Ivy Bridge). Therefore, only older and less demanding games will run fluently.

Power Consumption

The entire SoC is rated at a TDP of 7.5 watts. Thus, the chip can be used in compact subnotebooks.

ModelIntel Celeron N2940Intel Celeron N2910Intel Celeron N2810
SeriesIntel CeleronIntel CeleronIntel Celeron
CodenameBay Trail-MBay Trail-MBay Trail-M
Series: Celeron Bay Trail-M
» Intel Celeron N29401.83 - 2.25 GHz4 / 4
Intel Celeron N29301.83 - 2.16 GHz4 / 4
Intel Celeron N29201.86 - 2 GHz4 / 4
Intel Celeron N28402.16 - 2.58 GHz2 / 2
Intel Celeron N29101.6 GHz4 / 4
Intel Celeron N28302.16 - 2.41 GHz2 / 2
Intel Celeron N28202.17 - 2.39 GHz2 / 2
Intel Celeron N28151.86 - 2.13 GHz2 / 2
Intel Celeron N28102 GHz2 / 2
Intel Celeron N28081.58 - 2.25 GHz2 / 2
Intel Celeron N28071.58 - 2.16 GHz2 / 2
Intel Celeron N28061.58 - 2 GHz2 / 2
Intel Celeron N28051.46 GHz2 / 2
Intel Celeron N29401.83 - 2.25 GHz4 / 4
Intel Celeron N29301.83 - 2.16 GHz4 / 4
Intel Celeron N29201.86 - 2 GHz4 / 4
Intel Celeron N28402.16 - 2.58 GHz2 / 2
» Intel Celeron N29101.6 GHz4 / 4
Intel Celeron N28302.16 - 2.41 GHz2 / 2
Intel Celeron N28202.17 - 2.39 GHz2 / 2
Intel Celeron N28151.86 - 2.13 GHz2 / 2
Intel Celeron N28102 GHz2 / 2
Intel Celeron N28081.58 - 2.25 GHz2 / 2
Intel Celeron N28071.58 - 2.16 GHz2 / 2
Intel Celeron N28061.58 - 2 GHz2 / 2
Intel Celeron N28051.46 GHz2 / 2
Intel Celeron N29401.83 - 2.25 GHz4 / 4
Intel Celeron N29301.83 - 2.16 GHz4 / 4
Intel Celeron N29201.86 - 2 GHz4 / 4
Intel Celeron N28402.16 - 2.58 GHz2 / 2
Intel Celeron N29101.6 GHz4 / 4
Intel Celeron N28302.16 - 2.41 GHz2 / 2
Intel Celeron N28202.17 - 2.39 GHz2 / 2
Intel Celeron N28151.86 - 2.13 GHz2 / 2
» Intel Celeron N28102 GHz2 / 2
Intel Celeron N28081.58 - 2.25 GHz2 / 2
Intel Celeron N28071.58 - 2.16 GHz2 / 2
Intel Celeron N28061.58 - 2 GHz2 / 2
Intel Celeron N28051.46 GHz2 / 2
Clock1830 - 2250 MHz1600 MHz2000 MHz
L1 Cache224 KB224 KB112 KB
L2 Cache2 MB2 MB1 MB
Cores / Threads4 / 44 / 42 / 2
TDP7.5 Watt7.5 Watt7.5 Watt
Technology22 nm22 nm22 nm
max. Temp.105 °C100 °C
SocketFCBGA1170
FeaturesHD Graphics (Bay Trail, 313 - 854 MHz), Quick Sync, Wireless Display, SpeedstepHD Graphics (Bay Trail, max. 756 MHz)
iGPUIntel HD Graphics (Bay Trail) (313 - 854 MHz)Intel HD Graphics (Bay Trail) (313 - 756 MHz)Intel HD Graphics (Bay Trail) (313 - 756 MHz)
Architecturex86x86x86
Announced
ManufacturerIntel Celeron N2940Intel Celeron N2910Intel Celeron N2810

Benchmarks

Cinebench R15 - Cinebench R15 CPU Multi 64 Bit
min: 89     avg: 110.5     median: 110.5 (1%)     max: 132 Points
97 Points (1%)
59 Points (1%)
Cinebench R15 - Cinebench R15 CPU Single 64 Bit
min: 35     avg: 35.5     median: 35.5 (12%)     max: 36 Points
27 Points (9%)
31 Points (11%)
Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
min: 1.57     avg: 1.6     median: 1.6 (3%)     max: 1.62 Points
1.1 Points (2%)
0.7 Points (1%)
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
0.4 Points (1%)
0.3 Points (1%)
0.4 Points (1%)
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
1150 Points (10%)
844 Points (8%)
993 Points (9%)
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
3958 Points (5%)
2907 Points (4%)
1474 Points (2%)
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
5784 Points (5%)
4302 Points (4%)
2672 Points (2%)
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
1663 Points (10%)
1206 Points (7%)
1318 Points (8%)
wPrime 2.10 - wPrime 2.0 1024m *
100%
1 N2940 +
867 s (10%)
86%
1 N2810 +
1941 s (23%)
wPrime 2.10 - wPrime 2.0 32m *
100%
1 N2940 +
29.2 s (6%)
93%
1 N2810 +
63.4 s (13%)
WinRAR - WinRAR 4.0
100%
1 N2810 +
680 Points (4%)
X264 HD Benchmark 4.0 - x264 Pass 2
100%
1 N2940 +
9.4 fps (4%)
46%
1 N2810 +
4.3 fps (2%)
X264 HD Benchmark 4.0 - x264 Pass 1
100%
1 N2940 +
46.9 fps (13%)
49%
1 N2810 +
22.8 fps (6%)
TrueCrypt - TrueCrypt Serpent
100%
1 N2940 +
0.1 GB/s (4%)
46%
1 N2810 +
0.1 GB/s (2%)
TrueCrypt - TrueCrypt Twofish
100%
1 N2940 +
0.2 GB/s (4%)
47%
1 N2810 +
0.1 GB/s (2%)
TrueCrypt - TrueCrypt AES
100%
1 N2940 +
0.2 GB/s (1%)
45%
1 N2810 +
0.1 GB/s (0%)
3DMark 06 - CPU - 3DMark 06 - CPU
2191 Points (5%)
1612 Points (3%)
1043 Points (2%)
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
27.5 s (6%)
27 s (6%)
43 s (9%)
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
61.2 s (3%)
61 s (3%)
93.9 s (4%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
1566 s (7%)
1566 s (7%)
1999 s (9%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
100%
1 N2810 +
2038 Points (2%)
3DMark 11 - 3DM11 Performance Physics
100%
1 N2940 +
1635 Points (6%)
52%
1 N2810 +
858 Points (3%)
3DMark - 3DMark Ice Storm Physics
17767 Points (11%)
13106 Points (8%)
9157 Points (6%)
3DMark - 3DMark Cloud Gate Physics
1257 Points (3%)
1107 Points (3%)
710 Points (2%)
3DMark - 3DMark Fire Strike Standard Physics
100%
1 N2910 +
1566 Points (4%)
62%
1 N2810 +
969 Points (2%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
100%
1 N2810 +
1328 Points (2%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
100%
1 N2810 +
762 Points (15%)
Geekbench 2 - 32 Bit - Geekbench Stream
100%
1 N2910 +
2001 Points (16%)
110%
1 N2810 +
2192 Points (18%)
Geekbench 2 - 32 Bit - Geekbench Memory
100%
1 N2910 +
1743 Points (16%)
116%
1 N2810 +
2027 Points (18%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
100%
1 N2910 +
2189 Points (4%)
78%
1 N2810 +
1715 Points (3%)
Geekbench 2 - 32 Bit - Geekbench Integer
100%
1 N2910 +
2544 Points (5%)
76%
1 N2810 +
1924 Points (4%)
Geekbench 2 - 32 Bit - Geekbench Total Score
100%
1 N2910 +
2205 Points (6%)
86%
1 N2810 +
1898 Points (5%)

Average Benchmarks Intel Celeron N2940 → 100% n=14

Average Benchmarks Intel Celeron N2910 → 81% n=14

Average Benchmarks Intel Celeron N2810 → 69% n=14

- 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

v1.17
log 16. 15:37:17

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

#1 checking url part for id 4576 +0s ... 0s

#2 checking url part for id 4577 +0s ... 0s

#3 not redirecting to Ajax server +0s ... 0s

#4 did not recreate cache, as it is less than 5 days old! Created at Tue, 16 Aug 2022 13:13:41 +0200 +0s ... 0s

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

#6 linkCache_getLink no uid found +0.005s ... 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 no uid found +0.003s ... 0.015s

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

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

#22 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.015s

#23 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.015s

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

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

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

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

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

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

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

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

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

#33 composed specs +0s ... 0.015s

#34 did output specs +0s ... 0.015s

#35 getting avg benchmarks for device 6009 +0s ... 0.016s

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

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

#38 got single benchmarks 6009 +0.01s ... 0.027s

#39 getting avg benchmarks for device 4576 +0s ... 0.027s

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

#41 got single benchmarks 4576 +0.007s ... 0.034s

#42 getting avg benchmarks for device 4577 +0.001s ... 0.035s

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

#44 got single benchmarks 4577 +0.009s ... 0.044s

#45 got avg benchmarks for devices +0s ... 0.044s

#46 linkCache_getLink no uid found +0s ... 0.044s

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

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

#49 linkCache_getLink no uid found +0.001s ... 0.046s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#88 linkCache_getLink no uid found +0s ... 0.059s

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

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

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

#92 linkCache_getLink no uid found +0s ... 0.061s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#111 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.068s

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

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

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

#115 linkCache_getLink no uid found +0s ... 0.069s

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

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

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

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

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

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

#122 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.072s

#123 min, max, avg, median took s +0s ... 0.072s

#124 return log +0s ... 0.072s

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