MongoDB WiredTiger

A Technical Introduction to WiredTiger

Document-level Concurrency
In-memory performance
Multi-core scalability
Checksums
Compression
Durability with & without journaling

 
MongoDB 3.0 introduces a new pluggable storage engine API and a new storage engine called WiredTiger.
The engineering team behind WiredTiger team has a long and distinguished career, having architected and built Berkeley DB, now the world’s most widely used embedded database.
In this talk we will describe our original design goals for WiredTiger, including considerations we made for heavily threaded hardware, large on-chip caches, and SSD storage.
We’ll also look at some of the latch-free and non-blocking algorithms we’ve implemented, as well as other techniques that improve scaling, overall throughput and latency. Finally,
we’ll take a look at some of the features we hope to incorporate into WiredTiger and MongoDB in the future.

https://www.mongodb.com/world2015

 
Concurrency Control in MongoDB 3.0

This talk will describe the changes which went into MongoDB 3.0 in order to allow storage engines to achieve their maximum concurrency potential.
In MongoDB 3.0, concurrency control has been separated into two levels: top-level, which protects the database catalog, and storage engine-level,
which allows each individual storage engine implementation to manage its own concurrency. We will start from the top and introduce the concept of multi-granularity locking and how it protects the database catalog.
We will then explain how the MongoDB lock manager works and how it allows storage engines to manage their own concurrency control without imposing any additional overhead.