Notebookcheck Logo
, , , , , ,
zu verknüpfen.
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
 

Intel Core i3-2330M vs Intel Core i3-2328M vs Intel Core i3-2348M

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-2328M

► remove from comparison Intel 2328M

Der Intel Core i3-2328M ist ein Mittelklasse Doppelkernprozessor für Notebooks welcher im September 2012 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-2328M 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). Der Core i3-2328M entspricht weitgehenst dem Core i3-2330M, bietet jedoch laut CPU World keine Unterstützung für Intel's Small Business Advantage Tools (USB Blocker, PC Health Check, Data Backup und Wireless Display).

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 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 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-2348M

► remove from comparison Intel 2348M

Der Intel Core i3-2348M ist ein Mittelklasse Doppelkernprozessor für Notebooks, welcher im 1. Quartal 2013 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-2348M 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). Der Core i3-2348M entspricht weitgehenst dem Core i3-2350M, bietet jedoch laut CPU World keine Unterstützung für Intel's Small Business Advantage Tools (USB Blocker, PC Health Check, Data Backup und Wireless Display).

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-2348M jedoch nur für die Grafikkarte zum Einsatz. 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 und auf Niveau einer Nvidia Geforce 310M Einstiegsgrafikkarte.  Dank Turbo Boost wird sie wie beim 2350M von 650MHz bis 1150MHz getaktet.

