Recent content by stuken

When using snes9x ex the performance is way down in comparison to nvidia update 110. The screen refresh rate as reported in the emulator is 48.85hz. If that's correct its far too low. In addition there appears to be another bug where ui animations stutter and loop back a few frames on...

The ram usage is for a base system, the absolute minimum for the Google software stack to run. There is basically no more ram left for any other applications without paging out essential processes. Hence the home screen redraws, background media being killed, redraws on tab switching in chrome...

CPU scaling appears to be almost unchanged from 5.0.1. It's still throttling up to 1.5ghz on a touch input and staying there even if CPU load is negligible. It is still running as hot as 5.0.1 on load which is expected given the above. RAM usage is still reading critical with the same frequency...

Not off to a great start. I've had my 3rd crash triggered simply by browsing to the reddit nexus 9 board. Now it appears to be on a forced cache erase after the consecutive crashes. From this we can safely say nobody in Google pays any attention the forum moaning otherwise they might have...

The DCO isn't that big of an issue. It's actually quite efficient when the cache is populated with the optimized code. Cache misses are only really going to be noticeable during an application boot which takes a few moments longer. The real issue is ram starvation and that stems mostly from the...

K1 is not an arm CPU. There is a code tranlation layer which takes the compiled arm64 abi opcodes and converts them to native k1 opcodes. This is pretty much like a caching jit compiler in that hot code paths get kept in a cache to be quickly reused. If an app has high cyclomatic complexity...

First off we loose 128mb for denver's opcode translation cache, then we have the increased kernel resident set size due to the 64bit support, then art does its 64bit compilation of android runtime applications which also require a larger memory footprint than a 32bit equivalent and finally we...

The problem is the configuration of the cpu governer. It ramps up to high speeds far too quickly in response to very light loads. It also throttle up to 1.5ghz in response to simple touch inputs. That is the reason you see such huge useage while browsing as you are constantly scrolling and...