@@ -18,7 +18,7 @@ the :doc:`complete list of FAQs </faq>` or post your question to the
18
18
What are memory mapped files?
19
19
-----------------------------
20
20
21
- Memory mapped files are segments are a way of keeping files and data
21
+ Memory mapped files are a way of keeping files and data
22
22
up to date in memory using the system call ``mmap()``. MongoDB uses
23
23
memory mapped files as its storage engine. By using memory mapped
24
24
files MongoDB can treat the content of its data files as if they were
@@ -30,7 +30,7 @@ How do memory mapped files work?
30
30
31
31
Memory mapping assigns files to a block of virtual memory with a
32
32
direct byte-for-byte correlation. Once mapped, the relationship
33
- between file and memory, allows MongoDB to interact with the data in
33
+ between file and memory allows MongoDB to interact with the data in
34
34
the file as if it were memory.
35
35
36
36
How does MongoDB work with memory mapped files?
@@ -55,9 +55,9 @@ What is the difference between soft and hard page faults?
55
55
---------------------------------------------------------
56
56
57
57
:term:`Page faults <page fault>` occur when MongoDB needs access to
58
- data that isn't currently in active memory. A "hard" page fault,
58
+ data that isn't currently in active memory. A "hard" page fault
59
59
refers to situations when MongoDB must access a disk to access the
60
- data. A "soft" page fault, by contrast merely moves memory pages from
60
+ data. A "soft" page fault, by contrast, merely moves memory pages from
61
61
one list to another, and does not require as much time to complete.
62
62
63
63
What tools can I use to investigate storage use in MongoDB?
@@ -73,11 +73,11 @@ What is the working set?
73
73
74
74
Working set represents the total body of data that the application
75
75
uses in the course of normal operation. Often this is a subset of the
76
- total data size, but the specific size of working set depends on
76
+ total data size, but the specific size of the working set depends on
77
77
actual moment-to-moment use of the database.
78
78
79
79
If you run a query that requires MongoDB to scan every
80
- :term:`document` in a collection, the working set includes every
80
+ :term:`document` in a collection, the working set includes every active
81
81
document in memory.
82
82
83
83
For best performance, the majority of your *active* set should fit in
0 commit comments