Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Remedy off-by-1 error in how to keep Robson's n factor down. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
3618255733e06a2b2faaa85d0fca287b |
| User & Date: | larrybr 2022-01-28 19:28:24.206 |
Context
|
2022-01-29
| ||
| 22:20 | Add documentation for the recent virtual table enhancements. (check-in: 3cca88e77e user: drh tags: trunk) | |
|
2022-01-28
| ||
| 19:28 | Remedy off-by-1 error in how to keep Robson's n factor down. (check-in: 3618255733 user: larrybr tags: trunk) | |
| 17:19 | Mention the new sqlite3_error_offset() interface in the change log. (check-in: 4891c7e52e user: drh tags: trunk) | |
Changes
Changes to pages/malloc.in.
| ︙ | ︙ | |||
888 889 890 891 892 893 894 | <p>The last two allocations can be controlled and/or eliminated by configuring the [pagecache memory allocator], and [lookaside memory allocator] appropriately, as described above. The storage space required for [database connection] objects depends to some extent on the length of the filename of the database file, but rarely exceeds 2KB on 32-bit systems. (More space is required on 64-bit systems due to the increased size of pointers.) | | | 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 | <p>The last two allocations can be controlled and/or eliminated by configuring the [pagecache memory allocator], and [lookaside memory allocator] appropriately, as described above. The storage space required for [database connection] objects depends to some extent on the length of the filename of the database file, but rarely exceeds 2KB on 32-bit systems. (More space is required on 64-bit systems due to the increased size of pointers.) Each parser object uses about 1.6KB of memory. Thus, elements 3 through 6 above can easily be controlled to keep the maximum memory allocation size below 2KB.</p> <p>If the application is designed to manage data in small pieces, then the database should never contain any large strings or BLOBs and hence element 1 above should not be a factor. If the database does contain large strings or BLOBs, they should be read using |
| ︙ | ︙ |