{"id":2340,"date":"2018-08-29T17:59:06","date_gmt":"2018-08-29T17:59:06","guid":{"rendered":"http:\/\/dbtut.com\/?p=2340"},"modified":"2018-12-06T13:22:36","modified_gmt":"2018-12-06T13:22:36","slug":"how-to-improve-database-performance-on-mongodb-part-1","status":"publish","type":"post","link":"https:\/\/dbtut.com\/index.php\/2018\/08\/29\/how-to-improve-database-performance-on-mongodb-part-1\/","title":{"rendered":"How To Improve Database Performance on MongoDB Part 1"},"content":{"rendered":"

 <\/p>\n

This little guide is medium in scope, it is not exhaustive. It just gives you an idea to focus<\/p>\n

1 Choose the right storage engine for your specific workload.<\/strong><\/span><\/p>\n

The storage engine is the component of the database that is responsible for managing how data is stored, both in memory and on disk.<\/p>\n

Comparative:<\/p>\n\n\n\n\n\n\n\n
Storage Engine<\/strong><\/td>\nCharacteristics<\/strong><\/td>\n<\/tr>\n
MMAPv1<\/td>\n\n
    \n
  • Is MongoDB\u2019s original storage engine based on memory mapped files.<\/li>\n
  • Is the default storage engine in MongoDB 3.0 and all previous versions.<\/li>\n
  • It was designed for heavy reads<\/li>\n
  • This engine is deprecated with the MongoDB 4.0 release<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
WiredTiger<\/td>\n\n
    \n
  • Starting in MongoDB 3.0, the WiredTiger storage engine is available in the 64-bit builds<\/li>\n
  • Is the default storage engine since version 3.2<\/li>\n
  • Is designed for heavy reads-writes operations uses document-level concurrency control for write operations<\/li>\n
  • Supports compression for journal, all collections and indexes, by default, uses\u00a0 snappy compression library, can be changed for zlib library<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
Encrypted<\/td>\n\n
    \n
  • Starting in MongoDB Enterprise version 3.2<\/li>\n
  • Is based upon WiredTiger, all characteristics regarding WiredTiger also apply to he Encrypted storage engine.<\/li>\n
  • The encryption occurs transparently in the storage layer; i.e. all data files are fully encrypted from a filesystem perspective, and data only exists in an unencrypted state in memory and during transmission.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
In-Memory<\/td>\n\n