> On Oct 7, 2016, at 1:45 PM, Joe Mistachkin <sql...@mistachkin.com> wrote: > > Have you tried using the URI "file::memory:?cache=shared”
Shared cache will definitely help when using multiple read-only connections, but I have a feeling memory-mapping would help even more since it would hopefully eliminate redundant memcpy calls between the database and the “file” cache. Daniel, try using “pragma mmap_size=N” where N is basically the minimum of the size of the database file and the amount of free RAM. > How can we allow many reader threads on an in memory, write once read many > times database and achieve multi-core performance? This part’s easy: just open a database connection per thread. Using the shared-cache mode as above means the threads won’t each allocate their own cache, which will save memory and improve locality of reference. —Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
