Hello, I'm using SQLite extensively (thanks for the great tool!) in an application where it's almost exclusively accessed on a single thread. I have found that the SQLITE_THREADSAFE=0 compile-time option gives us a 3% improvement in overall performance by removing mutex overhead.
However: there are 2 places where I very rarely access sqlite from a separate thread. One of these is a call to sqlite3_interrupt() which, on inspection of the source, seems like it is probably safe to access from multiple threads. However I also call sqlite3_release_memory() on receiving a memory warning from the system. That one looks much less safe to call off-thread. It seems like a shame to incur a 3% penalty across the board when I'm only very rarely accessing off another thread. Are there any other options here? Regards, Xavier Snelgrove -- Xavier Snelgrove Cofounder & CTO, Whirlscape Inc. http://whirlscape.com xavier at whirlscape.com
