- Author
- Not stated in the text; the gist URL names phiresky
- Published
- Undated
- Kind
- Short GitHub gist of settings advice, based on personal experience
- Original
- gist.github.com/phiresky/978d8e204f77feaa0ab5cca08d2d5b27
- Subject
- Databases and storage
- Themes
- Close to the machine
What it is
The gist is a checklist of SQLite pragmas. It claims these settings let a database reach multiple GByte. It also claims they allow many concurrent readers. The text does not name its author.
What it says
- The gist says to enable write-ahead logging for concurrent readers and speed.
- It says synchronous normal is corruption safe in write-ahead mode. It says off can corrupt data, though the author never had problems.
- It says a large mmap_size uses memory mapping and should be much faster on Linux.
- It says a page size of 32768 helped one project that stored large blobs.
- It warns that the write-ahead log can grow without limit. It suggests checkpoints.
What evidence it gives
The gist gives no benchmarks or measurements. It rests on the author's own experience, such as one project for page size. It quotes the SQLite documentation for the optimize pragma and for auto-vacuum.
Interests and limits
The gist is short and undated in its text. The author admits not knowing how much temp_store helps. The page size advice may not suit small rows. The gist does not test any setting.