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

Intel Core i7-2720QM vs Intel Core i7-2637M

Intel Core i7-2720QM

► remove from comparison Intel 2720QM

Der Intel Core i7-2720QM 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 3 GHz (Belastung von 4 Kernen), 3.2 GHz (2 Kerne) und 3.3 Ghz (1 Kern) dynamisch gesteigert 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. Weiterhin sind nun ebenfalls AES Funktionen und ein verbesserter Dual Channel DDR3 Speichercontroller (DDR3-1066, 1333 und 1600 unterstützt) 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 Niveau einer Nvidia Geforce 310M Einstiegsgrafikkarte.  Durch die Turbo Boost Technologie wird sie von 650 MHz bis 1300 MHz getaktet.

Die Performance liegt dank der verbesserten Architektur deutlich oberhalb des Vorgängers i7-740QM und schlägt sogar deutlich den ehemaligen mobilen Spitzenreiter i7-940XM. Dadurch ist die Quad Core CPU für alle Anwendungen ausreichend schnell. Einen ausführlichen Test der starken Quad Core Sandy Bridge Prozessoren finden Sie hier.

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

► remove from comparison

Der Intel Core i7-2637M (fälschlich auch manchmal i7-2630UM bezeichnet) ist ein stromsparender ULV (Ultra Low Voltage) Prozessor für Subnotebooks. Mit 1.7 GHz Basistaktfrequenz ist er relativ gering getaktet, jedoch kann er dank Turbo Boost bis zu 2.8 GHz hochtakten (2.5 Ghz bei Belastung beider Kerne). Durch die Unterstützung von Hyperthreading können 4 Threads gleichzeitig bearbeitet werden. Verglichen mit dem langsameren i7-2617M, bietet der 2637M eine höhere Taktfrequenz (CPU Basistakt und Turbo, GPU Turbo).

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 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, 1200 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. Dadurch erreicht er in etwa die Leistung eines Core i3-2310M. Dies ist jedoch von der Kühlung des Chips abhängig damit der Turbo Boost "zünden" kann.

Die Sandy Bridge Doppelkernprozessoren beinhalten im angegebenen TDP von 17 Watt auch die Grafikkarte und den Speicherkontroller. Durch den Turbo Boost 2.0 wird der TDP jedoch unter Last eher ausgenutzt. Mit 17W TDP eignet sich der Prozessor auch für kleine und leichte Notebooks.

ModelIntel Core i7-2720QMIntel Core i7-2637M
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-2720QM2.2 - 3.3 GHz4 / 86 MB
Intel Core i7-2675QM compare2.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-2640M compare2.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-2637M1.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-2720QM2.2 - 3.3 GHz4 / 86 MB
Intel Core i7-2675QM compare2.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-2640M compare2.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-2637M1.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 - 3300 MHz1700 - 2800 MHz
L1 Cache256 KB128 KB
L2 Cache1 MB512 KB
L3 Cache6 MB4 MB
Cores / Threads4 / 82 / 4
TDP45 Watt17 Watt
Transistors995 Million624 Million
Technology32 nm32 nm
Die Size216 mm2149 mm2
max. Temp.100 °C100 °C
SocketFCBGA1224, FCPGA988BGA1023
FeaturesHD Graphics 3000 (650-1300MHz), DDR-1600 Memory Controller, HyperThreading, AVX, Quick Sync, VirtualizationTurbo Boost 2.0, Hyper-Threading, Virtualization VT-x, Virtualization for Directed I/O (VT-d), Trusted Execution, AES, Intel 64, Anti-Theft, My WiFi, Idle States, Enhanced SpeedStep, Thermal Monitorin, Execute Disable Bit
iGPUIntel HD Graphics 3000 (650 - 1300 MHz)Intel HD Graphics 3000 (350 - 1200 MHz)
Architecturex86x86
$378 U.S.$289 U.S.
Announced
ManufacturerIntel Core i7 2720QMIntel Core i7 2637M

Benchmarks

