A big LITTLE Problem: A Tale of big.LITTLE Gone Wrong
https://medium.com/@jadr2ddude/a-big-little-problem-a-tale-of-big-little-gone-wrong-e7778ce744bb [medium.com]
2018-11-02 18:17
ARM decided that instead of a one-size-fits-all design, building 2 kinds of cores would be the best way to solve this problem. Power-hungry “big” cores handle applications like games which demand speed at all costs, and low-power “LITTLE” cores handle light loads without draining the battery. This system is called “big.LITTLE” (and the modern variant of this is also called Heterogeneous Multi-Processing). It is transparent to applications — they start on a LITTLE core, and are moved to a big core as soon as the operating system detects that they are using a lot of processing power.
Well, at least that is the theory. Nobody and nothing is perfect.
Today it’s go’s turn to find out Exynos isn’t perfect.
source: L