I've done some speed tests and here are my findings (disclaimer, my test runs for just over a minute so timings are not extremely reliable):
1. Reusing SQL params object array - negligible speed improvement - test too short to say anything with confidence 2. Using prepared statements rather then execSQL() - 20% faster (BTW - there is no need to use an array at all here) 3. Removing log statements - 100% faster (whoops!) 4. Inserting 10 times as many rows (speed (per row average) stays about the same) 5. Running on the Hero instead of the emulator - 400%-500% faster There are quite a few other objects being created within the main loop so maybe there are some speed improvements to be made. However, after experimenting with point 1, I don't expect these to be as dramatic as points 2,3 and 5. So, assuming I stick with the database approach, the options are: 1. 15MB database download 2. 2.5MB download then perform a one-hour initialisation step I can see that second option is a bit weird... --~--~---------~--~----~------------~-------~--~----~ 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 android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
