I turned journalling off in my test program and sqlite3 is running about 3000/inserts per second right now at around 6M records. Lousy performance compared to WAL mode. journal=memory behaved the same way.
Journaling off might work if you don't have any indexes. Taking the primary key off of my test program cranks up to 374,000 inserts/sec average over 50M records with journal_mode=WAL - pretty decent throughput I'd say. Interestingly enough sqlite4 is slower in that case (without the random primary key)....running around 80,000 inserts/sec So sqlite4 is faster when inserting random numbers in the index but slower when not (i.e. only the rowid index). -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Roger Binns Sent: Monday, December 31, 2012 1:59 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] 1.1GB database - 7.8 million records -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 31/12/12 10:35, Michael Black wrote: > One transaction like you did is best. > > I recently ran a test which ran pretty well with a commit every 1M > records. Doing every 100,000 records slowed things down dramatically. If you are creating the initial database then you can turn journalling etc off until the database, indices etc are fully created. This will get you a little more speed too. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlDh7mkACgkQmOOfHg372QR/dwCfVhcMaYJIr6pTFKsL1LbaFiVJ xk8An3lyoOv/LLmi9lWh8ZFEFJdCGfZO =ie9C -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
