"P Kishor" <[EMAIL PROTECTED]> wrote: > Richard, > > On 3/22/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > ... > > The problem is that your working set is bigger than your cache > > which is causing thrashing. I suggest a solution like this: > > > > Add entries to table ONE until the table and its unique index get > > so big that they no longer fit in cache all at once. > > What is this "cache" you talk about? Is this the hard disk cache, or > some kind of OS-level cache, or a SQLite level cache?
All of the above. > How can I find > the size of this, and is this cache user-adjustable? If yes, how? > On Linux, the "top" command will show you how much OS disk cache you are currently using. The hard disk cache is usually small enough that it can be neglected. The OS cache is also usually much larger than SQLite's own internal cache. You might run an experiment where you start inserting and timing each insert, then switch to a different table when the insert speed drops below a threshold. -- D. Richard Hipp <[EMAIL PROTECTED]> ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
