On 28 Mar 2013, at 12:43pm, Jeff Archer <jsarc...@nanotronicsimaging.com> wrote:
> But the question is: Why? Without journaling only half as > much writing to disk should occur so why would it take longer? But you are still doing 5764 sets of writing. One per transaction (which, since you are not defining transactions yourself is actually one per SQL command). When you define a single transaction you're actually doing just one write: the only thing that requires a write to disk is your COMMIT command. So naturally doing one write takes less time than doing 5764 write. Journalling isn't relevant to the above. Journals just add extra to the above, no matter whether you're doing a single transaction or many transactions. But they don't make anything like as much difference as the difference between 1 transaction and 5764 transactions. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
