Notebookcheck Logo

Intel Core i7-2675QM vs Intel Core i7-2640M

Intel Core i7-2675QM

► remove from comparison Intel 2675QM

Der Intel Core i7-2675QM ist ein Quad-Core Prozessor basierend auf der Sandy Bridge Architektur. Er bietet 4 Kerne und kann dank Hyperthreading 8 Threads gleichzeitig bearbeiten. Der Basistakt von 2,2 GHz kann dank Turbo Boost bei ausreichender Kühlung auf 2.8 GHz (Belastung von 4 Kernen), 3 GHz (2 Kerne) und 3,1 Ghz (1 Kern) dynamisch gesteigert werden. Im Vergleich zu den stärkeren Core i7 Prozessoren fehlt dem 2675QM wie beim 2630QM (Vorgänger) die VT-d und Trusted Execution Funktionen.

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. Weiters sind nun ebenfalls AES Funktionen und ein verbesserter Dual Channel DDR3 Speichercontroller direkt im Prozessor integriert.

Die integrierte 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 dem Niveau einer Nvidia Geforce 310M Einstiegsgrafikkarte. Dank Turbo Boost wird sie von 650 MHz bis 1200 MHz getaktet. Der sehr ähnliche Core i7-2670QM bietet im Vergleich eine geringere Turbo Boost Frequenz für die Grafikkarte von 1100 MHz.

Die Performance liegt knapp unterhalb des älteren Core i7-2720QM, welcher um 200 MHz höhere Turbo Boost Taktraten aufweist. Dadurch sollte der i7-2675M auch den Desktop Core i7-940 schlagen und für alle Anwendungen ausreichend Leistung aufbringen können.

Im Vergleich zu den Sandy Bridge Doppelkernprozessoren sind die Quad Core CPUs mit einer höheren TDP spezifiziert und eignen sich daher nur für große Notebooks. Im Vergleich zu den Clarksfield CPUs beinhaltet die TDP jedoch nun auch die Grafikkarte, wodurch sie im Schnitt sparsamer wurden.

Intel Core i7-2640M

► remove from comparison Intel 2640M

Der Intel Core i7-2640M ist der schnellste Doppelkernprozessor für Notebooks im 3. Quartal 2011 und löst den Core i7-2620M ab. Er bietet zwei Kerne und kann dank Hyperthreading 4 Threads gleichzeitig bearbeiten. Der Basistakt von 2,8 GHz kann durch Turbo Boost bei ausreichender Kühlung auf 3,3 GHz (Belastung von 2 Kernen) und 3,5 (1 Kern) dynamisch gesteigert werden. Im Vergleich zum langsameren i5-2540M, bietet der 2620M nicht nur eine höhere Taktrate, sondern auch mehr Last Level Cache (4 versus 3MB), der ältere 2620M ist jedoch nur geringer getaktet.

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. Weiters sind nun ebenfalls AES Funktionen und 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.

Die Performance liegt dank der verbesserten Architektur und des überarbeiteten Turbo Boost oberhalb einer ähnlich getakteten Arrandale CPU. Der 2640M sollte dadurch die Performance der schnellsten Arrandale Quad-Core Modelle erreichen (z.B. Core i7-920XM). Daher reicht die Leistung auch für anspruchsvolle Tätigkeiten wie HD Videoschnitt oder 3D Spiele. Durch die hohe Taktrate von 2.8 GHz (3.3 - 3.5 GHz mittels Turbo) hat der 2640M auch Vorteile gegenüber den langsamer getakteten Quad-Core Prozessoren bei Software die nur 1-2 Threads auslastet.

Die Sandy Bridge Doppelkernprozessoren beinhalten im angegebenen TDP von 35 Watt auch die Grafikkarte und den Speicherkontroller. Durch den Turbo Boost 2.0 wird der TDP jedoch unter Last durchaus ausgenutzt. Mit 35W TDP eignet sich der Prozessor am besten für 14" Notebooks und größer.

