Yes: Inserts wrapped in transactions 10,000 at a shot. Tried pragma synchronous=OFF
And 3 different threadsafe compilations for sqlite: # define SQLITE_THREADSAFE 0 /* IMP: R-07272-22309 */ # define SQLITE_THREADSAFE 1 /* IMP: R-07272-22309 */ # define SQLITE_THREADSAFE 2 /* IMP: R-07272-22309 */ All other settings are default. all 6 versions peg the cpu when i run concurrent instances => # of cores. Bare Metal wrote to local disk. Will test writing to same share next. VM's write to NAS (Windows server 2008 mapped network drive). <<< Response to: >>> Have you run your bare metal test using the same share? And have you tried "pragma synchronous=OFF" ?? And I assume you are using transactions? Have you profiled your app to see where it's spinning? Probably trying to get the lock on the share. What flags did you use to comiple the sqlite library? In particular for threadsafe? Michael D. Black Senior Scientist Advanced Analytics Directorate Advanced GEOINT Solutions Operating Unit Northrop Grumman Information Systems _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
