Re:iPhone update for Meltdown-Spectre: before/after performa...
by Infernal on Wednesday January 10, 2018 @03:30PM
(#16118747)
On an iPhone 6 - I actually gained performance from 11.2 to 11.2.2 (I neglected to run Geekbench on 11.2.1). Previously my best single-core score on iPhone 6 was 1536 (and only when battery was above 93% would I get in the 1500s), now today I got 1540 single core on only 66% battery - previously anything below about 70% battery would give me a score down in the 1200s.
Re:iPhone update for Meltdown-Spectre: before/after performa...
by jobu on Wednesday January 10, 2018 @03:45PM
(#16118902)
There really seems to be some performance issues with either the network stack or the threading/background processing in iOS11 on older devices.
I've had periodic slowdowns and unresponsiveness with my iPhone 6 since upgrading to 11, but a few weeks ago I was downloading a bunch of music for a trip and my phone was virtually unusable until the downloads were done. Since then I've noticed unresponsiveness around the same time I see notifications for podcast updates or after exiting an app that was downloading tons of content (e.g. The Weather Channel app).
Re:iPhone update for Meltdown-Spectre: before/after performa...
by ponchoalv on Wednesday January 10, 2018 @03:11PM
(#16118554)
same behaivor here... no perfomance / battery hit.
Re:iPhone update for Meltdown-Spectre: before/after performa...
by oatmealsnap on Wednesday January 10, 2018 @03:29PM
(#16118740)
6 or 6s?
Re:iPhone update for Meltdown-Spectre: before/after performa...
by delish on Wednesday January 10, 2018 @03:34PM
(#16118800)
I have a 6S+. I noticed a performance gain going from 11.2.1 to 11.2.2.
Before: 2384.
After: 2541.
Something's up. I updated my 6S yesterday and have noticed zero in performance changes or battery loss. Still plenty of bugs though, I was reading an email and the 'flag/file/trash/reply/new' bar totally went away. At least the touchscreen hasn't gone unresponsive, causing me to have to hit sleep/wake to toggle it back on. Maybe they finally fixed that.