I have just checked Geekbench for my iPhone 7 single (2648) multi (4560) and the original results from Februar 2017 is
single (3576) multi (6029). So I was blaming to iOS 11 , however the case of slowness is connected with the battery. I have lost up to 35% of the performance. So I am highly recommend either stay on 10.3.3 or upgrade to iOS 11 but change battery to get full performance. I will try to exchange battery after holidays
Key thing to do is run Geekbench again just
before you go in to change the battery. Then run it again
after it has a new battery in it.
Keep in mind the whole sequence of events here:
- Geekbench has illustrated that iPhones slow down with iOS "upgrades"
- Since that's a quantitative and repeatable experiment, it's hard to refute the "before & after."
- Apple has then spun it away as "older batteries," as if by throttling, they are doing something for all users (yes, I recognize this can be passionately argued both ways)
- In doing so, Apple has connected the quantitative & repeatable experiment slowdown to the idea that it's ONLY an aging battery triggering this iOS slow-down code
- Conceptually, that means when an older iOS device has a brand new battery installed by Apple, the Geekbench scores should jump right back up.
So many of us seem to be readily accepting Apple's excuse... even excited about getting to spend $29 bucks to put a new battery in an old iDevice. But the OTHER PART of that should get back to what led to the availability of this $29 battery option: that AFTER putting that new battery in, the iDevice should bypass the throttling code and be much faster, both in how fast
feels and in the quantitative measure of the very same Geekbench test run again.
On a bigger picture scale, there has long been conspiracy speculation that Apple writes throttling code into iOS updates to make older iDevices feel slower... to motivate us to buy new iDevices sooner. If there is any code in iOS that is there to do this, that could be the actual cause of the before & after Geekbench-measured slowdown, instead of- or in conjunction with- code that slows things down with an older battery. In other words, what if the battery excuse is just that- almost a "you're holding it wrong" excuse that Apple hoped would smooth over this whole thing? What if it's not the battery or barely the battery, but other iOS code specifically intended to make iDevices run slower with age?
Conceptually, that code- if it exists- also needs to be turned off after this battery is swapped. Else, users who happen to have Geekbench scores from when the prior battery was new will still be able to illustrate a quantitative, objectively-verifiable slowdown in spite of replacing an old battery with a new battery. Thus, there's potentially a
second Geekbench reveal in the wings here: after replacing the battery, how does the iDevice stack up against it's scores when it's prior battery was also new?
- If it's about the same, one might conclude that Apple told the truth and these slowdowns are in fact associated with aging batteries.
- If it's meaningfully inferior, it implies that there is other throttling code in iOS purposely slowing down older iDevices (even with brand new Apple batteries) and thus, this gesture doesn't actually address the real, underlying problem.
In either case, the net:net is very positive for us consumers. Either way, older iDevices must get faster for $29. AND if the conspiracy throttling is also in play, it is soon going to be easily & objectively caught by Geekbench tests run before and after the battery is replaced. Detect it again after battery replacement and this issue becomes bigger, pressuring Apple to ALSO turn off any of that (conspiracy) throttling NOT related to the battery. Net result (if that kind of code exists): even faster older iDevices in the potential second round of this.