Sorry, forgot to remove tracing. :( Without it, it's only about 300ms for querying. That's at least comparable to other java code. Probably sqlite does't like complex queryes, but there are ways to deal with that...
On Apr 16, 10:11 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Digit wrote: > > I think 63 ms == 0.063 s, so the difference is about 120:1 which really > > looks a bit surprising here, even taking the ARM emulation into account. > > > can you post a small code snippet (and/or even an example database file) to > > duplicate this ? > > Here: > > package sqlite.test; > > import java.io.File; > import java.io.IOException; > import java.util.Date; > > ....... > } > > Output was > Queried in 59 ms > First next in 314 ms > Done in 6930 ms > = 20568 > > That's in debug, in run that was 41, 204, 4104, (and 20036:) ) > > Traceview is corrupt. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
