Notebookcheck Logo

Intel Atom Z3735E vs Intel Atom Z3745

Intel Atom Z3735E

► remove from comparison Intel Z3735E

The Intel Atom Z3735E is a power-efficient quad-core SoC for tablets (mainly Android). It is clocked at 1.33 - 1.83 GHz and is part of the Bay Trail-T platform. Thanks to the specially optimized 22nm low-power design process (P1271) with Tri-Gate transistors, performance and energy efficiency have been significantly improved compared to its predecessor. In contrast to the Z3735D, the Z3735E only offers a 32 bit single-channel DDR3L-RS-1333 memory controller (max. 1 GB).

Architecture

The processor cores are based on the new Silvermont architecture, which is an out-of-order design for the first time. The increased utilization of the pipeline and many other improvements (optimized branch prediction, increased buffers, and enhanced decoders) have increased the performance per clock by about 50 percent. At the same time, however, the Hyper-Threading feature of the previous generation has been removed. Other major additions are the support for new instruction set extensions such as SSE 4.1 and 4.2 as well as AES-NI (depending on the model).

Performance

Thanks to 4 CPU cores and the improved performance per clock, the Z3735E is significantly faster than previous Intel Atoms like the Z2760. Depending on the benchmark, the Z3735E competes with AMDs Temash and Kabini APUs like the A6-1450 and A4-5000. For everyday tasks such as Internet or Office the performance is adequate, but not for very complex software or modern games. Compared to ARM SoCs for Android systems, the Z3735E is placed in the upper mid-range segment.

Graphics

The HD Graphics (Bay Trail) is based on the Intel Gen7 architecture, which supports DirectX 11 and is also found in the Ivy Bridge series (e.g. HD Graphics 4000). With only 4 EUs (Execution Units) and a relatively low clock speed of up to 646 MHz, the GPU is even slower than the HD Graphics (Ivy Bridge). Therefore, only older and less demanding games (like simple Android titles) will run fluently. However, video acceleration and other multimedia applications are no problem for the chip.

Power Consumption

The entire SoC is rated at an SDP of 2.2 W, which indicates a TDP of less than 4 W. Thus, the chip can be used in passively cooled tablets.

Intel Atom Z3745

► remove from comparison Intel Z3745

The Intel Atom Z3745 is a power efficient quad-core SoC for Windows and Android tablets. It is clocked at 1.33 - 1.86 GHz and part of the Bay Trail-T platform. Thanks to the specially optimized 22 nanometer low-power process (P1271) with tri-gate transistors, performance and energy efficiency have been significantly improved compared to its predecessor. Compared to the Z3740, the Z3745 is based on the new C0 stepping and offers a slightly increased GPU clock rate.

Architecture

The processor cores are based on the new Silvermont architecture, which is an out-of-order design for the first time. The increased utilization of the pipeline and many other improvements (optimized branch prediction, increased buffers, enhanced decoders) have increased the performance per clock by about 50 percent. At the same time, however, the Hyper-Threading feature of the previous generation has been removed. Other major changes are the support for new instruction set extensions such as SSE 4.1 and 4.2 as well as AES-NI (depending on the model).

Performance

Thanks to 4 CPU cores and the improved performance per clock, the Z3745 is significantly faster than previous Intel Atoms, e.g. the Z2760. Depending on the benchmark, the Z3745 competes with Temash and Kabini APUs like the AMD A6-1450 and A4-5000. For everyday tasks such as Internet or Office the performance is adequate, but not for very complex software or modern games.

Graphics

The HD Graphics (Bay Trail) is based on the Intel Gen7 architecture, which supports DirectX 11 and is also found in the Ivy Bridge series (e.g. HD Graphics 4000). With only 4 EUs (Execution Units) and a relatively low clock speed of up to 778 MHz, the GPU is even slower than the HD Graphics (Ivy Bridge). Therefore, only older and less demanding Windows games like World of Warcraft or Fifa will run fluently. However, video acceleration and display resolutions up to 2560 x 1600 pixels are no problem for the chip.

Power Consumption

The entire SoC is rated at an SDP of 2 watts, which indicates a TDP of less than 4 watts. Thus, the chip can be used in passively cooled tablets.

