Thank you Smith. The table is preseted with some data in my Android system. And I guess my APPLICATION is more like a SERVICE which will be started at system boot time and speed issue happens at the time. According to the some other reasons, I have to use wal+normal journal and sync mode.
>3. Start a transaction and hold the DB read locks for the duration of your application (again, if it won't need writing) I only have several single SELECT at boot time and I guess it is not necessary to use TRANSACTION? And there are still some write ops in my service. >4. Ensure there are no other time-consuming bits of code in the sqlite api RESET()-STEP() loop. I think I only use sqlite api in some normal ways. And I do not know more details about what happens during the boot time. -- Sent from: http://sqlite.1065341.n5.nabble.com/ _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
