, , , , , ,
zu verknüpfen.
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
 

Intel Core i3-2330M vs Intel Core i3-2357M

Intel Core i3-2330M

► remove from comparison Intel 2330M

Der Intel Core i3-2330M ist ein Mittelklasse Doppelkernprozessor für Notebooks welcher im Mai 2011 vorgestellt wurde. Er bietet zwei Kerne und kann dank Hyperthreading 4 Threads gleichzeitig bearbeiten. Im Vergleich zu den i5 und i7 Doppelkernprozessoren, bietet der i3-2330M keinen Turbo Boost zum automatischen übertakten des Prozessors (jedoch für die integrierte Grafikkarte). Auch VT-d, Trusted Execution und AES sind deaktiviert (wie beim i5-2410M).

Sandy Bridge ist eine Weiterentwicklung der Arrandale Architektur. Neben Optimierungen sind besonders die neuen 256 Bit AVX Instruktionen im CPU Teil und der verbesserte Turbo 2.0 erwähnenswert. Dieser kommt beim i3-2310M jedoch nur für die Grafikkarte zum Einsatz. Weiters  ist ein verbesserter Dual Channel DDR3 Speicherkontroller für max. 8 GB DDR-1333MHz direkt im Prozessor integriert.

Die intergrierte DirectX 10 fähige Intel HD Graphics 3000 Grafikkarte ist direkt in der CPU untergebracht und teilt sich mit dieser den Level 3 / Last Level Cache. Dadurch sinkt zwar die Prozessorleistung etwas bei aktivierter Grafik, die Grafikleistung ist jedoch deutlich besser als bei der alten Intel HD Graphics und auf Niveau einer Nvidia Geforce 310M Einstiegsgrafikkarte.  Dank Turbo Boost wird sie wahrscheinlich wie beim 2310M von 650MHz bis 1100MHz getaktet.

Die Performance liegt dank der verbesserten Architektur etwas oberhalb einer ähnlich getakteten Arrandale CPU. Im Schnitt liegt der Core i3 deshalb wahrscheinlich auf dem Level eines 2.53 GHz Core i3-380M. Für die meisten Anwendungen sollte die Performance dadurch ausreichen.

Die Sandy Bridge Doppelkernprozessoren beinhalten im angegebenen TDP von 35 Watt auch die Grafikkarte und den Speicherkontroller. Mit 35W TDP eignet sich der Prozessor am besten für 14" Notebooks und größer.

Intel Core i3-2357M

► remove from comparison Intel 2357M

Der Intel Core i3-2357M ist ein stromsparender ULV (Ultra Low Voltage) Prozessor für Subnotebooks. Mit 1.3 GHz Taktfrequenz ist er relativ gering getaktet und bietet keine automatische Übertaktung mit Turbo Boost 2.0. Durch die Unterstützung von Hyperthreading können 4 Threads gleichzeitig bearbeitet werden.

Sandy Bridge ist eine Weiterentwicklung der Arrandale Architektur. Neben Optimierungen sind besonders die neuen 256 Bit AVX Instruktionen im CPU Teil und der verbesserte Turbo 2.0 erwähnenswert (der jedoch im CPU Teil des i3-2357M nicht zum Einsatz kommt). Weiters ist ein verbesserter Dual Channel DDR3 Speicherkontroller für max. 8 GB DDR3-1333MHz direkt im Prozessor integriert.

Die intergrierte DirectX 10 fähige Intel HD Graphics 3000 Grafikkarte ist direkt in der CPU untergebracht und teilt sich mit dieser den Level 3 / Last Level Cache. Dadurch sinkt zwar die Prozessorleistung etwas bei aktivierter Grafik, die Grafikleistung ist jedoch deutlich besser als bei der alten Intel HD Graphics in ULV Notebooks. Vergleichen mit den stärkeren 35 Watt Doppelkernprozessoren ist die Grafikleistung jedoch aufgrund der geringeren Taktfrequenz deutlich schlechter (350 versus 650 MHz Basistakt, 950 versus 1100-1300 MHz Turbo Boost).

