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

Mediatek Helio P65 vs Mediatek Helio G88

Mediatek Helio P65

► remove from comparison Mediatek Helio P65

Der MediaTek Helio P65 ist ein Mitte 2019 vorgestellter ARM-SoC (System-on-a-Chip) der Mittelklasse, der sowohl in Smartphones als auch Tablets (hauptsächlich Android) eingesetzt werden kann. Er wird in 12 Nanometern gefertigt und verfügt über acht CPU-Kerne in zwei Cluster. Zwei große ARM Cortex-A75 Performance-Kerne mit bis zu 2 GHz und vier ARM Cortex-A55 Stromspar-Kerne. Weiters integriert der Prozessor ein Cat-7 (DL) / Cat-13 (UL) LTE Modem (4G) und eine ARM Mali-G52MP2 mit bis zu 820 MHz. Auch eine AI Processing Unit ist laut Mediatek verbaut.

Der SoC wird im 12nm (12FFC) Prozess bei TSMC produziert und sollte dadurch eine gute Energieeffizienz aufweisen.

Mediatek Helio G88

► remove from comparison Mediatek Helio G88

Der MediaTek Helio G88 ist ein ARM-SoC (System-on-a-Chip) der oberen Mittelklasse, der sowohl in Smartphones als auch Tablets (hauptsächlich Android) eingesetzt werden kann. Er wird in 12 FinFET Nanometern gefertigt und verfügt über acht CPU-Kerne in zwei Cluster. Zwei schnelle ARM Cortex-A75 Performance-Kerne mit bis zu 2 GHz und 6 ARM Cortex-A55 Stromspar-Kerne mit bis zu 1,8 GHz (univerifiziert, ev auch 2 GHz). Alle 8 Kerne können dank Heterogeneous Multi-Processing gleichzeitig genutzt werden. Im Vergleich zum baugleichen Helio G85, unterstüzt der G88 nun 90 Hz Displays und bietet Version 2.0 der HyperEngine.

Weiters integriert der Prozessor ein Cat-7 (DL) / Cat-13 (UL) LTE Modem (4G) und eine ARM Mali-G75MP2 mit bis zu 1000 MHz (Peak). Auch die HyperEngine, die man schon vom G70 und vom G90 kennt, ist wieder mit dabei. Das Feature soll die Verteilung der Ressourcen zwischen dem Prozessor, dem Grafikchip und dem Arbeitsspeicher möglichst effizient gestalten, um eine konstante Bildrate über einen langen Zeitraum zu gewährleisten.

Der MediaTek Helio G85 unterstützt bis zu 8 GB LPDDR4X-Arbeitsspeicher bei Taktfrequenzen bis zu 1.800 MHz, eine 48 MP Kamera, Bluetooth 5.0, Wi-Fi 802.11ac und eMMC 5.1-Speicher.

Der SoC wird im neuen 12nm (12FFC) Prozess bei TSMC produziert und sollte dadurch eine gute Energieeffizienz aufweisen.

ModelMediatek Helio P65Mediatek Helio G88
SeriesMediatek MediatekMediatek Mediatek
CodenameCortex-A75 / A55Cortex-A75 / A55
Serie: Mediatek Cortex-A75 / A55
Mediatek Helio P90 compare2.2 GHz8 / 8 Cortex-A75 / A55
» Mediatek Helio P652 GHz8 / 8 Cortex-A75 / A55
Mediatek Helio G881.8 - 2 GHz8 / 8 Cortex-A75 / A55
Mediatek Helio G85 compare1.8 - 2 GHz8 / 8 Cortex-A75 / A55
Mediatek Helio G80 compare2 GHz8 / 8 Cortex-A75 / A55
Mediatek Helio G70 compare2 GHz8 / 8 Cortex-A75 / A55
Mediatek Helio P90 compare2.2 GHz8 / 8 Cortex-A75 / A55
Mediatek Helio P652 GHz8 / 8 Cortex-A75 / A55
» Mediatek Helio G881.8 - 2 GHz8 / 8 Cortex-A75 / A55
Mediatek Helio G85 compare1.8 - 2 GHz8 / 8 Cortex-A75 / A55
Mediatek Helio G80 compare2 GHz8 / 8 Cortex-A75 / A55
Mediatek Helio G70 compare2 GHz8 / 8 Cortex-A75 / A55
Clock2000 MHz1800 - 2000 MHz
Cores / Threads8 / 88 / 8
Technology12 nm12 nm
Features2x ARM Cortex-A75, 6x ARM Cortex-A552x Cortex-A75, 6x Cortex-A55
iGPUARM Mali-G52 MP2 (820 MHz)ARM Mali-G52 MP2 ( - 1000 MHz)
ArchitectureARMARM
Announced
ManufacturerMediatek Mediatek Helio P65Mediatek Mediatek Helio G88

Benchmarks

