Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix typos in the malloc.html document. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | 3.17 |
| Files: | files | file ages | folders |
| SHA1: |
31b59e00e563f695771d50bd9b020879 |
| User & Date: | drh 2017-03-06 11:34:37.556 |
Context
|
2017-03-07
| ||
| 13:05 | Fix the action= link for the search form on pages that are not at the top level. (check-in: 564d1318f8 user: drh tags: 3.17) | |
|
2017-03-06
| ||
| 19:56 | Merge fixes from the 3.17 branch. (check-in: 02cadace0c user: drh tags: trunk) | |
| 11:34 | Fix typos in the malloc.html document. (check-in: 31b59e00e5 user: drh tags: 3.17) | |
|
2017-03-04
| ||
| 20:09 | Fix typo reported by Jeffrey Mattox. (check-in: 1a4aa7fa1d user: drh tags: 3.17) | |
Changes
Changes to pages/malloc.in.
| ︙ | ︙ | |||
499 500 501 502 503 504 505 |
<tcl>hd_fragment pagecache {pagecache memory allocator}</tcl>
<h2> Page cache memory</h2>
<p>In most applications, the database page cache subsystem within
SQLite uses more dynamically allocated memory than all other parts
of SQLite combined. It is not unusual to see the database page cache
| | | 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 |
<tcl>hd_fragment pagecache {pagecache memory allocator}</tcl>
<h2> Page cache memory</h2>
<p>In most applications, the database page cache subsystem within
SQLite uses more dynamically allocated memory than all other parts
of SQLite combined. It is not unusual to see the database page cache
consume over 10 times more memory than the rest of SQLite combined.</p>
<p>SQLite can be configured to make page cache memory allocations from
a separate and distinct memory pool of fixed-size
slots. This can have two advantages:</p>
<ul>
<li><p>
|
| ︙ | ︙ | |||
702 703 704 705 706 707 708 | <a name="heaplimit"></a> <h2> Setting memory usage limits</h2> <p>The [sqlite3_soft_heap_limit64()] interface can be used to set an upper bound on the total amount of outstanding memory that the general-purpose memory allocator for SQLite will allow to be outstanding | | | | 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 | <a name="heaplimit"></a> <h2> Setting memory usage limits</h2> <p>The [sqlite3_soft_heap_limit64()] interface can be used to set an upper bound on the total amount of outstanding memory that the general-purpose memory allocator for SQLite will allow to be outstanding at one time. If attempts are made to allocate more memory than specified by the soft heap limit, then SQLite will first attempt to free cache memory before continuing with the allocation request. The soft heap limit mechanism only works if [memory statistics] are enabled and it works best if the SQLite library is compiled with the [SQLITE_ENABLE_MEMORY_MANAGEMENT] compile-time option.</p> <p>The soft heap limit is "soft" in this sense: If SQLite is not able to free up enough auxiliary memory to stay below the limit, it goes ahead and allocates the extra memory and exceeds its limit. This occurs under the theory that it is better to use additional memory than to fail outright.</p> <p>As of SQLite [version 3.6.1] ([dateof:3.6.1]), the soft heap limit only applies to the general-purpose memory allocator. The soft heap limit does not know about or interact with the [scratch memory allocator], |
| ︙ | ︙ |