An in-memory DB is held 100% in the cache (there is no backing store), so I believe it ignores this number and is allowed to grow up to the maximum DB size. The cache does not hold duplicate copies of pages held else-where in memory.
-j On Mar 17, 2016, at 8:17 AM, Michele Pradella <michele.pradella at selea.com> wrote: > I check the default cache_size of a In-Memory DB and it's 2000 > Do you think for that kind of DB I can put cache_size to 0 like default for > TEMP DB? or you think it's better leave 2000? > Just wandering if it's correct to have ram cache of a In-Memory DB > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Intelligence is like underwear: it is important that you have it, but showing it to the wrong people has the tendency to make them feel uncomfortable." -- Angela Johnson
