@anshelsag Now you have confused me. The whole poi…
@anshelsag Now you have confused me. The whole point of big.LITTLE is that it is better cores and heterogeneous compute??
@anshelsag Now you have confused me. The whole point of big.LITTLE is that it is better cores and heterogeneous compute??
@anshelsag Exactly last year, before that we only had 32-bit, before that CPUs were dual-core, before that single-core? What is your point?
@anshelsag Oh, I see, so if ARM, Qualcomm, Samsung etc do it, they are wrong because Apple hasn’t done it. LOL.
@anshelsag LOL, now I know you are trolling me.
@anshelsag Not hoping, the Android scheduler in big.LITTLE phones is specifically designed to work better. Please read article I sent you.
@anshelsag How do you know that an Apple Ax processor wouldn’t be even more power efficient if it was used in a big.LITTLE config?
@anshelsag I don’t think you understand the principles of big.LITTLE or of the way the scheduler works.
@anshelsag Sorry I don’t understand. The Android scheduler picks the best core for the workload. See androidauthority.com/arms-intellige…
@anshelsag Who says they don’t get used? I don’t understand?
@anshelsag Which isn’t the point… Please read my article… More cores=more choice for the workload. Has nothing to do with max load.