Andrew Brown wrote: > I find that we spend a lot of time in __raw_spin_lock
Please try to find out (stack trace, etc.) which particular resource is protected by that lock. If, for example, this would happen to be file lock operations, then you would need to use fewer transactions (by wrapping multiple queries into a single transaction). Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
