mongodb存储引擎

内存映射文件对MMAPv1引擎是很重要的部分，通过使用内存映射文件，mongodb将数据文件看成是在内存中，所以提供了快速的操作及处理访问数据很简单的方式。
对于访问的文档放到内存中，没有访问的不会映射到内存中。
默认情况下mongodb每60s写数据文件到磁盘，100毫秒写次journal文件。很多情况下，mongodb和操作系统会很频繁的刷新数据到磁盘，所以上面的值只是代表了理论上的最大值。

b.collection.dataSize() to return data size in bytes for the collection.
db.collection.storageSize() to return allocation size in bytes, including unused space.
db.collection.totalSize() to return the data size plus the index size in bytes.
db.collection.totalIndexSize() to return the index size in bytes.

查看每个库的状态
db._adminCommand(“listDatabases”).databases.forEach(function (d) {
mdb = db.getSiblingDB(d.name);
printjson(mdb.stats());
})
集合状态
db._adminCommand(“listDatabases”).databases.forEach(function (d) {
mdb = db.getSiblingDB(d.name);
mdb.getCollectionNames().forEach(function(c) {
s = mdb[c].stats();
printjson(s);
})
})
mongodb不需要使用swap space

The journal is a log that helps the database recover in the event of a hard shutdown. There are several configurable options that allows the journal to strike a balance between performance and reliability that works for your particular use case.

GridFS is a versatile storage system that is suited to handling large files, such as those exceeding the 16 MB document size limit.
存储引擎的类型，wiredtiger是默认的类型，
WiredTiger is the default storage engine starting in MongoDB 3.2. It is well-suited for most workloads and is recommended for new deployments. WiredTiger provides a document-level concurrency model, checkpointing, and compression, among other features. In MongoDB Enterprise, WiredTiger also supports Encryption at Rest.
For most read and write operations, WiredTiger uses optimistic concurrency control. WiredTiger uses only intent locks at the global, database and collection levels. When the storage engine detects conflicts between two operations, one will incur a write conflict causing MongoDB to transparently retry that operation.

Some global operations, typically short lived operations involving multiple databases, still require a global “instance-wide” lock. Some other operations, such as dropping a collection, still require an exclusive database lock.

MongoDB configures WiredTiger to create checkpoints (i.e. write the snapshot data to disk) at intervals of 60 seconds or 2 gigabytes of journal data.

内存使用，内存使用再配置文件中没有地方设置
Changed in version 3.2: Starting in MongoDB 3.2, the WiredTiger internal cache, by default, will use the larger of either:

60% of RAM minus 1 GB, or
1 GB.
For systems with up to 10 GB of RAM, the new default setting is less than or equal to the 3.0 default setting (For MongoDB 3.0, the WiredTiger internal cache uses either 1 GB or half of the installed physical RAM, whichever is larger).

For systems with more than 10 GB of RAM, the new default setting is greater than the 3.0 setting.

Via the filesystem cache, MongoDB automatically uses all free memory that is not used by the WiredTiger cache or by other processes. Data in the filesystem cache is compressed.

To adjust the size of the WiredTiger internal cache, see storage.wiredTiger.engineConfig.cacheSizeGB and –wiredTigerCacheSizeGB. Avoid increasing the WiredTiger internal cache size above its default value.

MMAPv1 is the original MongoDB storage engine and is the default storage engine for MongoDB versions before 3.2. It performs well on workloads with high volumes of reads and writes, as well as in-place updates.