Die Performance liegt dank der verbesserten Architektur und des überarbeiteten Turbo Boost etwas oberhalb einer ähnlich getakteten Arrandale CPU (Core i3-380UM). In unseren Benchmarks reihte sich die CPU je nach Benchmark auf dem Level eines 1.6 - 2 GHz Penryn Pentium (T3000-T3400) bzw eines AMD A6-3410MX.

Die Sandy Bridge Doppelkernprozessoren beinhalten im angegebenen TDP von 17 Watt auch die Grafikkarte und den Speicherkontroller und eignen sich damit auch für kleine und leichte Notebooks.

ModelIntel Core i3-2330MIntel Core i3-2357M
SeriesIntel Core i3Intel Core i3
CodenameSandy BridgeSandy Bridge
Serie: Core i3 Sandy Bridge
Intel Core i3-2370M compare2.4 GHz2 / 43 MB
Intel Core i3-2350M compare2.3 GHz2 / 43 MB
Intel Core i3-2348M compare2.3 GHz2 / 43 MB
» Intel Core i3-2330M2.2 GHz2 / 43 MB
Intel Core i3-2328M compare2.2 GHz2 / 43 MB
Intel Core i3-2312M compare2.1 GHz2 / 43 MB
Intel Core i3-2310M compare2.1 GHz2 / 43 MB
Intel Core i3-2308M compare2.1 GHz2 / 43 MB
Intel Core i3-2377M compare1.5 GHz2 / 43 MB
Intel Core i3-2375M compare1.5 GHz2 / 43 MB
Intel Core i3-2367M compare1.4 GHz2 / 43 MB
Intel Core i3-2365M compare1.4 GHz2 / 43 MB
Intel Core i3-2357M1.3 GHz2 / 43 MB
Intel Core i3-2370M compare2.4 GHz2 / 43 MB
Intel Core i3-2350M compare2.3 GHz2 / 43 MB
Intel Core i3-2348M compare2.3 GHz2 / 43 MB
Intel Core i3-2330M2.2 GHz2 / 43 MB
Intel Core i3-2328M compare2.2 GHz2 / 43 MB
Intel Core i3-2312M compare2.1 GHz2 / 43 MB
Intel Core i3-2310M compare2.1 GHz2 / 43 MB
Intel Core i3-2308M compare2.1 GHz2 / 43 MB
Intel Core i3-2377M compare1.5 GHz2 / 43 MB
Intel Core i3-2375M compare1.5 GHz2 / 43 MB
Intel Core i3-2367M compare1.4 GHz2 / 43 MB
Intel Core i3-2365M compare1.4 GHz2 / 43 MB
» Intel Core i3-2357M1.3 GHz2 / 43 MB
Clock2200 MHz1300 MHz
L1 Cache128 KB128 KB
L2 Cache512 KB512 KB
L3 Cache3 MB3 MB
Cores / Threads2 / 42 / 4
TDP35 Watt17 Watt
Transistors624 Million624 Million
Technology32 nm32 nm
Die Size149 mm2149 mm2
max. Temp.85 (PGA); 100(BGA) °C100 °C
SocketrPGA988B / BGA1023BGA1023
FeaturesHD Graphics 3000 (650-1100MHz), DDR3-1066/1333 Memory Controller (max 8GB), HyperThreading, AVX, Quick Sync, VirtualizationHD Graphics 3000 (350-950MHz), DDR3-1066/1333 Memory Controller (max 8GB), HyperThreading, AVX, Quick Sync, Virtualization
iGPUIntel HD Graphics 3000 (650 - 1100 MHz)Intel HD Graphics 3000 (350 - 950 MHz)
Architecturex86x86
Announced
ManufacturerIntel Core i3 2330MIntel Core i3 2357M

