Re: [sqlite] Regarding CoC

e staff, > and everybody approved. > > -- > D. Richard Hipp > d...@sqlite.org > ___ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Massively multithreaded SQLite queries

ers@mailinglists.sqlite.org> Subject: Re: [sqlite] Massively multithreaded SQLite queries Hi Andrew, This is a great use case for SQLite. Did you have to use any special flags or settings for SQLite to achieve this e.g. cache size, page size Read only etc? Thanks, Vikas > On Jun 7, 2017, at 10:07 AM, And

Re: [sqlite] Massively multithreaded SQLite queries

: Andrew Brown Sent: Friday, March 3, 2017 12:14 PM To: 'sqlite-users@mailinglists.sqlite.org' <sqlite-users@mailinglists.sqlite.org> Subject: Massively multithreaded SQLite queries Hello, Based on my reading of the documentation it seems like SQLite is a great candidate for cases where yo

Re: [sqlite] Massively multithreaded SQLite queries

Now this is a interesting question. As it happens I /am/ blindly assuming the os would schedule it properly. I will look at my options this evening and see about addressing that. On Mar 3, 2017 4:52 PM, Keith Medcalf wrote: No, the good rule of thumb is to allocate one

Re: [sqlite] Massively multithreaded SQLite queries

Yes, each thread has its own connection. On Mar 3, 2017 4:45 PM, Keith Medcalf <kmedc...@dessus.com> wrote: Does each thread have its own connection? > -Original Message- > From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] > On Behalf Of Andr

Re: [sqlite] Massively multithreaded SQLite queries

So in this case I'm running on a 72 core machine. Also the databases have one table in them each... The goal here is to bring all the cores to bear on the many queries - each grabbing the next query to be run and running it, until finally there are no more chunks to run. Then within my own

Re: [sqlite] Massively multithreaded SQLite queries

Well, in the situation I'm working with, my API is constructing 1835 small SQL jobs to be run, and then passing them off to a structure in which 72 threads are running, each with their own db connection (I assume that's what you mean by a database handle, a DB connection, but please, correct me

[sqlite] Massively multithreaded SQLite queries

tips to handle massively multithreaded side by side chunked queries on the same database? Thank you in advance, Andrew Brown ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite