> On Jan 4, 2018, at 6:29 PM, Peter Da Silva <peter.dasi...@flightaware.com> > wrote: > > Since you're I/O bound on socket connections, and not CPU or database bound, > you might want to just have one database thread that communicates using > native inter-thread messaging to pass out work and accept responses from the > worker threads.
+1. Also, this will make it easy to batch multiple updates into a single transaction, which greatly improves write performance. —Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
