Hi all,
I was asking myself what is the performance of the dual core, is it better at 500Mhz dual or 800Mhz single ? Do it eat much battery at 500 dual or 800 single ..?
I run some bench and here are the results :
I've not be able to find a real consistency for the cunsumption..... i've got to run more test.
Result are the same for a single core / dual core .. !!
- "Idle" : 95mA
- 500Mhz : 220mA
- 800Mhz : 330mA
Datas :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Graph : The grey bold line is the overall score.
Bars :
- SD Read and Write performance are not connected with Processor frequency nor single/dual core mode.
- CPU performance is increasing a little faster than frequency (bus speed ?)
- Database I/O only gain a little from single to dual core (500/800/1200 : 9,5%/13%/2,3%) (not multi core optimised ?)
- 3D and 2D performance are not limited by the CPU when frequency > 500Mhz.
- Overall, 500Mhz dual core is faster than 800Mhz single core (Benchmark is multi core compliant)
- Overall, 800Mhz dual core is faster than 1200Mhz single core
Would you mind placing a graph of benchmark numbers vs. power consumption for your different cpu points (dual 500, 800 single, 800 dual, 1200 single)?
MisterTedster said:
Would you mind placing a graph of benchmark numbers vs. power consumption for your different cpu points (dual 500, 800 single, 800 dual, 1200 single)?
Click to expand...
Click to collapse
Problem is that cunsumption results seems inconsistant.. for the moment.
Honusnap said:
Hi all,
I was asking myself what is the performance of the dual core, is it better at 500Mhz dual or 800Mhz single ? Do it eat much battery at 500 dual or 800 single ..?
I run some bench and here are the results :
I've not be able to find a real consistency for the cunsumption..... i've got to run more test.
Result are the same for a single core / dual core .. !!
Click to expand...
Click to collapse
Great idea. And nice start with the bench marking!
Tool
I used Battery Monitor Widget to test the consumption, i've sent an email to the developers, is the kernel faulty... is it the application... is the hardware able to report a "real" consumption... ?
I'm asking around me to buy a device and mesure the current / wattage drawn... this should me the most efficient way to test the device, not needing internal device report that could be flawn by something i can't control.
They are using some small / cheap devices in the RC models world to mesure current / wattage... i will give it a try.
50% increase ratio?
I find it interesting to see a 50% increase from single to dual core, be it the battery consumption or the overall performance score
---------- Post added at 04:38 PM ---------- Previous post was at 04:27 PM ----------
Honusnap said:
I used Battery Monitor Widget to test the consumption, i've sent an email to the developers, is the kernel faulty... is it the application... is the hardware able to report a "real" consumption... ?
I'm asking around me to buy a device and mesure the current / wattage drawn... this should me the most efficient way to test the device, not needing internal device report that could be flawn by something i can't control.
They are using some small / cheap devices in the RC models world to mesure current / wattage... i will give it a try.
Click to expand...
Click to collapse
The consumption measures depends on device. SGS2 has the chip to produce the real data, but it's deactivated. Some custom kernel devs have been able to produce the real charge data in mA, but not the drain yet.
So the app can only estimates based on % changes. mV data are for more unreliable actually (going up/down the opposite way of the % at times).
Nevertheless running 3 Antutu bench should run for quite some time and consume a few percent, so I'd say the resulting mA is getting accurate.
What would be nice is a little piece of hardware that we could plug on the battery pins and connect to the USB of the device to produce the real mA consumption, then it would provide a standard way to compare battery drain from phone to phone.
3c said:
I find it interesting to see a 50% increase from single to dual core, be it the battery consumption or the overall performance score
---------- Post added at 04:38 PM ---------- Previous post was at 04:27 PM ----------
The consumption measures depends on device. SGS2 has the chip to produce the real data, but it's deactivated. Some custom kernel devs have been able to produce the real charge data in mA, but not the drain yet.
So the app can only estimates based on % changes. mV data are for more unreliable actually (going up/down the opposite way of the % at times).
Nevertheless running 3 Antutu bench should run for quite some time and consume a few percent, so I'd say the resulting mA is getting accurate.
What would be nice is a little piece of hardware that we could plug on the battery pins and connect to the USB of the device to produce the real mA consumption, then it would provide a standard way to compare battery drain from phone to phone.
Click to expand...
Click to collapse
I've found the little hardware... it is on the way home, 'real' test in two or three weeks..
Honusnap said:
I've found the little hardware... it is on the way home, 'real' test in two or three weeks..
Click to expand...
Click to collapse
Can you post the link on where to get this piece of hardware, i'd like to get one too.
3c said:
Can you post the link on where to get this piece of hardware, i'd like to get one too.
Click to expand...
Click to collapse
Hi Ced,
Excuse me for not replying to your email, the device is the "G.T. High Precision Watt Meter", i've found some review that says that it is not very precise, but certainly sufficient for the phone.
Than i remember having an old oscilloscope at my parent's home.. , so i will update graphs when being at their place, in two weeks.
Related
I'm curious to know if anyone has incredible results
I use quadrant and cf- bench, for now I have a quadrant screenshot, this is also my average score:
Uploaded at Picoodle.com
I use last Mysam rom with abysskernel 2.5
theendfear said:
I'm curious to know if anyone has incredible results
I use quadrant and cf- bench, for now I have a quadrant screenshot, this is also my average score:
Uploaded at Picoodle.com
I use last Mysam rom with abysskernel 2.5
Click to expand...
Click to collapse
At what cpu speed, 1600-1664-1704?
Use Antutu or CF-Bench...Quadrant is a random number generator.
Mine is fully stock and antutu gives something around 6200, what about others?
Sent from my GT-N7000 using XDA App
this is my score with cf-bench:
Uploaded at Picoodle.com
always with abyssnote kernel 2.5 and mysam rom at 1.66ghz
CPU at 1.7GHz @ Rocket ROM v11
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@vessk0 wow!! at antutu test 7528 its exellent! I tried now, and don't go up 6900.. I think Its time to change rom =)
Are the 3D benchmarks limited to ±58fps (the refresh rate of the screen)? Is there any v-sync off setting that could unleash the power and give better results?
Yup, as far as i know it's limited to 60 fps. (Correct me if i'm wrong)
vessk0 said:
CPU at 1.7GHz @ Rocket ROM v11
Click to expand...
Click to collapse
Do I saw something wrong?
RAM: 1205
how you do that? can you teach me?
Even better with v12, second in world N7000 chart
Sent from my GT-N7000 using XDA App
Hi vessk0, I have the same rom now, but the score is too low
what's your configuration? I tried with 1.7ghz, aggressive task killer in sistem tuner app, 2048mb cache on sd and noop setted in I/O scheduler section.. the score is around 6900-7000 points
For benchmark I use 1.7GHz @ Performance governer, but internal SD card in settings of Antutu. That's it.
vessk0 said:
For benchmark I use 1.7GHz @ Performance governer, but internal SD card in settings of Antutu. That's it.
Click to expand...
Click to collapse
every time I use 1.7GHz and performance gov. my phone allways freezes.
I tried some different roms and kernels but same result
any advice?
k-12 said:
every time I use 1.7GHz and performance gov. my phone allways freezes.
I tried some different roms and kernels but same result
any advice?
Click to expand...
Click to collapse
Check your voltages, try to reduce it to 1325-1350 for 1.7 (default is 1450). That'll help it run cooler, and make it less likely to lock up.
But that said, you may just have an Exynos chip that is not happy at that speed, there is no guarantee that they can all do 1.7.
Rocket ROM V12/Abyss 2.6 @1.7GHz Performance Governor:
Quadrant
Linpack
Antutu
CF-Bench
SunSpider
BrowserMark
Vellamo
And here's a fairly recent benchmark of the Droid Razr with some other phones...you can use this as rough basis of comparison.
http://www.anandtech.com/show/5198/motorola-droid-razr-review-a-better-clad-bionic/8
TL;DR: The Note really kicks ass when you crank up the clocks!
@croak I have tested your same combination rom/kernel and for now seems the best! with performance gov and cpu set to 1.7ghz the score is very higher in all tests
our note is one of the most promising device, estimating that the development is just at the beginning point
What's going to be amazing is how fast the upcoming A15-based Exynos will be. Clock for clock, it's supposed to be 20% faster than A9 cores. And they will be shipping at 2Ghz!
I expect that the A15 Exynos dual-core will outperform a quad-core Tegra 3 and use a lot less power doing it. And it'll be cheaper to make.
Croak said:
I expect that the A15 Exynos dual-core will outperform a quad-core Tegra 3 and use a lot less power doing it. And it'll be cheaper to make.
Click to expand...
Click to collapse
One of the 3 can not be right. If it outperform a quadcore hardly will be needing less power. If it needs less power hardly will outperform quadcores and at end if both are true then no way to be cheaper!!!!
From quadlogic!!!
Sent from my GT-N7000 using XDA App
I was looking into buying either the TF / Prime this past week, and have been looking into the benchmarks I see on the net. I've seen a few reviews, one from AnandTech, and the other one from Slashgear and random Antutu benches across the web.
If I'm understanding correctly, it seems the Prime obviously does have an edge, however for general non-gaming use it seems the differences are minimal? Can anyone confirm or if you own both to test it out?
In a javascript benchmark (AnandTech.com), I'd only see a 0.4-0.5 second difference loading JS heavy webpages?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The BrowserMark comparison at slashgear shows a 0.5-0.6 second gain by the Prime:
So are the benches really showing the difference is this minimal or are there more to talk about that I'm not seeing? (Not referring to game benches, not too interested in gaming)
From what I understand the main difference is in the GPU so for games and such it will matter... Also more hardware support for video making 1080p a feature now.
The cpu itself is clocked higher so I wonder what the differences would be with an equally clocked TF101. I guess barely noticable...
Off course there's the quadcore vs dualcore but I wonder if that really matters in day to day use. I don't expect a huge difference in user experience so in that regards I don't think there's a big reason to upgrade from TF101 to TF201.
I still will though, because the size decrease (and weight decrease) combined with the other factors still make it a nice upgrade. But looking at just performance, meh...
i overclock my Tf101 to 1.5ghz and its very fast now. i would argue an overclocked Tf101 would perform the same if not better than a prime in most of these tests.
But then again, the prime might have just as much overclocking room... Giving it the lead again.
The problem is that benchmarks generally mean absolutely nothing. Having a good benchmark doesn't mean you are going to get great real world use.
pside15 said:
The problem is that benchmarks generally mean absolutely nothing. Having a good benchmark doesn't mean you are going to get great real world use.
Click to expand...
Click to collapse
That's the thing, having a machine that benchmarks 26% faster (TF201 vs TF 101) does not mean that it is going to necessarily be faster in real life depending on the software and how it uses it.
Benchmarks should prove the Prime to be a better machine, singularly. Dual/quad-core, it’s all about apps utilization and user functionality.
Then there’s price/performance, (in my case) a $250 101 beats the 201.
That's the part of what I've been trying to say. If I'm only going to see a split second of differences (0.5 second) in browsing around heavy javascript or just general web browsing performance, is there more than this?
Seems like so far the only argument I can see about getting a Prime is a GPU and CPU boost to gaming fps by 20-30 fps.
What about outside of gaming, in respect to general tasks that can take some time, like compressing a zip of a nand backup or large rom files, general encryption, etc.
The price per performance of the TF101 definitely seems to be taking the lead if we aren't talking about gaming apps.
dagrim1 said:
But then again, the prime might have just as much overclocking room... Giving it the lead again.
Click to expand...
Click to collapse
My impression is that quad core performance vs dual core does not follow a linear scale.. If the way the architecture of 4x ARM CPU's (TF201) vs 2x (TF101) is any similar to how Intel Quad vs Duo started getting popularity a few years ago, I feel that there are going to be relatively few noticeable differences, when the dual can suit an average user without noticeably seeing any changes using a quad for their tasks... Mainly it will have to wait until which apps can utilize the multiple cores efficiently. Crysis for android?
Course I might be off base with this, that's why I wanted to ask you guys who have owned it.
Unless you are using high end games specifically designed for the Quad core/GPU, you should not notice a real difference. Much of what you do with any tablet or computer is speed dependent on outside sources ie network speed, ( both on your end and the other end) input speed etc. If you are using or rendering high end graphics, you will notice the difference, but then why use a tablet for that in the first place.
The first benchmark for Prime is done is slowest, power saving mode.
Asus TF201 Prime is the best
GasGuzz said:
Benchmarks should prove the Prime to be a better machine, singularly. Dual/quad-core, it’s all about apps utilization and user functionality.
Then there’s price/performance, (in my case) a $250 101 beats the 201.
Click to expand...
Click to collapse
The 201 actually has a 5th core that is for normal usage, so most of the time you will be running a single core. I have seen in benchmarks that the internal flash on the 201 is slower than the 101. The 201 also has only a mono speaker compared to the stereo 101. The 101 right now has overclocking and custom ROMs. Add in price and that is the reason I just bought a 101 instead of a 201.
Cheers!
-M
Xda member since 2007
hi , i have a Vietnamese made galaxy note 3 ( or that what it is written on the back side of the cellphone ) , it was really good , and i didn't suspect that it could be fake .... today i decided to run quadrant benchmark , it scored 18060 ... which was a little bit lower than the normal score for the note 3 ( it could reach 22000 )
when i checked the processor in the system specifications , it showed this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is it the real cpu information for the sm-n900 ? shouldn't it have 8 cores ( octa ) instead of 4 ? and how about the maximum frequency ( 1900 mhz ) ?
thanks in advance
i ran the Phone INFO ★Samsung★ application and it said that it is original , but i am still not sure about the processor cores ,doesn't exynos mobile have 8 cores ?
ghassan haddad said:
hi , i have a Vietnamese made galaxy note 3 ( or that what it is written on the back side of the cellphone ) , it was really good , and i didn't suspect that it could be fake .... today i decided to run quadrant benchmark , it scored 18060 ... which was a little bit lower than the normal score for the note 3 ( it could reach 22000 )
when i checked the processor in the system specifications , it showed this :
is it the real cpu information for the sm-n900 ? shouldn't it have 8 cores ( octa ) instead of 4 ? and how about the maximum frequency ( 1900 mhz ) ?
thanks in advance
Click to expand...
Click to collapse
It is a real one. SM-900 has 2 sets of 4 core processors. One set is low power A-7 and other is high power A-15 set. At a time only one set is active. In case of benchmarks, only the high power cluster works. Try downloading an app called CPU-z in the play store.
thanks for your reply , but may i ask you what advantage would i get from the octa core if only one quad is able to run at a time ? what difference would it make when compared to other quad core cellphones ?
ghassan haddad said:
thanks for your reply , but may i ask you what advantage would i get from the octa core if only one quad is able to run at a time ? what difference would it make when compared to other quad core cellphones ?
Click to expand...
Click to collapse
The answer would be battery life. While running small apps like messaging, whatsapp, twitter, watching movies etc, the small cores would do the job efficiently. Even small games like candy-crush, clash of clans etc run on these small cores. On the other hand, playing graphic intensive games, decoding/encoding videos or using photoshop on your phone would be taken care of by the larger cores.
that seems logical , thanks again for your explanation
ghassan haddad said:
that seems logical , thanks again for your explanation
Click to expand...
Click to collapse
Anytime mate..
In general, the phone has maximum of 4 cores online out of 8. It could be 4 Cortex-A7 (lower power consumption) or 4 Cortex-A15 (better performance) online at one moment. Or if the phone supports big.LITTLE architechture (which I am unable to confirm at the moment), then the phone can also mix these, so you can have 3 A7 cores and 1 A15 core online or 2 and 2 etc.
As for the frequency, A15 runs at up to 1900 MHz, which is also shown on the screenshot, and A7 runs at up to 1300 MHz.
i read that there were some attempts to make the 8 cores work at the same time using some patch , but that was cancelled by samsung itself due to the overheat and the high battery consumption ....
http://browser.primatelabs.com/geekbench3/search?dir=desc&q=Sony+SGP771&sort=multicore_score
I have to say i am very impressed!!!
This is mine!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Iviato dal mio Sony Z4 Tablet utilizzando Tapatalk
kutulu32 said:
http://browser.primatelabs.com/geekbench3/search?dir=desc&q=Sony+SGP771&sort=multicore_score
I have to say i am very impressed!!!
Click to expand...
Click to collapse
So much for better thermal capabilities of a tablet. Apparently the Snapdragon 810 throttles as much as ever, despite the more space offered by the tablet.
Here's M9's scores by comparison: http://browser.primatelabs.com/geekbench3/search?dir=desc&q=htc+one+m9&sort=score
And exynos' (doesn't throttle): http://browser.primatelabs.com/geekbench3/search?dir=desc&q=+SM-G920S&sort=multicore_score
....in one word, disappointing.
BTW SD810 was/is supposed to perform (almost) the same as exynos 7420 when it doesn't throttle. Hoped that this tablet would too, well it doesn't (it throttles) so it is a pass for me :/
It's a shame if it in fact throttles despite being a tablet and the new revision of the chip but it will not affect normal usage and should not be a problem.
Skickat från min LG-V500 via Tapatalk
The processor shouldn't get throttled in this tablet as it's inside a larger shell and should be able to disperse heat a lot better than inside a phone.
Sent from my SGP612 using Tapatalk
Sent from my SGP712 using Tapatalk
Stevethegreat said:
So much for better thermal capabilities of a tablet. Apparently the Snapdragon 810 throttles as much as ever, despite the more space offered by the tablet.
Here's M9's scores by comparison: http://browser.primatelabs.com/geekbench3/search?dir=desc&q=htc+one+m9&sort=score
And exynos' (doesn't throttle): http://browser.primatelabs.com/geekbench3/search?dir=desc&q=+SM-G920S&sort=multicore_score
....in one word, disappointing.
BTW SD810 was/is supposed to perform (almost) the same as exynos 7420 when it doesn't throttle. Hoped that this tablet would too, well it doesn't (it throttles) so it is a pass for me :/
Click to expand...
Click to collapse
Even mi note pro throttles i know but nevertheless even with throttling the specs are nice.
My lg gflex 2 also throttles but with the right tweaking gaming performance is perfect.i think this tablet is very good for gaming. As for the comparisom between 810 and exynos (s6) nobody said that 810 is better.
kutulu32 said:
Even mi note pro throttles i know but nevertheless even with throttling the specs are nice.
My lg gflex 2 also throttles but with the right tweaking gaming performance is perfect.i think this tablet is very good for gaming. As for the comparisom between 810 and exynos (s6) nobody said that 810 is better.
Click to expand...
Click to collapse
Yeah but they should had been equal (given their specs) if it was not for throttling. I just can't see why a tablet should throttle at all. Maybe it's bad design from Sony's part. For example nexus 9 doesn't throttle despite the fact that Tegra K1 has a greater TDP than Snapdragon 810. I mean SD810 has a relatively low TDP, it should not throttle on tablets, period...
Stevethegreat said:
I just can't see why a tablet should throttle at all.
Click to expand...
Click to collapse
The reason it throttles is likely because excessive power dissipation, even if it doesn't cause heating problems can still degrade the battery life. So Sony has possibly and wisely chosen this strategy so you and I can have close to 20 hours of running time. I am sure if you run exynos at full clock rate the battery life will be horrible too. So I guess if you want long battery life that is the price you pay.
Keep I mind that the maximum performance is still there to utilize if you need it once in a while, just not continually, which is consistent with most real life use scenarios . 99% of users don't see any significant impact on their user experience.
najoor said:
The reason it throttles is likely because excessive power dissipation, even if it doesn't cause heating problems can still degrade the battery life. So Sony has possibly and wisely chosen this strategy so you and I can have close to 20 hours of running time. I am sure if you run exynos at full clock rate the battery life will be horrible too. So I guess if you want long battery life that is the price you pay.
Keep I mind that the maximum performance is still there to utilize if you need it once in a while, just not continually, which is consistent with most real life use scenarios . 99% of users don't see any significant impact on their user experience.
Click to expand...
Click to collapse
Depends on what you do. On multi window situations 20% more sustained performance can be a godsend, the difference between a leggy and a fluid experience. On my Samsung Tab's multiwindow low performance is always an issue and only Exynos 7420 / Snap 810 may solve it.
Now I understand that Xperia Tab is not that (no multiwindow), but I was thinking to install Linux arm and use it as my net book (in conjuction with the keyboard dock) as well as my tablet. Now I'm having second thoughts. I know I'm a minority in my needs from a tablet but I think a tablet SoC should behave differently than its phone counterpart. More potentialities in tablets.
I would think that next to stamina mode , a performance mode (existing only in Xperia tabs) would be welcomed. Sure battery would suffer but even 6-7 hours of laptop use is great for what it is. It would be like having a "laptop mode" (where one can use the full potential of the SoC) and a tablet mode (as it is today). I don't like constraints it is all...
BTW exynos 7420 throttles significantly less even after sustained usage (15-30 minutes). It still throttles but nowhere near SD810 levels, there is a gulf between them making Exynos to seem the significantly faster (even tough it isn't in raw numbers). Here's hoping Tab S2 would be using the 7420 (and not any older model), still I prefer Sony, xperia's weight and aspect ratio. For someone like me, this tablet represents a lost chance all because of throttling :/
Do we know which 810 version gives those numbers?
There is a word out there that there is a newer version of the SD810 that had the overheating problem solved. Looks like it is not very wide spread yet though, and many early batches still have the old version.
So, we need to know if there is a difference in throttling between both version or not. After all those who plan to get the devices will buy it with the new version most probably.
Anyone knows how to know which processor version the tablet has?
Has anyone tested the SD 815 USA version of the z4?
6thfloor said:
Has anyone tested the SD 815 USA version of the z4?
Click to expand...
Click to collapse
Couldn't find anything on that. Afaik there is/won't be no US model of the Z4T. And afaik the Snapdragon 815 doesn't exist.
Hi,
Been monitoring battery performance and CPU sleep states, and one thing I notice is that on my device the A53's spent a surprising amount of time at 1Ghz+ when the screen is on, and one of the A57 cores is always running a 384 when the device is idle, while the other 3 sleep. Is this Sony's attempt to keep the UI snappy? Having the A57 on all the time (screen on), even at that low frequency is going to use in the region of 100mW+ (which is about 4x that of each A53 core)
Can someone else sanity check my results?
I'm using perfmon, systempanel, and "floating monitors"
Perfmon can be found here: http://forum.xda-developers.com/showthread.php?t=1933284
It's also on the market for the price of a coffee, please consider buying it - great tool!
Yep sounds about right this Greek review:
https://translate.google.co.uk/tran.../2015/10/24/sony-xperia-z5-review/&edit-text=
Found that in most cases only one A57 core runs in the Z5.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pardon my ignorance but...how much worse do you think it is to run only the big cores and throttle them from 2Ghz to 300Mhz without turning ON and switching to the little ones? (In other words...disable the big little technology and just use the best 4 cores).
We're now using the little cores more than the big ones....and that 1.5Ghz cap could be the reason of a lot of stutters.
Changing the topic, now that Google is selling Nexus devices (5X and 6P) with big little. I think they will improve this ARM technology in future Android versions (including the kernel).
Sent from my E5823
thesebastian said:
Pardon my ignorance but...how much worse do you think it is to run only the big cores and throttle them from 2Ghz to 300Mhz without turning ON and switching to the little ones? (In other words...disable the big little technology and just use the best 4 cores).
We're now using the little cores more than the big ones....and that 1.5Ghz cap could be the reason of a lot of stutters.
Changing the topic, now that Google is selling Nexus devices (5X and 6P) with big little. I think they will improve this ARM technology in future Android versions (including the kernel).
Sent from my E5823
Click to expand...
Click to collapse
The little cores will be perfectly fine for most daily mundane tasks, such as checking emails, messaging etc. The stutters you mention probably is because the phone launched just before Marshmallow and Sony are focusing more on that OS, same kind of thing with the camera. The current camera app is just a placeholder for the proper app due for release in a week or two.
thesebastian said:
Pardon my ignorance but...how much worse do you think it is to run only the big cores and throttle them from 2Ghz to 300Mhz without turning ON and switching to the little ones? (In other words...disable the big little technology and just use the best 4 cores).
We're now using the little cores more than the big ones....and that 1.5Ghz cap could be the reason of a lot of stutters.
Changing the topic, now that Google is selling Nexus devices (5X and 6P) with big little. I think they will improve this ARM technology in future Android versions (including the kernel).
Sent from my E5823
Click to expand...
Click to collapse
In short, no. The little cores, whilst relative to the A57's are weak, they are by no means underpowered for running the UI and such. Do consider that the A53 core is faster than the A9 cores that powered previous flagships such as the Galaxy S3. Leaving one of the A57's ticking in the background is probably not such a bad idea having thought about it, as it allows fast handover when the high performance is required; I do however hypothesise that some of the stuttering might be due to threads being handed over to the A57, whilst it is running down at 384, which will be somewhat slower than the high frequency A53 core(s) the process is being passed from. It may be that we see a touch-boost or more aggressive CPU governor brought in to rectify this.
On a related note, there is a good article on the power-aware BIG.little implementation in the Snapdragon 810 here:
http://www.anandtech.com/show/8933/snapdragon-810-performance-preview/4
Definitely for performance.
If they weren't set is this fashion the UI would feel sluggish and sluggish on wake up.
Your findings sound perfectly normal/adequate, resemble a "interactive" CPU governor.