On a previous generation of smartphone hardware, a 1msec difference in
db access on an UML [User Mode Linux] emulator turned into a whole
second difference on a Zylonite board. So a 120x difference between
desktop hardware with a hard disk and an Android device with flash
memory doesn't seem at
On Dec 9, 4:40 pm, Doug Gordon gordo...@gmail.com wrote:
You really have to optimize everything.
Welcome to limited device development. Your phone is not your
desktop. :-)
Oh, and sdcards are really quite slow for hosting big sqlite
databases. The I/O alone can kill performance if you're not
One approach, depending on your application logic, is to access the
cursor for the first time inside queryDataBase and run the query in an
AsyncTask. You may be able to hide the delay from the user by putting
up a little animation while your app launches.
--
You received this message because you
I found that I had to significantly restructure both my database
design and query sequences in order to get satisfactory performance on
an actual phone. There are big differences between Android and a PC,
such as lack of gobs of real (and virtual!) memory. You don't have a
database server that can
4 matches
Mail list logo