Cinebench R15 - Cinebench R15 CPU Multi 64 Bit
100%
1 2637M +
201 Points (2%)
Cinebench R15 - Cinebench R15 CPU Single 64 Bit
100%
1 2637M +
93 Points (33%)
Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
min: 5.12     avg: 5.3     median: 5.3 (10%)     max: 5.64 Points
min: 2.19     avg: 2.2     median: 2.2 (4%)     max: 2.25 Points
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
100%
1 2637M +
1.1 Points (31%)
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
min: 4114     avg: 4168     median: 4167 (37%)     max: 4219 Points
min: 3529     avg: 3578     median: 3600 (32%)     max: 3605 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
min: 13961     avg: 14649     median: 14852 (20%)     max: 15301 Points
min: 7046     avg: 7069     median: 7074 (10%)     max: 7086 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
min: 15819     avg: 17946     median: 18193 (16%)     max: 19061 Points
min: 8430     avg: 8639     median: 8722 (8%)     max: 8765 Points
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
min: 4204     avg: 5084     median: 5236 (32%)     max: 5299 Points
min: 4464     avg: 4469     median: 4471 (28%)     max: 4472 Points
wPrime 2.10 - wPrime 2.0 1024m *
min: 410.2     avg: 423     median: 423.5 (5%)     max: 435.633 s
min: 690.5     avg: 744     median: 765.3 (9%)     max: 776.305 s
wPrime 2.10 - wPrime 2.0 32m *
min: 12.13     avg: 13     median: 13.1 (3%)     max: 13.729 s
min: 20.3     avg: 21.2     median: 21.7 (4%)     max: 21.701 s
WinRAR - WinRAR 4.0
100%
1 2637M +
min: 2286     avg: 2325     median: 2324.5 (15%)     max: 2363 Points
X264 HD Benchmark 4.0 - x264 Pass 2
100%
1 2637M +
min: 11.95     avg: 12.1     median: 12.1 (5%)     max: 12.23 fps
X264 HD Benchmark 4.0 - x264 Pass 1
100%
1 2637M +
min: 68.5     avg: 70.1     median: 69.5 (19%)     max: 72.22 fps
TrueCrypt - TrueCrypt Serpent
100%
1 2637M +
min: 0.112     avg: 0.1     median: 0.1 (4%)     max: 0.116 GB/s
TrueCrypt - TrueCrypt Twofish
100%
1 2637M +
min: 0.196     avg: 0.2     median: 0.2 (4%)     max: 0.2 GB/s
TrueCrypt - TrueCrypt AES
100%
1 2637M +
1.2 GB/s (4%)
3DMark 06 - CPU - 3DMark 06 - CPU
min: 5133     avg: 5529     median: 5616 (12%)     max: 5772 Points
min: 2814     avg: 2836     median: 2834 (6%)     max: 2860 Points
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
min: 11     avg: 11.4     median: 11 (2%)     max: 12.3 s
min: 13.7     avg: 14     median: 14 (3%)     max: 14.32 s
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
min: 26     avg: 27     median: 27 (1%)     max: 28.2 s
min: 31.9     avg: 32.3     median: 32 (1%)     max: 33.02 s
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
min: 635     avg: 650     median: 647 (3%)     max: 671 s
min: 735.2     avg: 755     median: 757.8 (3%)     max: 772 s
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
109640 MIPS (52%)
45450 MIPS (22%)
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
66400 MFLOPS (51%)
29870 MFLOPS (23%)
Windows 7 Experience Index - Win7 CPU
7.5 Points (96%)
6.9 Points (88%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
min: 11457     avg: 17984     median: 18725 (19%)     max: 19716 Points
min: 7546     avg: 7733     median: 7552 (8%)     max: 8101 Points
3DMark 11 - 3DM11 Performance Physics
min: 5473     avg: 6495     median: 6627 (23%)     max: 7334 Points
3258 Points (12%)
3DMark - 3DMark Ice Storm Physics
36234 Points (23%)
27910 Points (18%)
3DMark - 3DMark Ice Storm Unlimited Physics
100%
1 2637M +
29096 Points (27%)
3DMark - 3DMark Cloud Gate Physics
5494 Points (14%)
2382 Points (6%)
3DMark - 3DMark Fire Strike Standard Physics
7558 Points (19%)
3294 Points (8%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
100%
1 2637M +
4566 Points (8%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
100%
1 2637M +
2288 Points (47%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Single-Core
100%
1 2637M +
2703 Points (42%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Multi-Core
100%
1 2637M +
4800 Points (12%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Single-Core
100%
1 2637M +
2769 Points (32%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Multi-Core
100%
1 2637M +
5048 Points (6%)
Octane V2 - Octane V2 Total Score
100%
1 2637M +
16640 Points (22%)
Power Consumption - Prime95 Power Consumption - external Monitor *
100%
1 2637M +
29.1 Watt (5%)
Power Consumption - Cinebench R15 Multi Power Consumption - external Monitor *
100%
1 2637M +
30.5 Watt (8%)

Average Benchmarks Intel Core i7-2720QM → 100% n=19

Average Benchmarks Intel Core i7-2637M → 68% n=19

- 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 24. 23:55:52

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

#1 checking url part for id 2736 +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.007s ... 0.007s

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

#6 linkCache_getLink no uid found +0.002s ... 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 using $NBC_LINKCACHE +0s ... 0.012s

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

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

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

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

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

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

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

#27 getting avg benchmarks for device 1499 +0s ... 0.012s

#28 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.013s

#29 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.014s

#30 got single benchmarks 1499 +0.021s ... 0.035s

#31 getting avg benchmarks for device 2736 +0.001s ... 0.036s

#32 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.037s

#33 got single benchmarks 2736 +0.02s ... 0.057s

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

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

#36 linkCache_getLink no uid found +0.001s ... 0.058s

#37 linkCache_getLink no uid found +0.001s ... 0.059s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#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 +0.001s ... 0.069s

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

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

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

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

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

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

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

#129 linkCache_getLink no uid found +0.001s ... 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.071s

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

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

#137 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.071s

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

#139 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.072s

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

#141 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.073s

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

#143 linkCache_getLink no uid found +0s ... 0.073s

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

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

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

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

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

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

#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 using $NBC_LINKCACHE +0s ... 0.074s

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

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

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

#157 linkCache_getLink using $NBC_LINKCACHE +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 no uid found +0s ... 0.075s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#181 linkCache_getLink no uid found +0.001s ... 0.078s

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

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

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

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

#186 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.081s

#187 linkCache_getLink no uid found +0.001s ... 0.081s

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

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

#190 min, max, avg, median took s +0s ... 0.083s

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

#192 return log +0.004s ... 0.086s

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)