(04-16-2015, 11:05 AM)samipower Wrote: [ -> ]Oh man, very very bad speed, 75000 points in antutu benchmark but poor graphic card, very slow speed, good cpu but bad graphic card, waiting for a nvidia x1 smartphone........ , or proyect ara with nvidia k1 ........
You'll be waiting a long time. There hasn't been a Tegra phone since the 4i/4 series, and going by trends of the K1, you can expect the X1 to be featured in maybe 2 or 3 tablets, and maybe 5 or 6 Chromebooks by the time next year, after they've announced the X1's successor. Nvidia's Tegra SoC's haven't been fit for smartphones for quite some time. Tegra SoC's get too hot and eat too much batter for smartphone use.
And the S6's GPU is quite good. Among one of the best commercially available on ARM right now behind. Nothing poor or slow about it. While driving a QHD screen resolution isn't helpful to battery life or GPU performance; although it is almost, but not quite as powerful as K1's GPU, its still much more efficient and runs alot more cooler. Dolphin's shortcomings is mostly in the software. A powerful device helps, but Dolphin on Android still has a ways to go.
Talking about android enhancements, i can see that there is a frameskipping value in the .ini config, but it doesn't seem to have any impact whatever value you enter. Is there a plan to implement frame skipping at some point ?
(04-20-2015, 06:28 PM)format_c Wrote: [ -> ]Talking about android enhancements, i can see that there is a frameskipping value in the .ini config, but it doesn't seem to have any impact whatever value you enter. Is there a plan to implement frame skipping at some point ?
Good question, I'm also interested in frameskip/auto frameskip. Also I just noticed dolphin pro doesn't show up in play store any longer for some reason
(04-20-2015, 11:08 AM)Ivalicenyan Wrote: [ -> ] (04-16-2015, 11:05 AM)samipower Wrote: [ -> ]Oh man, very very bad speed, 75000 points in antutu benchmark but poor graphic card, very slow speed, good cpu but bad graphic card, waiting for a nvidia x1 smartphone........ , or proyect ara with nvidia k1 ........
You'll be waiting a long time. There hasn't been a Tegra phone since the 4i/4 series, and going by trends of the K1, you can expect the X1 to be featured in maybe 2 or 3 tablets, and maybe 5 or 6 Chromebooks by the time next year, after they've announced the X1's successor. Nvidia's Tegra SoC's haven't been fit for smartphones for quite some time. Tegra SoC's get too hot and eat too much batter for smartphone use.
And the S6's GPU is quite good. Among one of the best commercially available on ARM right now behind. Nothing poor or slow about it. While driving a QHD screen resolution isn't helpful to battery life or GPU performance; although it is almost, but not quite as powerful as K1's GPU, its still much more efficient and runs alot more cooler. Dolphin's shortcomings is mostly in the software. A powerful device helps, but Dolphin on Android still has a ways to go.
Putting the S6's lackluster performance in dolphin out here as a dolphin failure is just false. The blame is on ARM for simply providing inferior slow drivers. Until that is fixed the S6 won't be running dolphin as well as the Tegra competition. There's no magic optimization that will fix bad firmware design. Dolphin on android has made amazing improvements, but you will never see dolphin bending over backwards to make certain SoC hardware work better, because it's not their problem. Dolphins shortcomings are mostly in the device GPU drivers, because the actual emulator runs great on devices with proper well designed drivers, like the K1 and X1. Say what you want about the abysmal availability, it doesn't change the fact that Tegra chips are just better at this.
Keep in mind that when trying to compare different SoC performance, you're also asking a company which focuses on CPU performance (ARM/Qualcomm/Samsung/Intel) to deliver powerful graphics drivers. The CPU itself has a minimal "driver" stack in the kernel to make it operate correctly. Applications like Dolphin use native instructions on these processors which are handled directly by the CPU. There is no driver layer involved in most of the operations (with the exception of kernel protected operations). But graphics is a completely different beast. Applications don't "compile" native GPU code. They make calls through a driver layer. The driver then processes the request, making the appropriate calls to the GPU using the native instructions of the GPU. For a GPU, drivers can be equally as important as the GPU itself. So NVIDIA does have a leg-up in this area due to being a graphics card business. And you can see the difference in problems between the SoCs. Tegra is seldom used in phones due to power and heat (this is an assumption on my part, re-using the reason listed above. I have no actual knowledge of specific power/thermal requirements or specs on any of the Tegra processors). On a larger device, this is less important because this can be overcome with larger batteries and better heat dissipation. While NVIDIA isn't as good at low thermals and low power consumption in a smaller package, it has more powerful graphics and a more refined graphics driver (including full OGL).
(04-21-2015, 04:38 AM)agrabren Wrote: [ -> ]Keep in mind that when trying to compare different SoC performance, you're also asking a company which focuses on CPU performance (ARM/Qualcomm/Samsung/Intel) to deliver powerful graphics drivers. The CPU itself has a minimal "driver" stack in the kernel to make it operate correctly. Applications like Dolphin use native instructions on these processors which are handled directly by the CPU. There is no driver layer involved in most of the operations (with the exception of kernel protected operations). But graphics is a completely different beast. Applications don't "compile" native GPU code. They make calls through a driver layer. The driver then processes the request, making the appropriate calls to the GPU using the native instructions of the GPU. For a GPU, drivers can be equally as important as the GPU itself. So NVIDIA does have a leg-up in this area due to being a graphics card business. And you can see the difference in problems between the SoCs. Tegra is seldom used in phones due to power and heat (this is an assumption on my part, re-using the reason listed above. I have no actual knowledge of specific power/thermal requirements or specs on any of the Tegra processors). On a larger device, this is less important because this can be overcome with larger batteries and better heat dissipation. While NVIDIA isn't as good at low thermals and low power consumption in a smaller package, it has more powerful graphics and a more refined graphics driver (including full OGL).
This is actually a pretty reasonable breakdown of generally how things work. One hing I would like to say, the Tegra power/heat thing is definitely an adapting issue. For those with shield's/nexus 9's you know that while the tablet can run super hot, it can also demonstrate remarkable efficiency. The SHIELD in particular has some amazing video playback stamina, something that older Tegra chips suffered through. It's adundantly clear that in normal light use, the K1 has the efficiency to match its competitors. However where the problems start is on the higher end of the scale. Tegra chips have amazing speed, but the top end generates a rather large amount of heat, and allowing this top end is what gives the chip trouble operating in phones (this is true for basically any Tegra chip). The power end is a different weird thing. The K1 actually has a max power draw that is higher than what some phones can even supply. Tablets sidestep this problem, but in a phone this top end becomes power limited. For those that like TDP, it's generally the same story. Low end is comperable, top end is excessive and requires throttling. Which can brings me to the final point: how could oems deal with it?. Simple, they'd end up throttling and capping the top end to prevent the processor from exceeding limits. And you would end up with a snapdragon 810 like situation where the processor is constantly being restricted and forced to underperform in order to operate within specific limits. Now it's not exactly the same, being that the 810 can barely idle without heating up, but the general idea is there. While the K1 can be made to operate within a phone, it requires more work and compromises than oems like making. So they go with other options that are more immediately usable. As a result, the vast majority of phones are equipped with snapdragon processors, and are under equipped for emulation. Samsung is one of the few large scale alternatives, but unfortunately they use a GPU maker that suffer from similar problems. dolphin on android's progress is actually being controlled by the limitations of these GPU makers, and until we see more Tegra devices, or more effort from Qualcomm and Mali, dolphin will stagnate in the performance department.
Is there a noticeable difference in performance between Dolphin on a SHIELD device (where full OpenGL is available) and the Nexus 9, which only has GLES?
The emulator runs better than expected. Though, ive only tested one game and wont be bothered to trY others. It manages to play PSO1&2+ barely. The only time it becomes "unplayable" is selecting a class in the character creation. But if youre patient enough itll eventually go through and speed up greatly. The rest of the game is a hit or miss. Each area is different. Some run at 30, others drag around 15. my biggest issue is the lack of on screen d-pad, but that could be remedied by a controller. Till then its savestates for me.
Hm, just noticed Exynos 7 does throttling quite a bit; CPU reached 59c, next up to find out at what temperature it starts to throttle
https://youtu.be/2-TAZVx5usU
With GLES 3.2 the driver issue should be less, but they could manage to still make it terrible, without buffer_storage they still have the ability to slow everything down for us.