ModelIntel Atom Z3735EIntel Atom Z3745
SeriesIntel AtomIntel Atom
CodenameBay Trail-TBay Trail-T
Series: Atom Bay Trail-T
Intel Atom Z3795 compare1.59 - 2.39 GHz4 / 4
Intel Atom Z3785 compare1.49 - 2.41 GHz4 / 4
Intel Atom Z3775 compare1.46 - 2.39 GHz4 / 4
Intel Atom Z3775D compare1.49 - 2.41 GHz4 / 4
Intel Atom Z3770 compare1.46 - 2.4 GHz4 / 4
Intel Atom Z3770D compare1.5 - 2.41 GHz4 / 4
Intel Atom Z3736F compare1.33 - 2.16 GHz4 / 4
Intel Atom Z3736G compare1.33 - 2.16 GHz4 / 4
Intel Atom Z37451.33 - 1.86 GHz4 / 4
Intel Atom Z3745D compare1.33 - 1.83 GHz4 / 4
Intel Atom Z3740 compare1.33 - 1.86 GHz4 / 4
Intel Atom Z3740D compare1.33 - 1.83 GHz4 / 4
Intel Atom Z3735D compare1.33 - 1.83 GHz4 / 4
» Intel Atom Z3735E1.33 - 1.83 GHz4 / 4
Intel Atom Z3735F compare1.33 - 1.83 GHz4 / 4
Intel Atom Z3735G compare1.33 - 1.83 GHz4 / 4
Intel Atom Z3680 compare1.33 - 2 GHz2 / 2
Intel Atom Z3680D compare1.33 - 2 GHz2 / 2
Intel Atom Z3795 compare1.59 - 2.39 GHz4 / 4
Intel Atom Z3785 compare1.49 - 2.41 GHz4 / 4
Intel Atom Z3775 compare1.46 - 2.39 GHz4 / 4
Intel Atom Z3775D compare1.49 - 2.41 GHz4 / 4
Intel Atom Z3770 compare1.46 - 2.4 GHz4 / 4
Intel Atom Z3770D compare1.5 - 2.41 GHz4 / 4
Intel Atom Z3736F compare1.33 - 2.16 GHz4 / 4
Intel Atom Z3736G compare1.33 - 2.16 GHz4 / 4
» Intel Atom Z37451.33 - 1.86 GHz4 / 4
Intel Atom Z3745D compare1.33 - 1.83 GHz4 / 4
Intel Atom Z3740 compare1.33 - 1.86 GHz4 / 4
Intel Atom Z3740D compare1.33 - 1.83 GHz4 / 4
Intel Atom Z3735D compare1.33 - 1.83 GHz4 / 4
Intel Atom Z3735E1.33 - 1.83 GHz4 / 4
Intel Atom Z3735F compare1.33 - 1.83 GHz4 / 4
Intel Atom Z3735G compare1.33 - 1.83 GHz4 / 4
Intel Atom Z3680 compare1.33 - 2 GHz2 / 2
Intel Atom Z3680D compare1.33 - 2 GHz2 / 2
Clock1330 - 1830 MHz1330 - 1860 MHz
L1 Cache224 KB224 KB
L2 Cache2 MB2 MB
Cores / Threads4 / 44 / 4
TDP<4 Watt<4 Watt
Technology22 nm22 nm
SocketUTFCBGA1380UTFCBGA1380
FeaturesIntel HD Graphics (Bay Trail, 313 - 646 MHz), Quick Sync, Wireless Display, Clear Video HD, Intel 64, SSE 4.1, SSE 4.2, AES-NI, Secure Key, Anti-Theft, Identify-Protection, max. 1 GB Single-Channel (32 Bit) DDR3L-RS 1333, Quick SyncIntel HD Graphics (Bay Trail, 311 - 778 MHz), Quick Sync, Wireless Display, Clear Video HD, Intel 64, SSE 4.1, SSE 4.2, AES-NI, Secure Key, Anti-Theft, Identify-Protection, max. 4 GB Dual-Channel LPDDR3-1067
iGPUIntel HD Graphics (Bay Trail) (311 - 646 MHz)Intel HD Graphics (Bay Trail) (311 - 778 MHz)
Architecturex86x86
$21 U.S.$32 U.S.
Announced
ManufacturerIntel Atom Z3735EIntel Atom Z3745

Benchmarks

