News for hackers. Stuff that matters.
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by acdha on Thursday February 09, 2023 @02:23PM (#34729754)
You care about single-core performance when you use the web: things like JavaScript processing, layout, etc. will bottleneck on one core and since developers are shipping more code this is probably the most noticeable difference. It's also a little hard to tell in some cases since there are many “native apps” which use an embedded web view for some of their UI.

This is important for developers to know about because if you use a recent iPhone your experience is not just fundamentally better than any Android user's but it's especially significant compared to the kinds of cheaper phones many people buy. Look at the chart here: a Galaxy S22 is comparable to the iPhone XS which shipped 4 years earlier but even the S22 towers over the Moto E30 & other budget phones.

https://infrequently.org/2022/12/performance-baseline-2023/#...

Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by SketchySeaBeast on Thursday February 09, 2023 @02:45PM (#34730171)
While I agree it's important for developers to know, I think that Ca.gov example would have been more compelling if we'd had side by sides between various systems - as it was it was incredibly slow, but that's an aberration, and it was a universal problem. Otherwise we have to once again resort to benchmarks. I've been happy with the experience on my last Android phone for 3 years now, another benchmark isn't swaying me, my phone is more than fast enough.
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by acdha on Thursday February 09, 2023 @03:13PM (#34730664)
Hey, if it works for you, that's great. My point is really just that there are still pretty common situations where CPU performance matters and so you really need to measure on the types of devices your users actually use. If you look at that and say it's fine, you don't need to change anything but I suspect a lot of developers would not be happy with the performance of their sites on, say, 3G or public library WiFi on a phone which was $200 when it came out multiple years ago. A fair amount of that isn't CPU-related but network transfer, but real testing will catch both of those.
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by ilyt on Thursday February 09, 2023 @02:45PM (#34730180)
My phone is aging One Plus 5T and so far I never felt even slight reason to change it. It is just plainly fast enough.

Only thing that would make extra performance matter are video games and I don't play those on phone.

Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by notshift on Thursday February 09, 2023 @03:41PM (#34731087)
I have a One Plus which is slightly newer than that (~4 years old). It's very slow. I suspect people with a sentiment like yours just don't care about small amounts of latency. I wish the screen was immediately and instantaneously responsive to all my actions, and I wish all the apps I opened would immediately be interactive as soon as they are visible.
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by stkdump on Thursday February 09, 2023 @03:07PM (#34730574)
I just switched from a OnePlus 5 to a 9 Pro a few weeks back, and it is a noticable improvement. But you are right, while I was on the 5 I thought performance isn't a problem.
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by hokkos on Thursday February 09, 2023 @03:55PM (#34731306)
I had one but the battery was dead and could't find a replacement. With a Pixel 7 Pro now I feel the speed difference.
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by powersnail on Thursday February 09, 2023 @03:04PM (#34730507)
> You care about single-core performance when you use the web:

Theoretically, I would care. But in practice, I just took out an old budget android phone, gave it a go at browsing the web (news, images, and videos), and it seemed not to be noticeably slower than my much newer and pricier iPhone.

Benchmarks would probably show a great difference between the two, but my eyes can't tell.

Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by acdha on Thursday February 09, 2023 @04:04PM (#34731433)
People's tolerance varies and so do the sites they visit – and things like news sites are a lot better than they used to be before Google started more aggressively including performance in their search ranking factors.

My interest in this topic is mostly the same as the author of the post I linked, namely making sure that developers test and measure on lower-end devices to make sure they're not building sites which exclude key demographics. For example, a government site really needs to work well on the kinds of phones seniors get under the FCC Lifeline program.

Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by powersnail on Thursday February 09, 2023 @06:02PM (#34732994)
I agree on the principle. Developers should care about low budget devices, and demographics—key or not—shouldn’t be excluded. The principle is sound.

But that is different from the observation of the beginning of this thread, which is that Geekbench scores don’t really reflect practical limitation of devices. A big difference in the score does not mean a noticeable difference in performance when doing everyday web browsing on the phone. An observation that my own experience echoes.

Even if I’m extra-tolerant (I don’t think I am), it would surprise me that a performance difference I can’t even notice is going to be so intolerable to another human being that they are excluded from using the website.

When it comes to governmental services on the internet, I think really the focus is on whether the site _works_ on all kinds of devices, which means whether the rendering and interactions are correct. Some can fail to render on a low budget phone, or if some button doesn’t work, etc. these are real problems but that is quite irrelevant to benchmarks.

Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by acdha on Friday February 10, 2023 @08:11AM (#34739196)
I definitely agree that the focus should be broader - most websites, for example, probably bottleneck on the network first.

The broader point wasn’t that you should buy an iPhone but simply that the reason to care about single core benchmarks is that browsers fit that profile. It’s still perfectly reasonable to conclude that’s good enough for the sites you use.

I also feel like there’s an interesting angle about ad blocking here since that probably matters more than multiple processor generations.

Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by kaba0 on Friday February 10, 2023 @01:39AM (#34736403)
Let’s check back a few years later, how will that phone stand up. More powerful hardware is also future-proofing the devices, which apple actually care about. Hopefully this will change as now even Samsung promises some 5 years of software updates, but previously you could almost throw out a perfectly fine android phone 2 years later..
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by pharmakom on Friday February 10, 2023 @03:18AM (#34737009)
Why do phones get slower at the same tasks over time? Maybe our perceptions change?
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by acdha on Friday February 10, 2023 @08:05AM (#34739122)
That’s part of it: when you got a new phone, you probably noticed it being faster than the old one but over time your expectations adjust.

One factor which used to be under appreciated was battery degradation prior to that whole “Batterygate” flap back in 2016 where a lot of people learned that iOS throttled processor performance when the battery could no longer supply enough voltage for peak performance. That’s a lot more visible now so it’s less of a surprise than it used to be.

Most of the problem is that developers aren’t focused only on performance, so as the baseline hardware capacity increases the apps will slowly start to use more since very few people are going to spend time on something which seems fast enough.

That doesn’t happen all at once but it adds up over the half decade a phone will last. If you bought a phone and never updated anything, its performance would seem far more consistent … at least if you could avoid getting malware installed.

That third point is why I shared the link above: a lot of developers upgrade more frequently than average people and that means that our instincts for what seems fast enough might be missing things with our apps. That usually doesn’t mean things are unusable but it’s still polite to use your work on, say, the phone a senior citizen gets subsidized to make sure that you’re comfortable with that being the public face of your work.

(Bandwidth usage is at least as important here, too: use your website on 3G or ask how much it’d cost to use on a metered plan)

Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by SketchySeaBeast on Friday February 10, 2023 @08:54AM (#34739595)
But you don't have to anymore. My S20 is from March of 2020 and it's still as fast as the day I got it. It's hitting EoL for support, but as you said if I bought a new S23 Samsung promises supported for 5 years, and I think it might actually make it that whole way without slowing down.
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by purpleblue on Thursday February 09, 2023 @03:12PM (#34730646)
I was using a 12 year old desktop for my main system at home until I recently and impulsively decided to upgrade. I don't notice any difference because a lot of what I do is web browsing. The only thing that was transformational was things like using Photoshop, gaming and any high-intensity applications, which are few and far between. Even using Excel was hardly noticeable.
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by basch on Thursday February 09, 2023 @03:55PM (#34731314)
Id rather the web have less javascript than my phone be faster.
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by acdha on Thursday February 09, 2023 @04:00PM (#34731374)
That is something Alex Russell, the author of that blog post, is trying to raise awareness of in the industry but changing the culture of web development is a lot harder than buying a different phone (in many cases that won't even cost you more money).
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by basch on Thursday February 09, 2023 @04:02PM (#34731410)
Fix it at the rendering level. My device should default to not rendering a website the way the developer asks it to, but the way my defaults are set. Load a minimum viable site, ask my permission to execute more.
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by mhio on Thursday February 09, 2023 @11:15PM (#34735546)
I think there is a general security and privacy argument for this type of setup as well.

As a web browser has become a general purpose VM, it has capabilities far surpassing what is needed at least 50% the time, I'd go as high as 90% of the time personally. Which is great that we have a magical run anything anywhere VM, but it's a double edge sword of the performance, security and privacy issues that come along with it.

If there was a well defined subset of functionality that browsers presented as the default "web enclave" and then opening up all the bells and whistles further was an opt in choice, a large chunk of those issues would go away. But that requires a bunch of people to agree on what that subset should include and the horror of trying to keep it updated over time. And that's _everyone_, including users putting up with "opting in" rather than everything just working.

I'm not sure I can see a subset of features becoming the default approach, at least until there is some horrible self propagating browser worm that impacts a large percentage of the world (or maybe by the 2nd or 3rd time, we will have had enough).

Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by kaba0 on Friday February 10, 2023 @01:41AM (#34736415)
How exactly would you decide what is minimum viable?

What about buying a ticket and it failing at the last step because your browser determined that js was unneeded?

Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by basch on Friday February 10, 2023 @09:45AM (#34740269)
Historically, browser vendors maintain per site settings of some sort. Whether that be Opera's Site Specific Patching or Brave.

Basically have to keep giant lists of what js actually enhances the people experience vs just being useful to the publisher.

Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by Tagbert on Friday February 10, 2023 @03:53PM (#34745689)
I find it is usually not so much about the JavaScript on a particular site for basic functions of that site but all of the other scripts and resources loaded by ads and promos. So many pop up videos stalking you as you try to browse the site.
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by SergeAx on Thursday February 09, 2023 @04:10PM (#34731507)
I am using Xiaomi Mi 8, it is four and a half years old now. I don't have visible problems with websites performance. The battery is quite degraded though:(
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by faeriechangling on Thursday February 09, 2023 @08:01PM (#34734187)
Yeah and the s23 has double the memory so it’s going to absolutely kick the crap out of the iPhone12 after it starts to swap your tabs into memory even accounting for the JVM.

It’s cool and all for Apple to have an edge in single core performance but it doesn’t matter all that much in the real world and the s23 is objectively the faster phone.

Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by acdha on Thursday February 09, 2023 @08:45PM (#34734567)
> the s23 has dramatically more memory so it’s going to absolutely kick the crap out of the iPhone12 after it starts to swap your tabs into memory.

Do you have any reproducible test results showing that or are you just asserting tribal loyalty? I jest, we all know the answer.

You might want to read up on how iOS and Android differ in key ways: native code versus JIT, garbage collection versus ARC, and all of the system level differences for how many things can run in the background as well as quickly apps can save and restore state - faster CPUs and SSDs allows iOS to be more aggressive there, too, and developers can tune more aggressively because they have fewer, more consistent configurations to support.

Also consider it from the perspective of the engineering trade offs that the manufacturers make. More RAM means lower battery life and a higher price, and consumers are also sensitive to both of those. Apple controls their stack so tightly that they designed a custom SoC and market-leading CPU, and they measure the user experience very closely since that’s a lot of what they’re selling — if there really was a gap, adding more RAM would be one of the easiest ways to close it. Similarly, Samsung wouldn’t make every phone they make have lower battery life and cost more if that only benefited a small percentage of users. They’re making different choices because they have different systems but both of them watch this stuff closely.

Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by kaba0 on Friday February 10, 2023 @01:44AM (#34736434)
While I agree with your overall points, you are wrong on the details: Android runs native code and ARC is just another form of GC (with less memory overhead, but also less throughput for what it matters. It is probably the better choice for mobile devices).

Apple hardware is just that much better, it is not about the software stack.

Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by acdha on Friday February 10, 2023 @07:05AM (#34738603)
Android does have native code support, but do non-games use it commonly? The Android reviews I've read tend to mention that being a game thing when talking about why it's important to have more RAM.

(And, yes, I should have said “Java's GC vs. ARC” since that tends to have higher peaks)

Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by kaba0 on Friday February 10, 2023 @10:57AM (#34741356)
Android’s ART used to be a completely AOT approach (that compiled to native machine code on the machine at install time), nowadays there is also a JIT compiler that shares profiling information across devices even.
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by acdha on Friday February 10, 2023 @12:30PM (#34742793)
Yeah, to be clear my point is not that one is better than the other but simply that you can’t directly compare RAM without adjusting for the fact that they have different designs.
Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by pjmlp on Friday February 10, 2023 @02:03AM (#34736568)
Android since version 5 AOT compiles the code, since version 7 it JITs first and then AOT compiles on idle, nowadays not only it JIT/AOT compiles it does so by using PGO metadata shared across devices via the PlayStore.

Reference counting is a GC algorithm.

Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by acdha on Friday February 10, 2023 @07:18AM (#34738698)
> Android since version 5 AOT compiles the code, since version 7 it JITs first and then AOT compiles on idle, nowadays not only it JIT/AOT compiles it does so by using PGO metadata shared across devices via the PlayStore.

Thanks, I knew that Android had native code support but I've always heard that described as something mostly used by games.

> Reference counting is a GC algorithm.

Yes, I should have been pedantic and written “Java's GC” since the point was that historically it's tended to trade RAM for performance. The classic complaint I've heard from our mobile developers was that Objective-C forced you to focus more on memory management.

Re:Apple’s 2½ year old iPhone 12 is 6% faster than the new S... by kaba0 on Friday February 10, 2023 @01:42AM (#34736422)
Android doesn’t run “the JVM”.