61–70 of 119 posts
https://twitter.com/enstyled/status/948892447765131264
TLDR: It's 11.2.1 that is throttling the older iPhones, because of the battery wear.
Why does Cloudflare tell me I'm able to browse a snapshot while the site is offline, but there is no snapshot?
This is because, humorously, the snapshot is actually of the 502 page. Apparently Cloudflare kicked in too late.
>> a significant decrease in performance on the iPhone 6 up to 50% 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 tha…
same behaivor here... no perfomance / battery hit.
Wow. After ios 10.2.1 halved performance on my iphone 6 due to the battery issues, I next avoided 11.0 as I accepted responsiveness would be slower on the older iphone6 model. Now if we want these security fixes that's another -40%... Yikes! However, it looks like ios 11.2.2 and a new battery is still slightly faster than ios 10.3.3 and an old battery! (geekbench single/multi core score from article of 924/1616 vs my…
I don't understand this logic at all. The fixes are being made for a reason... avoiding the update just means you are getting more performance for a less secure system. Are you betting on a law of averages to break in your favor? Hoping you're not a target of hackers? what am I missing with this strategy?
>> a significant decrease in performance on the iPhone 6 up to 50% 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 tha…
Earlier quoted context omitted.
I don't understand this logic at all. The fixes are being made for a reason... avoiding the update just means you are getting more performance for a less secure system. Are you betting on a law of averages to break in your favor? Hoping you're not a target of hackers? what am I missing with this strategy?
All of these issues require local execution. It’s perfectly fine for many single user, performance critical use cases to make this type of security trade off.
Delivered via JavaScript
Earlier quoted context omitted.
It's energy providers that will win the most.
All major cloud providers are buying renewables for their operations. Yay? At least the additional renewable generation capacity built out will exist for decades (while processors should become more efficient as these security issues are addressed and new hardware rolls out).
Not yay. This is an overnight massive bump so they are going to consume from the same existing pool of renewables, forcing utilities to use more non renewables to make up for the demand difference.
Also, even when they do build out the renewable generation to make up the difference, it's still environmentally a problem due to the manufacturing of the renewable generation (solar panels, windmills, transformers, etc).
We have no surplus of renewable energy to absorb this kinda stuff so more energy usage is always bad at this point. It's just slightly less bad when they commit to paying to fund renewable.
Why does Cloudflare tell me I'm able to browse a snapshot while the site is offline, but there is no snapshot?
This is because, humorously, the snapshot is actually of the 502 page. Apparently Cloudflare kicked in too late.
I just ran GeekBench 4 on my iPhone X on iOS 11.2.2 vs 11.2.1. Single core: 4239 vs 4241 Multi-core: 10081 to 10203 So no difference.
I wonder what the difference is between the 6 used in the benchmark in the article and the iPhone X that would cause these different results. They both support speculative execution. Either way, encouraging results to a fellow iPhone X user.
Ok, I'm sceptical about the results. The reason is that there doesn't seem to be a massive difference between the tests. Since this fix is about speculative exec, why would it affect crypto code which is very register based and branchless as much as sqlite which is full of branches and memory/storage based? Why would it affect AES which is hardware accelerated as much as integer processing which is not? I'm not sayin…
The low scores in the article are in a similar ballpark to my (slow) iphone 6 on ios 10.3.3 with a 3yr old battery - i.e. about half what they should be with a fresh battery.