News for hackers. Stuff that matters.
Re:Hold the Phone: A Big-Data Conundrum by staunch on Saturday July 26, 2014 @09:09PM (#8091558)
It's incredible the answers non-technical people come up with to explain technical things. The reason RAGE takes more CPU/GPU power than Quake III is because it does more. Not because John Carmack wants your gaming PC to feel slow. The same is true of Apple when they ship a new app that does more.

Samsung is just a generic hardware vendor for Android PCs, like Dell. They don't create operating systems or apps.

It probably also has a psychological component. Just seeing a new generation gaming PC makes mine feel slow.

Re:Hold the Phone: A Big-Data Conundrum by kibibu on Saturday July 26, 2014 @09:17PM (#8091576)
RAGE is doing substantially more of everything than Quake III, so I think the difference between Quake III from 1999 and RAGE from 2011 is a poor parallel to draw with iOS6 to iOS7.

A better comparison is that Windows 8 runs faster than Windows 7, which in turn ran faster than Vista. Linux kernels continues to improve in performance too.

Re:Hold the Phone: A Big-Data Conundrum by drewcrawford on Saturday July 26, 2014 @11:16PM (#8091832)
I think people substantially underestimate how hard the iOS GUI pushes the performance wall, from one release to the next.

There was a talk at WWDC this year (session 419, if you want to watch it) that goes into some detail about how the blur effects on e.g. the lock screen, notification center, control center, toolbars, etc. work.

You can watch the talk for the details, but as a practical matter several of these effects involve seven (!) full GPU passes, just for these effects alone, let alone whatever UI is under or over them. And not even the very latest-gen devices can do it consistently full-screen at 60fps. iOS displays motion underneath blur effects in very small areas (e.g. a toolbar) on new devices but if you think about it, you never see motion underneath, say, the lock screen. The reason is that not even the latest iPad Air has the GPU to apply some fullscreen blurs in enough time to meet the draw deadline.

This actually surprises a lot of people--I can't count the number of designs I've gotten where some designer has made a large blurred UI element and expects something to move underneath it. Which, depending on the size of the element and the target hardware you can sometimes get away with, but you are in for quite the lengthy performance test, and a complicated spectrum of fallbacks for all the devices that just aren't fast enough.

And that's just one blur effect. You take a look at all the other "new" iOS things that are less visible, like the endless stream of new background technologies (background fetch, silent push, NSURLSession, multi-app audio routing, various iCloud syncing stuff) the new bluetooth stuff (iBeacon, HomeKit, Multipeer), turning WebKit into an LLVM compiler, and all the other things that are going on in iOS it really is "doing more of everything". I remember a time when iOS was basically just a few OS processes plus 1 active app, and as we speak ps on my phone lists 87 processes.

Re:Hold the Phone: A Big-Data Conundrum by JonnieCache on Sunday July 27, 2014 @04:32AM (#8092269)
Does that graphical stuff not destroy battery life?
Re:Hold the Phone: A Big-Data Conundrum by VLM on Sunday July 27, 2014 @08:35AM (#8092578)
Yes. The UI equivalent of automotive tail fins is expensive. That's the sole point of it.

At some point in the "near" future it'll be energetically a net positive to snap a pix on the cam, analyze the eye pupils and accelerometers and recent eyeball movements, and if you're not looking at that part of the screen, its not going to waste energy displaying it. Could even see this happening with backlighting. Watching other people use their phones is likely to get very distracting for 3rd parties.

Re:Hold the Phone: A Big-Data Conundrum by kibibu on Sunday July 27, 2014 @09:00AM (#8092617)
I hadn't really considered foveated rendering on mobile, but that's a very interesting idea.
Re:Hold the Phone: A Big-Data Conundrum by bjustin on Saturday July 26, 2014 @10:09PM (#8091722)
You missed an easy Windows comparison by focusing on Windows 7 and 8: Vista brought big graphics changes but ran poorly on a lot of existing hardware, similarly to iOS 7 on the iPhone 4.
Re:Hold the Phone: A Big-Data Conundrum by Zigurd on Saturday July 26, 2014 @10:16PM (#8091734)
> The same is true of Apple when they ship a new app that does more.

There are often better explanations. GMail is fast. All the time. No matter how much mail you have. That's because it runs from a local database and all server interaction is abstracted behind sync and local accesses to data. Google Play is slow because it is a REST app with a native app veneer. It's harder to make an app like Google Play use sync'ed databases. So sometimes it does puzzling things like taking tens of seconds to go to the next track even when you are shuffling only your downloaded music.

Fast apps can "do more" and remain fast. Slow apps are slow for architectural and algorithmic reasons rather than because they "do more."

Re:Hold the Phone: A Big-Data Conundrum by traek on Saturday July 26, 2014 @11:24PM (#8091856)
> GMail is fast. All the time. No matter how much mail you have. That's because it runs from a local database and all server interaction is abstracted behind sync and local accesses to data.

I don't know about Android, but on iOS, the Gmail app is much slower to launch and navigate than the stock mail app. I think that, on launch, the Gmail app makes some requests before showing you any of even your locally cached data, which always struck me as poor design.

Re:Hold the Phone: A Big-Data Conundrum by rjvir on Saturday July 26, 2014 @11:37PM (#8091884)
That's also how the GMail website still acts, which confuses me as well. Why can Facebook load a complex web app instantly while GMail still shows a loading bar on launch?
Re:Hold the Phone: A Big-Data Conundrum by dekhn on Saturday July 26, 2014 @11:56PM (#8091909)
actually, when you load facebook, it shows an interstitial which looks like a page of posts, but is really just a bunch of blocks carefully arranged, and it has nothing to do with the final load page.
Re:Hold the Phone: A Big-Data Conundrum by dekhn on Monday July 28, 2014 @02:07PM (#8098392)
Huh. I checked back a few times. It looks like facebook loads an interstitial with boxes, that actually corresponds to the layout of the page, but not the content. This includes sentence layout (the boxes cover the area that gets replaced with text, similar for images). Now I'm curious what's going on.
Re:Hold the Phone: A Big-Data Conundrum by walterbell on Saturday July 26, 2014 @10:37PM (#8091775)
Is there a fixed limit to the size of the local GMail cache?
Re:Hold the Phone: A Big-Data Conundrum by TooSmugToFail on Saturday July 26, 2014 @10:06PM (#8091717)
What exactly got that better from iOS6 to iOS7 that justifies the evident performance drop?

I think the google trends graph for "iphone slow" search phrase says all that there's to say about this phenomenon.

Re:Hold the Phone: A Big-Data Conundrum by dajohnson89 on Sunday July 27, 2014 @06:10AM (#8092381)
When a new iphone comes out, owners of old iphones could feel that their phones are inadequate, and are searching for "is the iphone [n-1] slow?".

Also, with each iphone generally comes a new ios version, which is more or less written for the specs of the newest phone. That being said, this post is being typed from an iphone 4s I've owned for two years. I've never had any complaints about performance. Never noticed a slowdown.

Re:Hold the Phone: A Big-Data Conundrum by paul_f on Sunday July 27, 2014 @07:39AM (#8092496)
The article clearly says this is not the case. The searches for "iPhone slow" come when the new version of iOS is released, not when it is announced.

Second, we do studies like this so that one data point (yours) is not used to make general understanding.

Re:Hold the Phone: A Big-Data Conundrum by jnbiche on Saturday July 26, 2014 @11:31PM (#8091877)
Re:Hold the Phone: A Big-Data Conundrum by TobbenTM on Saturday July 26, 2014 @09:34PM (#8091618)
Re: samsung: while they don't make the operating system, they do bundle apps and sometimes even their own filesystem (Galaxy S1). This particular filesystem made android slow.
Re:Hold the Phone: A Big-Data Conundrum by bookwormAT on Sunday July 27, 2014 @06:06AM (#8092374)
You can argue that this means Samsung does indeed make their own operating system.

The term OS, as it is used by media and most people today, is the software that is installed on the device before you install any additional apps to it. E.g the "App Store" is considered a part of iOS, the Internet Explorer as part of Windows, and the Homescreen and Dock of Max OSX is considered a part of OS X.

Since a Galaxy and a HTC One ship with different Applications, a different user interface and other key software components (you mentioned the filesystem on the Galaxy S), Android is less an operating system but but the cross platform foundation that most operating systems are based on today.

Re:Hold the Phone: A Big-Data Conundrum by joshlegs on Saturday July 26, 2014 @09:53PM (#8091676)
> The same is true of Apple when they ship a new app that does more.

Presumably youre implying here that people who complain about their iphone being slow are the people who upgraded their OS while keeping their old hardware?

Re:Hold the Phone: A Big-Data Conundrum by nardi on Sunday July 27, 2014 @03:56AM (#8092244)
That is what the article is about.