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

Intel Core i7-2720QM vs Intel Core i7-2635QM

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-2635QM

► remove from comparison Intel 2635QM

Der Intel Core i7-2635QM 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 GHz kann dank Turbo Boost bei ausreichender Kühlung auf 2.6 GHz (Belastung von 4 Kernen), 2.8 GHz (2 Kerne) und 2.9 Ghz (1 Kern) dynamisch gesteigert werden. Im Vergleich zu den stärkeren Core i7 Versionen bietet der 2635QM kein VT-d und keine Trusted Execution Funktionen.

Im Vergleich zum 2630QM bietet der 2635QM einen etwas höheren Turbo Takt für die integrierte Grafikkarte (1200 MHz versus 1100 MHz) und wird im BGA Package geliefert (2630QM rPGA).

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 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.

Die Performance sollte vergleichbar mit dem Core i7-2630QM sein und damit knapp oberhalb eines i7-940XM liegen. 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.

ModelIntel Core i7-2720QMIntel Core i7-2635QM
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-2635QM2 - 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-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-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-2635QM2 - 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-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 - 3300 MHz2000 - 2900 MHz
L1 Cache256 KB256 KB
L2 Cache1 MB1 MB
L3 Cache6 MB6 MB
Cores / Threads4 / 84 / 8
TDP45 Watt45 Watt
Transistors995 Million995 Million
Technology32 nm32 nm
Die Size216 mm2216 mm2
max. Temp.100 °C100 °C
SocketFCBGA1224, FCPGA988FCBGA1224
FeaturesHD Graphics 3000 (650-1300MHz), DDR-1600 Memory Controller, HyperThreading, AVX, Quick Sync, VirtualizationHD Graphics 3000 (650-1200MHz), DDR-1333 Memory Controller, HyperThreading, AVX, Quick Sync, Virtualization
iGPUIntel HD Graphics 3000 (650 - 1300 MHz)Intel HD Graphics 3000 (650 - 1200 MHz)
Architecturex86x86
$378 U.S.
Announced
ManufacturerIntel Core i7 2720QMIntel Core i7 2635QM

Benchmarks

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: 4.6     avg: 4.7     median: 4.7 (9%)     max: 4.68 Points
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
min: 4114     avg: 4168     median: 4167 (37%)     max: 4219 Points
min: 3677     avg: 3697     median: 3699 (33%)     max: 3699 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
min: 13961     avg: 14649     median: 14852 (20%)     max: 15301 Points
min: 13045     avg: 13521     median: 13581 (19%)     max: 13581 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
min: 15819     avg: 17946     median: 18193 (16%)     max: 19061 Points
15522 Points (14%)
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
min: 4204     avg: 5084     median: 5236 (32%)     max: 5299 Points
4583 Points (28%)
wPrime 2.10 - wPrime 2.0 1024m *
min: 410.2     avg: 423     median: 423.5 (5%)     max: 435.633 s
486 s (6%)
wPrime 2.10 - wPrime 2.0 32m *
min: 12.13     avg: 13     median: 13.1 (3%)     max: 13.729 s
15 s (3%)
3DMark 06 - CPU - 3DMark 06 - CPU
min: 5133     avg: 5529     median: 5616 (12%)     max: 5772 Points
4906 Points (10%)
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
14 s (3%)
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
31 s (1%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
min: 635     avg: 650     median: 647 (3%)     max: 671 s
719 s (3%)
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
100%
1 2720QM +
109640 MIPS (52%)
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
100%
1 2720QM +
66400 MFLOPS (51%)
Windows 7 Experience Index - Win7 CPU
7.5 Points (96%)
7.4 Points (95%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
min: 11457     avg: 17984     median: 18725 (19%)     max: 19716 Points
16710 Points (17%)
3DMark 11 - 3DM11 Performance Physics
min: 5473     avg: 6495     median: 6627 (23%)     max: 7334 Points
5658 Points (20%)
3DMark - 3DMark Ice Storm Physics
100%
1 2720QM +
36234 Points (23%)
3DMark - 3DMark Cloud Gate Physics
100%
1 2720QM +
5494 Points (14%)
3DMark - 3DMark Fire Strike Standard Physics
100%
1 2720QM +
7558 Points (19%)

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

Average Benchmarks Intel Core i7-2635QM → 93% n=14

- 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. 16:16:43

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

#1 checking url part for id 1575 +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.008s

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

#6 linkCache_getLink no uid found +0.003s ... 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.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 1499 +0s ... 0.013s

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

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

#30 got single benchmarks 1499 +0.024s ... 0.039s

#31 getting avg benchmarks for device 1575 +0s ... 0.04s

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

#33 got single benchmarks 1575 +0.008s ... 0.048s

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

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

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

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

#38 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.049s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#142 linkCache_getLink no uid found +0s ... 0.058s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#158 min, max, avg, median took s +0s ... 0.06s

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

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

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)