ModelIntel Core i7-2675QMIntel Core i7-2640M
SeriesIntel Core i7Intel Core i7
CodenameSandy BridgeSandy Bridge
Serie: Core i7 Sandy Bridge
Intel Core i7-2960XM compare2.7 - 3.7 GHz4 / 88 MB
Intel Core i7-2860QM compare2.5 - 3.6 GHz4 / 88 MB
Intel Core i7-2920XM compare2.5 - 3.5 GHz4 / 88 MB
Intel Core i7-2760QM compare2.4 - 3.5 GHz4 / 86 MB
Intel Core i7-2820QM compare2.3 - 3.4 GHz4 / 88 MB
Intel Core i7-2720QM compare2.2 - 3.3 GHz4 / 86 MB
» Intel Core i7-2675QM2.2 - 3.1 GHz4 / 86 MB
Intel Core i7-2670QM compare2.2 - 3.1 GHz4 / 86 MB
Intel Core i7-2635QM compare2 - 2.9 GHz4 / 86 MB
Intel Core i7-2630QM compare2 - 2.9 GHz4 / 86 MB
Intel Core i7-2640M2.8 - 3.5 GHz2 / 44 MB
Intel Core i7-2620M compare2.7 - 3.4 GHz2 / 44 MB
Intel Core i7-2649M compare2.3 - 3.2 GHz2 / 44 MB
Intel Core i7-2629M compare2.1 - 3 GHz2 / 44 MB
Intel Core i7-2677M compare1.8 - 2.9 GHz2 / 44 MB
Intel Core i7-2637M compare1.7 - 2.8 GHz2 / 44 MB
Intel Core i7-2657M compare1.6 - 2.7 GHz2 / 44 MB
Intel Core i7-2617M compare1.5 - 2.6 GHz2 / 44 MB
Intel Core i7-2960XM compare2.7 - 3.7 GHz4 / 88 MB
Intel Core i7-2860QM compare2.5 - 3.6 GHz4 / 88 MB
Intel Core i7-2920XM compare2.5 - 3.5 GHz4 / 88 MB
Intel Core i7-2760QM compare2.4 - 3.5 GHz4 / 86 MB
Intel Core i7-2820QM compare2.3 - 3.4 GHz4 / 88 MB
Intel Core i7-2720QM compare2.2 - 3.3 GHz4 / 86 MB
Intel Core i7-2675QM2.2 - 3.1 GHz4 / 86 MB
Intel Core i7-2670QM compare2.2 - 3.1 GHz4 / 86 MB
Intel Core i7-2635QM compare2 - 2.9 GHz4 / 86 MB
Intel Core i7-2630QM compare2 - 2.9 GHz4 / 86 MB
» Intel Core i7-2640M2.8 - 3.5 GHz2 / 44 MB
Intel Core i7-2620M compare2.7 - 3.4 GHz2 / 44 MB
Intel Core i7-2649M compare2.3 - 3.2 GHz2 / 44 MB
Intel Core i7-2629M compare2.1 - 3 GHz2 / 44 MB
Intel Core i7-2677M compare1.8 - 2.9 GHz2 / 44 MB
Intel Core i7-2637M compare1.7 - 2.8 GHz2 / 44 MB
Intel Core i7-2657M compare1.6 - 2.7 GHz2 / 44 MB
Intel Core i7-2617M compare1.5 - 2.6 GHz2 / 44 MB
Clock2200 - 3100 MHz2800 - 3500 MHz
L1 Cache256 KB128 KB
L2 Cache1 MB512 KB
L3 Cache6 MB4 MB
Cores / Threads4 / 82 / 4
TDP45 Watt35 Watt
Transistors995 Million624 Million
Technology32 nm32 nm
Die Size216 mm2149 mm2
SocketBGA
FeaturesHD Graphics 3000, DDR-1333 Memory Controller, HyperThreading, AVX, Quick Sync, Virtualization (VT-x)HD Graphics 3000, DDR3-1066/1333 Memory Controller (max 8GB), HyperThreading, AVX, Quick Sync, Virtualization
iGPUIntel HD Graphics 3000 (650 - 1200 MHz)Intel HD Graphics 3000 (650 - 1300 MHz)
Architecturex86x86
Announced
max. Temp.100 °C
$346 U.S.

