Win a copy of TDD for a Shopping Website LiveProject this week in the Testing forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
Bartenders:
  • Piet Souris
  • Himai Minh

"Knowing" isn't the same as measuring

 
Saloon Keeper
Posts: 25463
180
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
We often advise people in this forum not to waste time in prematurely optimizing the parts of their apps that they "know" need optimizing. Here's a real-world example of why:

http://www.wired.com/epicenter/2011/03/android-iphone-web/

 
Rancher
Posts: 43027
76
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The methodology doesn't convince me. Using a mix of handsets -and not even saying which ones in the case of iOS- just muddles the numbers.

The Nexus S and the Galaxy S have 1 GHz ARM Cortex A8 CPUs.

iPhone 4.2 and 4.3 are not actual devices but OS versions that run on a) the iPhone 3 on a 412 MHz ARM 1176, b) the iPhone 3GS on a 600 MHz ARM Cortex-A8, and c) the iPhone 4 on a 800 MHz ARM Cortex-A8 (http://en.wikipedia.org/wiki/IPhone#Model_Comparison).

So at least 25% difference (800MHz vs. 1GHz) can be chalked up to the CPU, if not 66% (600MHz vs. 1GHz), assuming that the iPhone 3 wasn't actually used. The latter case would negate the "findings" of this comparison. So while a comparison of a single device running iOS vs. a single device running Android might make sense, this test says nothing about iOS performance vs. Android performance.
 
Tim Holloway
Saloon Keeper
Posts: 25463
180
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think rather than the merits of hardware or OS, the paragraph of note in this article is the final one. And, there's at least some reason to believe that the real bottleneck wasn't the devices, but the efficiency of the pipes feeding the devices.

My own experience, BTW, has been that the overhead of downloading an extensive AJAX support package can easily dwarf everything else. In my case, simply bundling the AJAX libraries into a single unit and enabling client-side caching meant a full order of magnitude in speed improvement.
 
There are 29 Knuts in one Sickle, and 17 Sickles make up a Galleon. 42 tiny ads in a knut:
free, earth-friendly heat - a kickstarter for putting coin in your pocket while saving the earth
https://coderanch.com/t/751654/free-earth-friendly-heat-kickstarter
reply
    Bookmark Topic Watch Topic
  • New Topic