Database size   Larger databases usually benefit from a larger page size. Larger pages hold more information and therefore use space more effectively—particularly if you insert rows that are slightly more than half a page in size. The larger the page, the less page swapping that is required.

Number of rows   Because a row (excluding BLOBs) must fit on a page, the page size determines how large the largest packed row can be, and how many rows you can store on each page. Sometimes reading one page to obtain the values of one row may have the side effect of loading the contents of the next few rows into memory. See Row packing and table definitions.

Query types   In general, smaller page sizes are likely to benefit queries that retrieve a relatively small number of rows from random locations. By contrast, larger pages tend to benefit queries that perform sequential table scans.

Cache size   Large page sizes may require larger cache sizes. When your cache cannot hold enough pages, performance suffers as UltraLite begins swapping frequently-used pages to disk. See UltraLite CACHE_SIZE connection parameter.

Index entries   Page size also affects indexes. The larger the database page, the more index entries it can hold. See Working with UltraLite indexes.

Device memory   Small pages are particularly useful if your database must run on small devices with limited memory. For example, 1 MB of memory can hold 1000 pages that are each 1 KB in size, but only 250 pages that are 4 KB in size.