Die Performance liegt dank der verbesserten Architektur etwas oberhalb einer ähnlich getakteten Arrandale CPU. Im Schnitt liegt der Core i3 deshalb auf oder knapp über 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.

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

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: 2.01     avg: 2.1     median: 2.1 (4%)     max: 2.14 Points
2.2 Points (4%)
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
100%
1 2328M +
min: 0.84     avg: 0.9     median: 0.9 (25%)     max: 0.88 Points
102%
1 2348M +
0.9 Points (26%)
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
100%
1 2330M +
min: 2869     avg: 2888     median: 2888 (26%)     max: 2904 Points
100%
1 2328M +
min: 2764     avg: 2864     median: 2880 (26%)     max: 2912 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
100%
1 2330M +
min: 6263     avg: 6457     median: 6465.5 (9%)     max: 6593 Points
100%
1 2328M +
min: 6098     avg: 6433     median: 6475 (9%)     max: 6551 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
min: 7745     avg: 7876     median: 7887 (7%)     max: 7944 Points
min: 7398     avg: 7794     median: 7826 (7%)     max: 7981 Points
8152 Points (7%)
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
min: 3591     avg: 3624     median: 3623.5 (22%)     max: 3654 Points
min: 3414     avg: 3560     median: 3582 (22%)     max: 3600 Points
3780 Points (23%)
wPrime 2.10 - wPrime 2.0 1024m *
100%
1 2330M +
min: 722     avg: 781     median: 789 (9%)     max: 826 s
100%
1 2328M +
min: 778     avg: 846     median: 801 (9%)     max: 1066 s
wPrime 2.10 - wPrime 2.0 32m *
100%
1 2330M +
min: 22     avg: 24.7     median: 25.1 (5%)     max: 26.38 s
100%
1 2328M +
min: 24.77     avg: 26.7     median: 25.2 (5%)     max: 32.91 s
WinRAR - WinRAR 4.0
100%
1 2328M +
2003 Points (12%)
X264 HD Benchmark 4.0 - x264 Pass 2
100%
1 2328M +
11.8 fps (5%)
X264 HD Benchmark 4.0 - x264 Pass 1
100%
1 2328M +
62.2 fps (17%)
TrueCrypt - TrueCrypt Serpent
100%
1 2330M +
0.1 GB/s (3%)
102%
1 2328M +
0.1 GB/s (3%)
TrueCrypt - TrueCrypt Twofish
100%
1 2330M +
0.2 GB/s (4%)
103%
1 2328M +
0.2 GB/s (4%)
TrueCrypt - TrueCrypt AES
100%
1 2330M +
0.2 GB/s (1%)
104%
1 2328M +
0.2 GB/s (1%)
3DMark 06 - CPU - 3DMark 06 - CPU
min: 2610     avg: 2629     median: 2627 (6%)     max: 2649 Points
min: 2638     avg: 2694     median: 2697 (6%)     max: 2741 Points
2829 Points (6%)
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
100%
1 2330M +
min: 17     avg: 17.6     median: 17.7 (4%)     max: 18 s
100%
1 2328M +
min: 17.69     avg: 18     median: 17.8 (4%)     max: 18.59 s
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
100%
1 2330M +
min: 40     avg: 40.3     median: 40 (2%)     max: 41 s
100%
1 2328M +
min: 39.91     avg: 40.4     median: 40.2 (2%)     max: 41.04 s
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
100%
1 2330M +
min: 926     avg: 936     median: 941 (4%)     max: 944 s
100%
1 2328M +
min: 924     avg: 933     median: 928 (4%)     max: 952 s
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
100%
1 2330M +
min: 33000     avg: 35000     median: 35000 (17%)     max: 37000 MIPS
108%
1 2328M +
min: 37460     avg: 39557     median: 37820 (18%)     max: 43390 MIPS
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
100%
1 2330M +
min: 22170     avg: 24085     median: 24085 (18%)     max: 26000 MFLOPS
112%
1 2328M +
min: 26610     avg: 26837     median: 26900 (21%)     max: 27000 MFLOPS
Windows 7 Experience Index - Win7 CPU
100%
1 2330M +
6.5 Points (83%)
95%
1 2328M +
min: 5.8     avg: 6.2     median: 6.2 (79%)     max: 6.5 Points
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
100%
1 2330M +
min: 6879     avg: 7014     median: 7008 (7%)     max: 7165 Points
100%
1 2328M +
min: 6842     avg: 6996     median: 7032 (7%)     max: 7052 Points
3DMark 11 - 3DM11 Performance Physics
100%
1 2330M +
min: 2782     avg: 2786     median: 2786 (10%)     max: 2790 Points
90%
1 2328M +
min: 2277     avg: 2508     median: 2508 (9%)     max: 2739 Points
3DMark - 3DMark Ice Storm Physics
100%
1 2328M +
min: 22765     avg: 23526     median: 23131 (15%)     max: 24681 Points
3DMark - 3DMark Cloud Gate Physics
100%
1 2328M +
min: 2035     avg: 2044     median: 2041 (5%)     max: 2057 Points
3DMark - 3DMark Fire Strike Standard Physics
100%
1 2328M +
min: 2821     avg: 2861     median: 2861 (7%)     max: 2901 Points
Geekbench 2 - 32 Bit - Geekbench Stream
100%
1 2328M +
4385 Points (35%)
Geekbench 2 - 32 Bit - Geekbench Memory
100%
1 2328M +
4009 Points (36%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
100%
1 2328M +
4616 Points (9%)
Geekbench 2 - 32 Bit - Geekbench Integer
100%
1 2328M +
3998 Points (8%)
Geekbench 2 - 32 Bit - Geekbench Total Score
100%
1 2328M +
4255 Points (11%)

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

Average Benchmarks Intel Core i3-2328M → 100% n=4

Average Benchmarks Intel Core i3-2348M → 105% n=4

- 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

v1.17
log 19. 16:25:30

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

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

#2 checking url part for id 3617 +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 Wed, 18 May 2022 13:12:25 +0200 +0s ... 0s

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

#6 linkCache_getLink no uid found +0.006s ... 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 2364 +0s ... 0.016s

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

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

#38 got single benchmarks 2364 +0.025s ... 0.041s

#39 getting avg benchmarks for device 3504 +0s ... 0.042s

#40 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.042s

#41 got single benchmarks 3504 +0.014s ... 0.057s

#42 getting avg benchmarks for device 3617 +0s ... 0.057s

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

#44 got single benchmarks 3617 +0.005s ... 0.063s

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

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

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

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

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

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

#51 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.065s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#110 linkCache_getLink no uid found +0s ... 0.068s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#153 linkCache_getLink no uid found +0s ... 0.074s

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

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

#156 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.074s

#157 linkCache_getLink no uid found +0s ... 0.074s

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

#159 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.074s

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

#161 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.074s

#162 linkCache_getLink no uid found +0s ... 0.074s

#163 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.074s

#164 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.074s

#165 linkCache_getLink no uid found +0s ... 0.074s

#166 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.074s

#167 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.074s

#168 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.075s

#169 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.075s

#170 linkCache_getLink no uid found +0s ... 0.075s

#171 linkCache_getLink no uid found +0s ... 0.075s

#172 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.075s

#173 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.075s

#174 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.075s

#175 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.075s

#176 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.075s

#177 linkCache_getLink no uid found +0s ... 0.075s

#178 linkCache_getLink no uid found +0s ... 0.075s

#179 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.075s

#180 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#181 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#182 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#183 linkCache_getLink no uid found +0s ... 0.076s

#184 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#185 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#186 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#187 linkCache_getLink no uid found +0s ... 0.076s

#188 linkCache_getLink no uid found +0s ... 0.076s

#189 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#190 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#191 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#192 linkCache_getLink no uid found +0s ... 0.076s

#193 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#194 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#195 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#196 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

#197 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

#198 linkCache_getLink no uid found +0s ... 0.077s

#199 linkCache_getLink no uid found +0s ... 0.077s

#200 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

#201 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

#202 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

#203 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

#204 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

#205 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

#206 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

#207 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.078s

#208 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.078s

#209 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.078s

#210 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.078s

#211 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.078s

#212 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.078s

#213 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.078s

#214 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.078s

#215 linkCache_getLink no uid found +0s ... 0.078s

#216 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.078s

#217 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.078s

#218 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.078s

#219 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.079s

#220 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.079s

#221 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.079s

#222 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.079s

#223 linkCache_getLink no uid found +0s ... 0.079s

#224 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.079s

#225 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.079s

#226 linkCache_getLink no uid found +0s ... 0.079s

#227 linkCache_getLink no uid found +0s ... 0.079s

#228 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.079s

#229 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.079s

#230 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.079s

#231 linkCache_getLink no uid found +0s ... 0.079s

#232 linkCache_getLink no uid found +0s ... 0.079s

#233 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.079s

#234 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.079s

#235 linkCache_getLink no uid found +0s ... 0.08s

#236 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.08s

#237 linkCache_getLink no uid found +0s ... 0.08s

#238 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.08s

#239 linkCache_getLink no uid found +0s ... 0.08s

#240 linkCache_getLink no uid found +0s ... 0.08s

#241 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.08s

#242 linkCache_getLink no uid found +0s ... 0.081s

#243 linkCache_getLink no uid found +0s ... 0.081s

#244 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.081s

#245 linkCache_getLink no uid found +0s ... 0.081s

#246 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.081s

#247 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.082s

#248 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.082s

#249 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.083s

#250 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.083s

#251 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.083s

#252 min, max, avg, median took s +0s ... 0.084s

#253 return log +0s ... 0.084s

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)