On 19 Jan 2014, at 2:00pm, Mario M. Westphal <m...@mwlabs.de> wrote:
> I logged the execution times of various operations in this phase to a text > file. Everything was fast, the processing, the INSERTs etc. > But COMMIT operations sometimes took 20s, then 0.2s, then again 10s. That's > the time SQLite spends in the execute call with "COMMIT". First, I want to check that you've read <http://sqlite.org/faq.html#q6> I can't answer your question but only a big UPDATE or DELETE would legitimately take 20s. If you're seeing INSERT times of 10s or 20s then you're seeing the result of two threads clashing over database access. One thread has to back off and wait for the other to finish, and the retry times eventually reach 10s and 20s before they get so long SQLite gives up and returns an error. So you're not seeing a process take 20s to do useful stuff, you're seeing one thread keep the database busy -- so busy that it's always busy when the other thread tries to write to it. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
