Bencht euer Smartphone und gewinnt ein Honor 4C! - Seite 15

Seite 15 von 18 - Forum: Smartphones & Tablets auf overclockers.at

URL: https://www.overclockers.at/smartphones-tablets/bencht-euer-smartphone-und-gewinnt-ein-honor-4c_245323/page_15 - zur Vollversion wechseln!

Gerät: OnePlusOne
CPU: Qualcomm MSM8974AC Snapdragon 801
Cores: Quad-core 2.5 GHz Krait 400
GPU: Adreno 330
OS: CYANOGEN 12.0-YNG1TAS17L
Android Version: 5.0.2

Multicore:3009
Singlecore:996

Link: http://browser.primatelabs.com/geekbench3/5259163

Lg

Samsung Galaxy S6 --> http://geizhals.at/samsung-galaxy-s...z-a1237277.html


CPU: Samsung Exynos Octa 7420
Cores:
4 x ARM Cortex-A57 @ 2,1 Ghz
4 x ARM Cortex-A53 @ 1,5 Ghz
GPU: Mali-T760
Android: 5.1.1


Single-core: 1271
Multi-core: 4192

Validierung: http://browser.primatelabs.com/geekbench3/5259237

test nr. 2

Lenovo MEDION X5004

CPU: Qualcomm Snapdragon 615 1,5 GHz
Cores: 4x 1,5 GHz + 4x 1,1 GHz
GPU: Adreno 405
Android: 5.0.2

Single-score: 637
Multi-Score: 2461

val: http://browser.primatelabs.com/geekbench3/5261633

zuletzt bild vergessen

Btw. Cuero ist falsch eingetragen. muss wohl ein iPhone 6s Plus haben, kein 6 Plus

cheater! hängt ihn!!11!1!
stimmt:

Zitat von Cuero

Apple iPhone 6s Plus

CPU: Apple A9 - 1.85 GHz
OS: iOS 9.2.1
Singlescore: 2515
Multiscore: 4359

https://browser.primatelabs.com/geekbench3/5030088

Apple iPhone 6s

CPU: Apple A9 - 1.85 GHz
OS: iOS 9.2.1
Singlescore: 2554
Multiscore: 4446

https://browser.primatelabs.com/geekbench3/5030057

Nochmals mein Z5 compact:
http://browser.primatelabs.com/geekbench3/5268624
http://browser.primatelabs.com/geekbench3/5268664
Interessant wie die Werte variieren.

Auch noch ein letztes Bench mit dem Nexus 6P, nach wie vor Stock nur noch ein paar Tasks gekillt.

Google Nexus 6P (32GB)
CPU: Snapdragon 810, 4x 2.0 GHz Cortex-A57 + 4x 1.55 GHz Cortex-A53
GPU: Adreno 430
OS: Android 6.0.1
Singlescore: 1361
Multiscore: 5316

Google Nexus 5 32GB hammerhead
CPU: Qualcomm MSM8974 Snapdragon 800
2.27 GHz, 4x cores
GPU: Adreno 330 @ 450 MHz
OS: Android 6.0.1
singlescore: 921
Multiscore: 2707

Validierung:
http://browser.primatelabs.com/geekbench3/5035644

Sollt mein Moto vl auch nochmal benchen. Jetzt läuft ja Android 6.0 drauf

Edit:
OK macht keinen unterschied.
http://browser.primatelabs.com/geekbench3/5271978

Nur der Switch von Android 4 auf Android 5 bringt einen deutlich Performance-Schub.

Ich hab mein Xperia Ray (von 2011 ) vorgestern von 4.3 auf 5.1.1 geupgradet, der Bench-Score ist daraufhin ordentlich abgestürzt, aber es läuft trotzdem wesentlich besser - was vielleicht auch hauptsächlich an der Class-10 SD-Karte liegt.

ich würds ja ausprobieren, aber mir gefällt das alte android einfach zu gut

Zitat von mat

Nur der Switch von Android 4 auf Android 5 bringt einen deutlich Performance-Schub.

Ich habe es zahlreiche Male in der Liste beobachtet und bei meinem Review vom Honor 4C war es ebenso der Fall. Ein kurzer Blick in ein Lollipop-Review sagt:

Zitat

How could Google have squeezed more performance and more battery life out of a simple software update, you ask? Well, it comes down to ART, AOT compilation, and Project Volta.

ART, or the Android Runtime, has actually been available since Android 4.4 as an optional developer feature that could be enabled if you so choose. However with Android 5.0, ART is set as the default, effectively replacing the old 'Davlik' runtime that has been around for years. This change has many performance implications.

Davlik used a just-in-time (JIT) compiler to compile an application’s Java bytecode into native hardware instructions when said code was executed (such as when an app was opened). This form of compiler was necessary in older Android editions due to the hardware limitations of the devices it was running on, specifically in the storage and RAM departments.

ART shifts to an ahead-of-time (AOT) compiler, which compiles the entire application’s bytecode into native code only once, rather than each time the application is opened. As these native instructions typically use more space, apps themselves have a larger footprint on Android 5.0 and devices running ART; something that has only really been possible since RAM and NAND capacities of Android smartphones have increased.

By compiling applications into native code ahead of time – typically when the app is opened for the first time – a lot of system overhead is removed for any subsequent launch and use of the same app. Although this does mean the first launch of an app will be slower under ART than Davlik, after the first launch, performance should be improved.

Google also claims that by compiling the entire application at once and only once, it can achieve greater optimization of the code, which again should improve performance. As overhead is removed at the same time, battery life should be improved thanks to fewer CPU cycles going to compilation each time an app is opened and used.
ART also features an improved garbage collection (GC) mechanism, which works behind the scenes to allocate and reallocate memory. Previously, the GC system would have to pause code execution to clean up memory use, which would cause what Google describes as “jank”, or general stutter while using an app. With ART, the GC system has been improved to reduce pause times, in turn reducing jank. Combined with better memory allocation systems, and again performance increases.

overclockers.at v4.thecommunity
© all rights reserved by overclockers.at 2000-2025