On Tue, Aug 31, 2010 at 4:11 AM, Fabrizio Giudici
<[email protected]> wrote:
> So I
> supposed to be very safe in that area and I'm disappointed to discover
> that it was a false sense of safety. What am I possibly missing?
Well, that's difficult to answer in the abstract.
The two most variable performance things I can think of in Android are
network I/O operations and flash writes. The former is fairly obvious,
and we've been recommending network I/O be done in an AsyncTask,
IntentService, or background thread for some time.
The flash write scenario was new to me. Brad Fitzpatrick's
presentation at Google I|O 2010 ("Writing zippy Android apps", or
something like that) was a bit of an eye-opener. I had not realized
exactly how slow a flash write could be -- 1 byte in 200ms has been
seen, though normally it's tons faster. The speed will vary widely,
based on hardware capabilities, how much of the flash filesystem is in
use, wear-leveling status, and a host of other criteria. And, the
emulator won't emulate this, since the emulator's write speeds are
that of the host PC, typically on a hard drive or SSD-caliber flash.
Of course, there's always the possibility that the interference is
from something else on this person's phone.
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy
Android Development Wiki: http://wiki.andmob.org
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en