On Mar 3, 2017, at 5:51 PM, Keith Medcalf <kmedc...@dessus.com> wrote: > > No, the good rule of thumb is to allocate one thread per CPU.
It depends on the workload. Parallel make (e.g. “make -jN” in GNU make) typically improves in speed past N=core count to about 1.5x the core count. SQLite seems like a similar kind of workload: lots of CPU *and* disk I/O, so that you need a bit of oversubscription to keep all the cores busy, because some threads/processes will be stalled on I/O. Not that any of this is relevant at the current point, since the OP is currently neither I/O bound nor CPU-bound, but lock-bound. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