Performance Rating - Geekbench 5.1, PCM Work, Sling Shot Physics, Antutu v8 CPU - Helio P65
24.5 pt (42%)
Performance Rating - Geekbench 5.1, PCM Work, Sling Shot Physics, Antutu v8 CPU - Helio G88
27.5 pt (47%)
3DMark - 3DMark Ice Storm Unlimited Physics
min: 13952     avg: 15592     median: 15591.5 (14%)     max: 17231 Points
3DMark - 3DMark Sling Shot Extreme (ES 3.1) Unlimited Physics
min: 2364     avg: 2396     median: 2395.5 (30%)     max: 2427 Points
2427 Points (30%)
3DMark - 3DMark Sling Shot (ES 3.0) Unlimited Physics
min: 2318     avg: 2392     median: 2392 (35%)     max: 2466 Points
2426 Points (35%)
Geekbench 2 - 32 Bit - Geekbench Stream
2564 Points (21%)
Geekbench 2 - 32 Bit - Geekbench Memory
4383 Points (40%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
10035 Points (20%)
Geekbench 2 - 32 Bit - Geekbench Integer
4526 Points (9%)
Geekbench 2 - 32 Bit - Geekbench Total Score
6229 Points (16%)
Geekbench 3 - Geekbench 3 64 Bit Multi-Core
5076 Points (8%)
7296 Points (11%)
Geekbench 3 - Geekbench 3 64 Bit Single-Core
1726 Points (35%)
2065 Points (42%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Single-Core
1836 Points (28%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Multi-Core
5483 Points (13%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Single-Core
1711 Points (20%)
1792 Points (21%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Multi-Core
5097 Points (6%)
5649 Points (7%)
Geekbench 5.0 - Geekbench 5.0 64 Bit Single-Core
357 Points (18%)
363 Points (18%)
Geekbench 5.0 - Geekbench 5.0 64 Bit Multi-Core
1211 Points (4%)
1257 Points (4%)
Geekbench 5.3 - Geekbench 5.1 - 5.4 64 Bit Single-Core
min: 351     avg: 354     median: 354 (17%)     max: 357 Points
365 Points (18%)
Geekbench 5.3 - Geekbench 5.1 - 5.4 64 Bit Multi-Core
min: 1222     avg: 1240     median: 1239.5 (4%)     max: 1257 Points
1265 Points (4%)
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
min: 3778.9     avg: 4074     median: 4073.8 (5%)     max: 4368.6 ms
3706 ms (4%)
Octane V2 - Octane V2 Total Score
min: 10422     avg: 10461     median: 10460.5 (14%)     max: 10499 Points
10625 Points (14%)
WebXPRT 3 - WebXPRT 3 Score
min: 51     avg: 51.5     median: 51.5 (15%)     max: 52 Points
48 Points (14%)
AnTuTu v8 - AnTuTu v8 UX
32430 Points (27%)
40633 Points (34%)
AnTuTu v8 - AnTuTu v8 MEM
32472 Points (26%)
40643 Points (33%)
AnTuTu v8 - AnTuTu v8 GPU
32053 Points (6%)
39982 Points (7%)
AnTuTu v8 - AnTuTu v8 CPU
60518 Points (22%)
63862 Points (23%)
AnTuTu v8 - AnTuTu v8 Total Score
157473 Points (15%)
185120 Points (18%)
PassMark PerformanceTest Mobile V1 - PerformanceTest Mobile CPU Tests
6412 Points (1%)
PCMark for Android - PCM f. Android Computer Vision
3553 Points (19%)
PCMark for Android - PCM f. Android Storage
8280 Points (22%)
PCMark for Android - PCM f. Android Work Score 2.0
min: 6291     avg: 6517     median: 6516.5 (43%)     max: 6742 Points
8248 Points (54%)
PCMark for Android - PCM f. Android Work Score
7594 Points (38%)
PCMark for Android - PCM f. Android Storage 2.0 score
10607 Points (30%)
PCMark for Android - PCM f. Android Work Score 3.0
8842 Points (50%)

Average Benchmarks Mediatek Helio P65 → 100% n=19

Average Benchmarks Mediatek Helio G88 → 111% 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 23. 09:23:28

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

#1 checking url part for id 14007 +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, 18 Jan 2022 12:10:47 +0100 +0s ... 0s

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

#5 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.005s

#6 linkCache_getLink no uid found +0.002s ... 0.007s

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

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

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

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

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

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

#13 composed specs +0s ... 0.007s

#14 did output specs +0s ... 0.007s

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

#16 getting avg benchmarks for device 12257 +0.001s ... 0.012s

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

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

#19 got single benchmarks 12257 +0.007s ... 0.02s

#20 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.021s

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

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

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

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

#25 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.021s

#26 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.021s

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

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

#29 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.021s

#30 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.022s

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

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

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

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

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

#36 getting avg benchmarks for device 14007 +0s ... 0.023s

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

#38 got single benchmarks 14007 +0.006s ... 0.029s

#39 got avg benchmarks for devices +0s ... 0.029s

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

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

#42 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.03s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#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.039s

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

#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.04s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#103 min, max, avg, median took s +0s ... 0.045s

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

#105 return log +0.004s ... 0.049s

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)