Documentation Source Text
Check-in [04448a]
Not logged in

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix a typo in mmap.html.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1:04448addda33fd313d320c1bb9cd669df9439242
User & Date: drh 2013-05-23 22:56:49
Context
2013-05-28
13:23
Clarify the license for SQLite documentation. check-in: 419389 user: drh tags: trunk
2013-05-23
22:56
Fix a typo in mmap.html. check-in: 04448a user: drh tags: trunk
11:48
Update the documentation for PRAGMA mmap_size to explain that it can sometimes be a no-op. check-in: a577a4 user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/mmap.in.

53
54
55
56
57
58
59
60
61
62
63
64
65
66
67

<li><p>Performance does not always increase with memory-mapped I/O.  In fact,
    it is possible to construct test cases where performance is reduced
    by the use of memory-mapped I/O, though this is hard to do.</p>
</ol>

<p>Because of the potential disadvantages, memory-mapped I/O is turned
off by default.  To active memory-mapped I/O, use the [mmap_size pragma]
and set the mmap_size to some large number, usually 256MB or larger, depending
on how much address space your application can spare.  The rest is
automatic.  The [PRAGMA mmap_size] statement will be a silent no-op on
systems that do not support memory-mapped I/O.</p>

<h2>How Memory-Mapped I/O Works</h2>








|







53
54
55
56
57
58
59
60
61
62
63
64
65
66
67

<li><p>Performance does not always increase with memory-mapped I/O.  In fact,
    it is possible to construct test cases where performance is reduced
    by the use of memory-mapped I/O, though this is hard to do.</p>
</ol>

<p>Because of the potential disadvantages, memory-mapped I/O is turned
off by default.  To activate memory-mapped I/O, use the [mmap_size pragma]
and set the mmap_size to some large number, usually 256MB or larger, depending
on how much address space your application can spare.  The rest is
automatic.  The [PRAGMA mmap_size] statement will be a silent no-op on
systems that do not support memory-mapped I/O.</p>

<h2>How Memory-Mapped I/O Works</h2>