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

Intel Core i3-2370M vs Intel Core i3-2367M

Intel Core i3-2370M

► remove from comparison Intel 2370M

Der Intel Core i3-2370M ist ein Mittelklasse Doppelkernprozessor für Notebooks welcher Ende 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-2370M 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-2370M jedoch nur für die Grafikkarte zum Einsatz. Weiters  ist ein verbesserter Dual Channel DDR3 Speicherkontroller für max. 16 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 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-2370M deshalb auf dem Level eines Core i3-390M. 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-2367M

► remove from comparison Intel 2367M

Der Intel Core i3-2367M ist ein stromsparender ULV (Ultra Low Voltage) Prozessor für Subnotebooks. Mit 1.4 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. Im Vergleich zu den teureren Modellen, bietet der i3 kein VT-d, Trusted Execution, AES oder vPro. 

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-2367M nicht zum Einsatz kommt). Weiters ist ein verbesserter Dual Channel DDR3 Speicherkontroller für max. 16 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, 1000 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 und damit deutlich über dem alten Core i3-380UM mit 1.33GHz. Die durchschnittliche Performance sollte daher auf dem Niveau eines AMD A4-3300M liegen (nur Prozessorleistung).

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-2370MIntel Core i3-2367M
SeriesIntel Core i3Intel Core i3
CodenameSandy BridgeSandy Bridge
Serie: Core i3 Sandy Bridge
» Intel Core i3-2370M2.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-2330M compare2.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-2367M1.4 GHz2 / 43 MB
Intel Core i3-2365M compare1.4 GHz2 / 43 MB
Intel Core i3-2357M compare1.3 GHz2 / 43 MB
Intel Core i3-2370M2.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-2330M compare2.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-2367M1.4 GHz2 / 43 MB
Intel Core i3-2365M compare1.4 GHz2 / 43 MB
Intel Core i3-2357M compare1.3 GHz2 / 43 MB
Clock2400 MHz1400 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, BGA1023FCBGA1023
FeaturesHD Graphics 3000, DDR3-1066/1333 Memory Controller (max 8GB), HyperThreading, AVX, Quick Sync, VirtualizationHD Graphics 3000 (350-1000MHz), DDR3-1066/1333 Memory Controller (max 8GB), HyperThreading, AVX, Quick Sync, Virtualization
iGPUIntel HD Graphics 3000 (650 - 1150 MHz)Intel HD Graphics 3000 (350 - 1000 MHz)
Architecturex86x86
$225 U.S.
Announced
ManufacturerIntel Core i3 2370MIntel Core i3 2367M

