John Stanton <[EMAIL PROTECTED]> wrote: > I haven't looked at how Sqlite manages its cache, so my suggestion may > be irrelevant but we have had success in such a cacheing situation by > crafting the cache with pages organized in most recently used order. > The least recently used pages is the one replaced when there is no cache > hit. When a page is accessed it is linked to the most recently used > position. > > B-Tree interior nodes stay in cache. > > Another improvement was achieved by implementing enhanced B-Trees which > try to merge adjacent nodes before splitting or deleting a node. This > keeps the trees flatter and less checkerboarded and cuts back on > expensive splits when inserting randomly ordered keys. >
SQLite already uses an LRU cache. And, besides, I think the problem is in the operating system file cache, not in SQLite's secondary cache. The correction solution, I believe, is the 4th bullet under "Code" on http://www.sqlite.org/cvstrac/wiki?p=ToDo -- D. Richard Hipp <[EMAIL PROTECTED]> ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
