I have not discovered how to find internal memory throughput usage in OSX, and I agree that something is not allowing the system from maxing out the CPU or I/O.
Also, the unix time command does reveal that part of the program’s running time is spent in the system, though I do not know yet how it factors into my user’s perceived running time. On your advice, I have compiled SQLite (the amalgamation) with SQLITE_THREADSAFE = 0, and it does seem to have a very minor benefit: 2x100K sequences 1s 0.96s 200K in 1.98s = 101010 ips (inserts per second) 2x500K sequences 4.67s 4.69s 1M in 9.47s = 105596 ips With SQLITE_THREADSAFE = 1: 2x100K sequences 1.04s 1.02s 200K in 2.08s = 96153 ips 2x500K sequences 5.01s 5.02s 1M in 10.17s = 98328 ips It was already using PRAGMA locking_mode=EXCLUSIVE; it did not appear to make a noticeable difference. On Apr 2, 2014, at 5:30 PM, Keith Medcalf <kmedc...@dessus.com> wrote: > internal _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
