On 4/18/19, Stephen Chrzanowski <[email protected]> wrote: > I'm wondering > if there is going to be any optimization internally from SQLite by making > the page size, say, 180k? (
SQLite handles storing 200KB blobs just fine. It has been doing so routinely for time out of mind. Do not stress over the details of how it does so - that is a premature optimization. Just be assured that it works. Once you get your application up and working, if you want to optimize at that point, simply construct some test databases and manually change the page size to each of the eight different allowed SQLite page sizes (512, 1024, 2048, 4096, 8192, 16384, 32768, and 65536) and check to see the storage efficiency and performance at each page size. Then use whichever one works best. They should all work correctly - it is only a question of performance and size. And even then, the difference will be marginal. If you are concerned about unused space in the file, run the "sqlite3_analyzer.exe" utility on a database to get a detailed analysis of the unused space in the database file. Typically, storing blobs in an SQLite database will use *less* space than storing those same blobs as separate files in the filesystem. See https://www.sqlite.org/fasterthanfs.html for further analysis. -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
