On Mon, Mar 6, 2017 at 8:40 PM, Jens Alfke <j...@mooseyard.com> wrote:
> > > On Mar 6, 2017, at 7:57 PM, J Decker <d3c...@gmail.com> wrote: > > > > Pretty silly since it is sqlite, and a mmap'ed database is pretty much > > sync.... > > Not really. The data still has to be paged in off the disk, which can take > arbitrarily long (seconds, if the system is under heavy load), and complex > queries can end up doing a lot of CPU-intensive extra work that takes time > to run. Although yes, if you’re not super concerned about performance, it’s > overkill. > > (I spent a year or two once working on Chrome, which has a rule that no > synchronous I/O may take place on the UI thread, because it can impair > responsiveness. That applies to database queries too.) > yup; caveat developor. and if you are concerned than there's other things at play than a job doing what it needs to do; and doing nothing otherwise. Some systems will even spin-lock for you :) give me enough rope and I can play cats cradle with it. not all things that happen synchronously are because a user did it; and things that aren't shouldn't have to pretend they were. > > —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