Benchmarks

Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
100%
1 2640M +
min: 3.07     avg: 3.1     median: 3.2 (6%)     max: 3.2 Points
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
100%
1 2640M +
1.4 Points (4%)
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
100%
1 2640M +
min: 4009     avg: 4383     median: 4443 (40%)     max: 4506 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
100%
1 2640M +
min: 9691     avg: 9766     median: 9778 (13%)     max: 9833 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
100%
1 2640M +
min: 11067     avg: 11767     median: 11874 (11%)     max: 12037 Points
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
100%
1 2640M +
min: 5445     avg: 5549     median: 5534 (34%)     max: 5665 Points
wPrime 2.10 - wPrime 2.0 1024m *
100%
1 2640M +
min: 478.5     avg: 493.6     median: 489 (6%)     max: 524 s
wPrime 2.10 - wPrime 2.0 32m *
100%
1 2640M +
min: 15     avg: 15.5     median: 15.1 (3%)     max: 16.61 s
WinRAR - WinRAR 4.0
100%
1 2640M +
min: 2555     avg: 2632     median: 2620 (15%)     max: 2733 Points
X264 HD Benchmark 4.0 - x264 Pass 2
100%
1 2640M +
min: 16.38     avg: 16.9     median: 17 (8%)     max: 17.21 fps
X264 HD Benchmark 4.0 - x264 Pass 1
100%
1 2640M +
min: 88.7     avg: 91     median: 89.3 (24%)     max: 95 fps
TrueCrypt - TrueCrypt Serpent
100%
1 2640M +
min: 0.124     avg: 0.1     median: 0.1 (5%)     max: 0.152 GB/s
TrueCrypt - TrueCrypt Twofish
100%
1 2640M +
min: 0.198     avg: 0.2     median: 0.3 (6%)     max: 0.27 GB/s
TrueCrypt - TrueCrypt AES
100%
1 2640M +
1.6 GB/s (6%)
3DMark 06 - CPU - 3DMark 06 - CPU
100%
1 2640M +
min: 3882     avg: 3934     median: 3927 (8%)     max: 3978 Points
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
100%
1 2640M +
min: 11     avg: 11.2     median: 11 (2%)     max: 11.66 s
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
100%
1 2640M +
min: 25     avg: 26     median: 26 (1%)     max: 27.04 s
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
100%
1 2640M +
min: 604     avg: 626     median: 634 (3%)     max: 639 s
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
100%
1 2640M +
min: 64300     avg: 64523     median: 64545 (31%)     max: 64700 MIPS
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
100%
1 2640M +
min: 39000     avg: 39255     median: 39135 (30%)     max: 39750 MFLOPS
Windows 7 Experience Index - Win7 CPU
100%
1 2640M +
min: 7     avg: 7.2     median: 7.1 (91%)     max: 7.6 Points
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
100%
1 2640M +
min: 10127     avg: 10509     median: 10559 (11%)     max: 10838 Points
3DMark 11 - 3DM11 Performance Physics
100%
1 2640M +
min: 3902     avg: 4140     median: 4172 (14%)     max: 4320 Points
3DMark - 3DMark Ice Storm Physics
100%
1 2640M +
26569 Points (17%)
3DMark - 3DMark Cloud Gate Physics
100%
1 2640M +
2876 Points (7%)
Geekbench 5.4 - Geekbench 5.1 - 5.4 64 Bit Single-Core
100%
1 2675QM +
536 Points (26%)
Geekbench 5.4 - Geekbench 5.1 - 5.4 64 Bit Multi-Core
100%
1 2675QM +
1928 Points (7%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Single-Core
100%
1 2675QM +
3100 Points (36%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Multi-Core
100%
1 2675QM +
9800 Points (12%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Single-Core
100%
1 2675QM +
3100 Points (48%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Multi-Core
100%
1 2675QM +
10090 Points (25%)
Geekbench 2 - 32 Bit - Geekbench Stream
100%
1 2640M +
7873 Points (64%)
Geekbench 2 - 32 Bit - Geekbench Memory
100%
1 2640M +
6847 Points (62%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
100%
1 2640M +
7293 Points (14%)
Geekbench 2 - 32 Bit - Geekbench Integer
100%
1 2640M +
6298 Points (13%)
Geekbench 2 - 32 Bit - Geekbench Total Score
100%
1 2640M +
6913 Points (18%)

Average Benchmarks Intel Core i7-2675QM → NAN% n=

Average Benchmarks Intel Core i7-2640M → NAN% n=

- 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 19. 09:07:18

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

#1 checking url part for id 2839 +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, 16 Aug 2022 13:13:41 +0200 +0s ... 0s

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

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

#6 linkCache_getLink no uid found +0.003s ... 0.013s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#25 composed specs +0s ... 0.013s

#26 did output specs +0s ... 0.013s

#27 getting avg benchmarks for device 2870 +0.001s ... 0.014s

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

#29 got single benchmarks 2870 +0.007s ... 0.022s

#30 getting avg benchmarks for device 2839 +0s ... 0.022s

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

#32 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.024s

#33 got single benchmarks 2839 +0.009s ... 0.033s

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

#35 linkCache_getLink no uid found +0.001s ... 0.033s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#179 min, max, avg, median took s +0s ... 0.041s

#180 linkCache_getLink using $NBC_LINKCACHE +0.021s ... 0.061s

#181 return log +0.004s ... 0.065s

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