On Fri, 13 Jul 2012 21:40:19 -0700, Udi Karni <uka...@gmail.com> wrote:
>It very easily handles billion row/100GB tables - multi-table joins, etc. - >it just chugs for a while because it's single threaded, and will gobble up >memory and swap - but it gets the job done. If SQLite memory usage causes your system to swap, your sqlite cache might be too large. If you think you need a large cache, a good value to start with would be 30% to 40% of physical memory, divided by the database page_size. That leaves the operating system some real memory for file system buffers. Benchmark using that value, then benchmark with half and double values for cache_size. http://www.sqlite.org/pragma.html#pragma_cache_size http://www.sqlite.org/pragma.html#pragma_default_cache_size http://www.sqlite.org/pragma.html#pragma_page_size Note: The PRAGMA [default_]cache_size=n; is expressed as number of database pages, not bytes. -- Regards, Kees Nuyt _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
