-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nikolaus Rath wrote: > Is it normal that UPDATE still takes more than 11 times as much time as > SELECT, or should I be able to get better performance?
The UPDATE time also includes the time waiting to acquire file locks. If you have concurrent activity it could take a while. If you want to break out the lock time then restructure your sql to be: BEGIN IMMEDIATE; UPDATE ... ; COMMIT The BEGIN will then show up in apswtrace separately as the transaction wait time. Also note that these times are wall clock times so heavy threading could cause a lot of variance. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqCOIAACgkQmOOfHg372QSWYgCfVRDkPdWcjJooIrUjsIM2iLLw bWQAnjC2SDgdtE87DcMbjXQjRN2F38fU =lLYM -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
