You must never have used a Microsoft Operating system ... > -----Original Message----- > From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] > On Behalf Of Deon Brewis > Sent: Saturday, 4 March, 2017 00:33 > To: SQLite mailing list > Subject: Re: [sqlite] Massively multithreaded SQLite queries > > Can you give an example of an Intel Processor SKU with half-assed cores? > > There's HyperThreading of course, but I don't think anybody has ever > considered HyperThreading to be separate cores. > > - Deon > > -----Original Message----- > From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] > On Behalf Of Keith Medcalf > Sent: Friday, March 3, 2017 4:52 PM > To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> > Subject: Re: [sqlite] Massively multithreaded SQLite queries > > > No, the good rule of thumb is to allocate one thread per CPU. Depending > on the particular multi-core CPU you "may" be able to use all the cores > simultaneously but in many cases diminishing returns will set in long > before you can execute one thread per core. If this is an Intel processor > that claims it has more than one thread per core be *extremely* careful as > that will give you one thread and one half-assed thread per core. > Sometimes, half-assed cores are presented as real cores when they lack a > separate execution unit. Be vary wary. > > I presume you are forcing separate threads to separate cores by setting > processor affinity on the threads and not just blindly hoping that the OS > scheduler does "the right thing"? > > > -----Original Message----- > > From: sqlite-users > > [mailto:sqlite-users-boun...@mailinglists.sqlite.org] > > On Behalf Of Jens Alfke > > Sent: Friday, 3 March, 2017 17:19 > > To: SQLite mailing list > > Subject: Re: [sqlite] Massively multithreaded SQLite queries > > > > > > > On Mar 3, 2017, at 3:51 PM, Simon Slavin <slav...@bigfraud.org> wrote: > > > > > > Then mess with the '5' until you find a good value. > > > > A common rule of thumb with thread pools is to allocate one thread per > > CPU core. > > > > —Jens > > _______________________________________________ > > sqlite-users mailing list > > sqlite-users@mailinglists.sqlite.org > > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
