-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/03/12 18:23, Jay A. Kreibich wrote: > That depends on the OS. Some 64-bit OSes will give nearly all the 4GB > address space to a 32-bit application.
Those same OSes make it very easy to compile SQLite in 64 bits so this isn't an issue. > Others, like Windows, will only give half the space, and reserve the > other half of the address space for system mappings. See also /3GB > 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. The scenario was using a ramdisk. If the system has 16GB of memory and 15GB of memory is used for a ramdisk then only 1GB is available for I/O caching. A 32 bit SQLite process can still happily make a 15GB database on a ramdisk, but not in :memory:. The point is to be careful using memory for single purposes (files on a ramdisk) since it can't be used for other things at the same time. Under normal circumstances the OS can use memory for whatever is most needed at a point in time be it caching or for process heap and code. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk9ue0AACgkQmOOfHg372QTYOQCgwq8U2/NmEMqrbt5OlQdwTXVX JDgAn0zFcIxaEa8r43Cbi6W5U+NwdcL8 =1tE1 -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