Benchmarks

Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
min: 2.07     avg: 2.1     median: 2.1 (4%)     max: 2.14 Points
min: 1.15     avg: 1.2     median: 1.2 (2%)     max: 1.26 Points
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
min: 2869     avg: 2888     median: 2888 (26%)     max: 2904 Points
min: 1632     avg: 1667     median: 1645 (15%)     max: 1724 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
min: 6263     avg: 6457     median: 6465.5 (9%)     max: 6593 Points
min: 3615     avg: 3759     median: 3808 (5%)     max: 3854 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
min: 7745     avg: 7876     median: 7887 (7%)     max: 7944 Points
min: 4212     avg: 4531     median: 4661 (4%)     max: 4721 Points
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
min: 3591     avg: 3624     median: 3623.5 (22%)     max: 3654 Points
min: 2003     avg: 2079     median: 2081 (13%)     max: 2154 Points
wPrime 2.10 - wPrime 2.0 1024m *
min: 722     avg: 781     median: 789.4 (9%)     max: 826.241 s
min: 1323.44     avg: 1403     median: 1422.1 (17%)     max: 1462 s
wPrime 2.10 - wPrime 2.0 32m *
min: 22     avg: 24.7     median: 25.1 (5%)     max: 26.379 s
min: 42     avg: 43.3     median: 42.3 (9%)     max: 45.592 s
TrueCrypt - TrueCrypt Serpent
100%
1 2330M +
0.1 GB/s (3%)
TrueCrypt - TrueCrypt Twofish
100%
1 2330M +
0.2 GB/s (4%)
TrueCrypt - TrueCrypt AES
100%
1 2330M +
0.2 GB/s (1%)
3DMark 06 - CPU - 3DMark 06 - CPU
min: 2610     avg: 2629     median: 2627 (6%)     max: 2649 Points
min: 1554     avg: 1572     median: 1575 (3%)     max: 1586 Points
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
min: 17     avg: 17.6     median: 17.7 (4%)     max: 18 s
min: 29     avg: 29.5     median: 29.6 (6%)     max: 30 s
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
min: 40     avg: 40.3     median: 40 (2%)     max: 41 s
min: 66     avg: 66.2     median: 66 (3%)     max: 66.612 s
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
min: 926     avg: 936     median: 941 (4%)     max: 944 s
min: 1503.83     avg: 1510     median: 1512 (7%)     max: 1514 s
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
min: 33000     avg: 35000     median: 35000 (17%)     max: 37000 MIPS
22000 MIPS (10%)
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
min: 22170     avg: 24085     median: 24085 (18%)     max: 26000 MFLOPS
15290 MFLOPS (12%)
Windows 7 Experience Index - Win7 CPU
6.5 Points (83%)
4.9 Points (63%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
min: 6879     avg: 7014     median: 7008 (7%)     max: 7165 Points
4103 Points (4%)
3DMark 11 - 3DM11 Performance Physics
100%
1 2330M +
min: 2782     avg: 2786     median: 2786 (10%)     max: 2790 Points

Average Benchmarks Intel Core i3-2330M → 100% n=15

Average Benchmarks Intel Core i3-2357M → 73% n=15

- Bereich der Benchmarkergebnisse für diese Grafikkarte
- Durchschnittliche Benchmarkergebnisse für diese Grafikkarte
* 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 23. 06:35:07

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

#1 checking url part for id 2742 +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 Tue, 18 Jan 2022 12:10:47 +0100 +0.001s ... 0.001s

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

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

#6 linkCache_getLink no uid found +0.002s ... 0.01s

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

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

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

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

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

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

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

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

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

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

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

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

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

#20 composed specs +0s ... 0.01s

#21 did output specs +0s ... 0.01s

#22 getting avg benchmarks for device 2364 +0s ... 0.011s

#23 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.011s

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

#25 got single benchmarks 2364 +0.023s ... 0.034s

#26 getting avg benchmarks for device 2742 +0s ... 0.035s

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

#28 got single benchmarks 2742 +0.007s ... 0.042s

#29 got avg benchmarks for devices +0s ... 0.042s

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

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

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

#33 linkCache_getLink no uid found +0.001s ... 0.043s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#161 min, max, avg, median took s +0s ... 0.056s

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

#163 return log +0.004s ... 0.06s

Teilen Sie diesen Artikel um uns zu unterstützen. Jeder Link hilft!
> Notebook Test, Laptop Test und News > Benchmarks / Technik > Benchmarks / Technik > Prozessor Vergleich - Head 2 Head
Autor: Redaktion,  8.09.2017 (Update: 19.05.2020)