Depends on access type. If accessing sequentially, paging would be minimal, that is, you would process the "segment" that fits into memory, then page in another "segment" and process that, etc., etc.
However completely random hits on the database could result in heavy paging, unless it were possible to do the random accesses in a "sorted" manner. For example, input transactions sorted by the same key that you are accessing by. --- On Tue, 4/19/11, jeff archer <jarch...@yahoo.com> wrote: > From: jeff archer <jarch...@yahoo.com> > Subject: [sqlite] What happens if you insert more than your RAM > To: "SQLite-user.org" <sqlite-users@sqlite.org> > Date: Tuesday, April 19, 2011, 2:29 PM > Wouldn't it page to disk, thrash and > be very slow first? > > >On Mon, 18 Apr 2011 09:46:44 -0400, Pavel Ivanov <paiva...@gmail.com> > wrote: > >You won't be able to insert. The statement will fail. > > > >On Mon, Apr 18, 2011 at 9:44 AM, Adam DeVita <adev...@verifeye.com> > wrote: > >> Good day, > >> > >> What happens if you insert more than your RAM size > into an in memory > >> database? > >> (I'm particularly interested in the Windows > context). > >> > Jeff Archer > Nanotronics Imaging > jsarc...@nanotronicsimaging.com > <330>819.4615 > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
