Select your localized edition:

Close ×

More Ways to Connect

Discover one of our 28 local entrepreneurial communities »

Be the first to know as we launch in new countries and markets around the globe.

Interested in bringing MIT Technology Review to your local market?

MIT Technology ReviewMIT Technology Review - logo


Unsupported browser: Your browser does not meet modern web standards. See how it scores »

{ action.text }

The problem, the researchers say, is partly the way that nonvolatile memory used inside phones and memory cards works. Product specifications suggest these chips should be able to read and write data faster than processors or wireless data links can serve it up, but in practice, they can’t. This is because benchmarks used to categorize memory are for reading or writing bits of data on a disk in sequence, but many of the popular apps in reality access bits in a less ordered way. That shortcoming was shown to be magnified by the way that many of the apps studied used data management code that relies heavily on random data access.

“Random write performance is orders of magnitude worse for mobile device storage,” and slower than a typical 3G network, said Agrawal. “Storage performance has clearly not kept pace with the improvements in the network.”

The NEC researchers tested a handful of strategies that could limit the chokehold of data storage on app performance. Facebook became four times faster when they forced it to use a different system of data caching, for example. That shows that design choices that app developers make can mitigate the data storage bottleneck, although removing that bottleneck would require changes to mobile operating systems and hardware.

Agrawal told Technology Review that he didn’t know how Apple’s iPhone might perform in similar tests. Apple devices use only internal storage, and their technology is similar to that used by Android devices. However, Apple’s iOS operating system and apps built for it store data in different ways.

After Agrawal’s presentation, Eno Thereska of Microsoft Research suggested that the results need to be validated with tests involving real users, to see if they notice the performance limits uncovered. He questioned whether these limits really even mattered. “I can only read a webpage so fast,” he said, “and have to admit I’m pretty satisfied with mobile apps. What is users’ perception of these experiences?”

Agrawal says his group has not yet tested whether users notice memory bottlenecks, but notes that most of their tests replicated how people use their apps. For example, for Google Maps, they timed how long it took to get results after “find directions” was tapped. Agrawal says he is confident that people could tell the difference and do find limitations imposed by memory frustrating. “Why would anyone want to see a 20-second wait if they can get away with five seconds?”

4 comments. Share your thoughts »

Tagged: Computing, smart phones, mobile applications, consumer electronics, Android devices

Reprints and Permissions | Send feedback to the editor

From the Archives


Introducing MIT Technology Review Insider.

Already a Magazine subscriber?

You're automatically an Insider. It's easy to activate or upgrade your account.

Activate Your Account

Become an Insider

It's the new way to subscribe. Get even more of the tech news, research, and discoveries you crave.

Sign Up

Learn More

Find out why MIT Technology Review Insider is for you and explore your options.

Show Me