It's currently on offer on Flipkart (homepage, above-the-fold):pic.twitter.com/PBh1zRSgs6
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
...and *that* mattered because costs for SoCs have a lot to do with die sizes...and the easiest thing to cut is cache.
Consumers don't know to look for L2/L3 cache sizes on the tin. How would you even start to explain cache coherence to a punter?
...and core counts are a lie. DVFS keeps most cores are spun down most of the time. I go into it a tiny bit here:https://www.youtube.com/watch?v=4bZvq3nodf4 …
But it's really hard to overstate the impact of code and data locality. A bigger cache means you go to main memory less.
Check out the chart here for context: https://www.anandtech.com/show/9837/snapdragon-820-preview/2 …
You *badly* want to be in that low/left end of the curve. The easiest way to get that is a bigger cache so more programs do more of the time
...yet, mostly for cost and marketing reasons, nearly all Android-ecosystem SoCs are CPU poor. Many have tiny L2 and little (if any) L3.
MEANWHILE IN CUPERTINO: https://en.wikipedia.org/wiki/Apple_A9 https://en.wikipedia.org/wiki/Apple_A10 https://en.wikipedia.org/wiki/Apple_A11
Yes, you're reading that right: between the A10 and the A11, Apple went from 3MB L2/4MB L3 to *8MB L2*
For a sense of scale: http://norvig.com/21-days.html#answers … https://people.eecs.berkeley.edu/~rcs/research/interactive_latency.html …
So back to our $100 phone. The slow-clocked (1.3Ghz) A53 cores are missing _any_ discernible cache. What does that mean?
It means that anything that isn't a tight loop on a small amount of data is going to suffer a main-memory read.
...and main-memory reads are 200x more expensive than local (L1) reads. Need that data to keep doing work? Tough luck.
These situations are called "stalls" or "waits"; CPU is spun up, but it's not retiring instructions (doing work): https://en.wikipedia.org/wiki/Wait_state
...which means that one of the worst effects of the cores-not-caches tradeoff in this phone is that it loses *power efficiency* too.
The best trade in mobile CPU design today is to swap caches for cores (looking at you @qualcomm, @SamsungSemiUS, & @MediaTek)
So how slow is the @MediaTek MT6737? Lets go to the film!
Here are some devices built with this chip:https://www.kimovil.com/en/list-smartphones-by-processor/mediatek-mt6737 …
...and they all score like this: https://browser.geekbench.com/v4/cpu/4478849
This is 8-9x slower than the iPhone 8: https://browser.geekbench.com/ios_devices/51
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.