Cinebench R10 - Cinebench R10 Rend. Single (32bit)
100%
1 Z3745 +
min: 929     avg: 948     median: 941 (8%)     max: 973 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
100%
1 Z3745 +
min: 2491     avg: 3038     median: 3229 (4%)     max: 3393 Points
3DMark 11 - 3DM11 Performance Physics
100%
1 Z3745 +
min: 1005     avg: 1183     median: 1261 (4%)     max: 1284 Points
3DMark - 3DMark Ice Storm Physics
100%
1 Z3745 +
min: 14743     avg: 14957     median: 14945 (10%)     max: 15195 Points
3DMark - 3DMark Ice Storm Extreme Physics
100%
1 Z3745 +
min: 14732     avg: 15505     median: 15528 (13%)     max: 16016 Points
3DMark - 3DMark Cloud Gate Physics
100%
1 Z3745 +
min: 1186     avg: 1234     median: 1255 (3%)     max: 1261 Points
3DMark - 3DMark Fire Strike Standard Physics
100%
1 Z3745 +
1783 Points (4%)
Geekbench 2 - 32 Bit - Geekbench Stream
100%
1 Z3745 +
min: 1715     avg: 1772     median: 1772 (14%)     max: 1829 Points
Geekbench 2 - 32 Bit - Geekbench Memory
100%
1 Z3745 +
min: 1590     avg: 1660     median: 1660 (15%)     max: 1730 Points
Geekbench 2 - 32 Bit - Geekbench Floating Point
100%
1 Z3745 +
min: 2321     avg: 2724     median: 2723.5 (5%)     max: 3126 Points
Geekbench 2 - 32 Bit - Geekbench Integer
100%
1 Z3745 +
min: 1457     avg: 1759     median: 1759 (4%)     max: 2061 Points
Geekbench 2 - 32 Bit - Geekbench Total Score
100%
1 Z3745 +
min: 1811     avg: 2078     median: 2077.5 (5%)     max: 2344 Points
Sunspider - Sunspider 0.9.1 Total Score *
100%
1 Z3745 +
min: 621     avg: 667     median: 667 (6%)     max: 713 ms
Vellamo 3.x - Vellamo 3.x Browser
100%
1 Z3745 +
min: 2774     avg: 2964     median: 3011.5 (40%)     max: 3108 Points
Quadrant Standard Edition 2.0 - Quadrant Standard 2.0 Total Score
100%
1 Z3745 +
min: 17491     avg: 18396     median: 18279 (42%)     max: 19418 points
AnTuTu v4 - AnTuTu v4 Total Score
100%
1 Z3745 +
min: 31690     avg: 33031     median: 32811.5 (76%)     max: 34810 Points
AnTuTu v5 - AnTuTu v5 Total Score
100%
1 Z3745 +
min: 33318     avg: 34946     median: 33635 (34%)     max: 37656 Points
AnTuTu v6 - AnTuTu v6 Total Score
100%
1 Z3745 +
34692 Points (12%)
AndEBench - AndEBench Java
100%
1 Z3745 +
min: 875     avg: 958     median: 982 (30%)     max: 992 Iter./s
AndEBench - AndEBench Native
100%
1 Z3745 +
min: 14914     avg: 16893     median: 17437.5 (57%)     max: 17784 Iter./s
PassMark PerformanceTest Mobile V1 - PerformanceTest Mobile CPU Tests
100%
1 Z3745 +
min: 20763     avg: 26176     median: 27592 (4%)     max: 28757 Points
PCMark for Android - PCM f. Android Work Score
100%
1 Z3745 +
4298 Points (22%)

Average Benchmarks Intel Atom Z3745 → NAN% n=

- Range of benchmark values for this graphics card
- Average benchmark values for this graphics card
* 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 02. 10:03:53

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

#1 checking url part for id 5933 +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 Mon, 27 Jun 2022 13:12:58 +0200 +0s ... 0s

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

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

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

#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 5965 +0s ... 0.013s

#28 got single benchmarks 5965 +0s ... 0.013s

#29 getting avg benchmarks for device 5933 +0s ... 0.014s

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

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

#32 got single benchmarks 5933 +0.018s ... 0.032s

#33 got avg benchmarks for devices +0s ... 0.032s

#34 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.033s

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

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

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

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

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

#40 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 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.035s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#148 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.043s

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

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

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

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

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

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

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

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

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

#158 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.044s

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

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

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

#162 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.045s

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

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

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

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

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

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

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

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

#171 min, max, avg, median took s +0s ... 0.046s

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

#173 return log +0.004s ... 0.05s

Please share our article, every link counts!
> Notebook / Laptop Reviews and News > Benchmarks / Tech > Processor Comparison - Head 2 Head
Redaktion, 2017-09- 8 (Update: 2017-09-11)