Benchmarks

Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
min: 2.04     avg: 2.2     median: 2.3 (4%)     max: 2.31 Points
min: 1.32     avg: 1.3     median: 1.3 (2%)     max: 1.35 Points
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
min: 0.88     avg: 0.9     median: 1 (27%)     max: 0.96 Points
min: 0.53     avg: 0.5     median: 0.5 (16%)     max: 0.56 Points
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
min: 3087     avg: 3132     median: 3135 (28%)     max: 3165 Points
min: 1789     avg: 1823     median: 1826.5 (16%)     max: 1856 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
min: 7006     avg: 7059     median: 7064 (10%)     max: 7104 Points
min: 3701     avg: 4046     median: 4107.5 (6%)     max: 4168 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
min: 8337     avg: 8507     median: 8505 (8%)     max: 8681 Points
min: 4695     avg: 4889     median: 4918 (4%)     max: 5048 Points
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
min: 3787     avg: 3886     median: 3903 (24%)     max: 3951 Points
min: 2198     avg: 2262     median: 2275 (14%)     max: 2293 Points
wPrime 2.10 - wPrime 2.0 1024m *
min: 660.7     avg: 700     median: 715.1 (8%)     max: 740.306 s
min: 1132.6     avg: 1207     median: 1240.6 (15%)     max: 1246.27 s
wPrime 2.10 - wPrime 2.0 32m *
min: 20.7     avg: 22     median: 22.5 (5%)     max: 23.376 s
min: 36.4     avg: 39     median: 39.2 (8%)     max: 41.326 s
wPrime 1.55 - wPrime 1.55 1024m *
100%
1 2367M +
1132 s (4%)
wPrime 1.55 - wPrime 1.55 32m *
100%
1 2367M +
36.2 s (19%)
WinRAR - WinRAR 4.0
min: 2070     avg: 2515     median: 2514.5 (16%)     max: 2959 Points
min: 1535     avg: 1537     median: 1536.5 (10%)     max: 1538 Points
X264 HD Benchmark 4.0 - x264 Pass 2
100%
1 2367M +
min: 7.33     avg: 7.4     median: 7.4 (3%)     max: 7.5 fps
X264 HD Benchmark 4.0 - x264 Pass 1
100%
1 2367M +
min: 39     avg: 40.5     median: 40.5 (11%)     max: 41.9 fps
TrueCrypt - TrueCrypt Serpent
0.1 GB/s (4%)
min: 0.061     avg: 0.1     median: 0.1 (2%)     max: 0.063 GB/s
TrueCrypt - TrueCrypt Twofish
min: 0.192     avg: 0.2     median: 0.2 (4%)     max: 0.196 GB/s
min: 0.101     avg: 0.1     median: 0.1 (2%)     max: 0.111 GB/s
TrueCrypt - TrueCrypt AES
min: 0.22     avg: 0.2     median: 0.2 (1%)     max: 0.222 GB/s
min: 0.118     avg: 0.1     median: 0.1 (0%)     max: 0.126 GB/s
3DMark 06 - CPU - 3DMark 06 - CPU
min: 2844     avg: 2878     median: 2869.5 (6%)     max: 2962 Points
min: 1609     avg: 1876     median: 1689 (4%)     max: 3246 Points
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
min: 16     avg: 16.3     median: 16.4 (4%)     max: 16.516 s
min: 27.4     avg: 27.5     median: 27.4 (6%)     max: 27.592 s
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
min: 37.3     avg: 37.6     median: 37.6 (2%)     max: 38 s
min: 61.137     avg: 61.5     median: 61.5 (3%)     max: 62.003 s
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
min: 859.265     avg: 865     median: 861.7 (4%)     max: 871 s
min: 1396     avg: 1405     median: 1403.7 (6%)     max: 1415.5 s
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
35330 MIPS (17%)
27570 MIPS (13%)
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
25650 MFLOPS (20%)
17080 MFLOPS (13%)
Windows 7 Experience Index - Win7 CPU
6.8 Points (87%)
min: 5.1     avg: 5.2     median: 5.2 (67%)     max: 5.2 Points
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
min: 7353     avg: 7659     median: 7782 (8%)     max: 7854 Points
min: 4231     avg: 4406     median: 4357.5 (4%)     max: 4609 Points
3DMark 11 - 3DM11 Performance Physics
100%
1 2370M +
min: 2796     avg: 2898     median: 2898 (10%)     max: 3000 Points
3DMark - 3DMark Ice Storm Physics
100%
1 2370M +
26098 Points (17%)
3DMark - 3DMark Cloud Gate Physics
100%
1 2370M +
2218 Points (6%)
3DMark - 3DMark Fire Strike Standard Physics
100%
1 2370M +
3155 Points (8%)

Average Benchmarks Intel Core i3-2370M → 100% n=20

Average Benchmarks Intel Core i3-2367M → 70% n=20

- 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 27. 15:53:25

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

#1 checking url part for id 2986 +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 Sun, 23 Jan 2022 12:10:51 +0100 +0s ... 0s

#4 linkCache_getLink no uid found +0.006s ... 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.011s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#24 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.012s

#25 got single benchmarks 3015 +0.014s ... 0.026s

#26 getting avg benchmarks for device 2986 +0s ... 0.027s

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

#28 got single benchmarks 2986 +0.021s ... 0.048s

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

#30 linkCache_getLink no uid found +0.001s ... 0.049s

#31 linkCache_getLink no uid found +0.001s ... 0.05s

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

#33 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.051s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#205 min, max, avg, median took s +0.001s ... 0.068s

#206 linkCache_getLink using $NBC_LINKCACHE +0.024s ... 0.092s

#207 return log +0.004s ... 0.096s

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)