On Sat, Mar 24, 2012 at 05:36:09PM -0700, Roger Binns scratched on the wall:
> > In my particular scenario - while the raw data being attached and read > > is hundreds of GB - the result sets are only a few GB. > > 2GB is the threshold to switch to 64 bits. That depends on the OS. Some 64-bit OSes will give nearly all the 4GB address space to a 32-bit application. Others, like Windows, will only give half the space, and reserve the other half of the address space for system mappings. > > Whether a RAM-only version would truly run subtantially faster than an > > SSD-based DB - remains to be seen - but the <2GB experiments seem to > > show that in-memory is quite promising. > > Any memory used to store databases is memory that cannot be used for I/O > caching. True, but in-memory databases do not require I/O. Additionally, I/O caching is done by the OS. Even with a 32-bit SQLite process, if the system has more than 2GB of RAM, a 64-bit OS is going to be able to use any additional RAM (including that beyond 4GB) for I/O caching. -j -- 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 _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
