Hi Simon, Well in my case the linked threadsafe.html documentation won't be helpful, because it looks like at runtime I can only downgrade as far as multi-thread mode, not single-thread mode, and it's in single-thread mode where I'm really seeing a significant performance advantage.
I think the performance improvement is significant enough that I'll forgo the off-thread calls to sqlite3_release_memory. That was only rarely used anyway. I'll add an on-thread memory release call, and hope it triggers in time. And I'll just trust that sqlite3_interrupt is safe to use, based on my reading of the source. Xavier On Sat, Mar 14, 2015 at 8:27 PM, Simon Slavin <slavins at bigfraud.org> wrote: > > On 13 Mar 2015, at 6:26pm, Xavier Snelgrove <xavier at whirlscape.com> wrote: > > > Are there any other options here? > > Does the last section of > > <https://www.sqlite.org/threadsafe.html> > > help you in your situation ? Alternatively you might be able to use > > <https://www.sqlite.org/c3ref/mutex_alloc.html> > > to manually maintain a mutex. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > -- Xavier Snelgrove Cofounder & CTO, Whirlscape Inc. http://whirlscape.com 1 (416) 876-9427 xavier at whirlscape.com
