Memory and storage engine basics (WiredTiger) in MongoDB - Mini Project: Build & Apply

Memory and Storage Engine Basics with WiredTiger in MongoDB

📖 Scenario: You are managing a MongoDB database for a small online bookstore. You want to understand how to set up and configure the WiredTiger storage engine, which is the default in MongoDB, to optimize memory usage and storage performance.

🎯 Goal: Build a simple MongoDB configuration and query setup that demonstrates how to check and configure WiredTiger memory and storage settings.

📋 What You'll Learn

Create a MongoDB collection named books with sample documents.

Define a variable to hold the WiredTiger cache size configuration.

Write a query to retrieve all documents from the books collection.

Add a command to display the current WiredTiger cache usage statistics.

💡 Why This Matters

🌍 Real World

Understanding and configuring WiredTiger memory and storage settings helps optimize MongoDB performance for real applications like online bookstores.

💼 Career

Database administrators and developers need to know how to monitor and tune storage engines like WiredTiger to ensure efficient data storage and retrieval.

1

Create the books collection with sample documents

Create a MongoDB collection called books and insert these exact documents: { title: "The Great Gatsby", author: "F. Scott Fitzgerald", year: 1925 }, { title: "1984", author: "George Orwell", year: 1949 }, and { title: "To Kill a Mockingbird", author: "Harper Lee", year: 1960 }.

MongoDB

// Insert the specified documents into the books collection
// Your code here

Hint

Use db.books.insertMany() with an array of documents containing the exact fields and values.

2

Define WiredTiger cache size configuration variable

Create a variable called wiredTigerCacheSizeGB and set it to 1 to represent 1 gigabyte of WiredTiger cache size.

MongoDB

db.books.insertMany([
  { title: "The Great Gatsby", author: "F. Scott Fitzgerald", year: 1925 },
  { title: "1984", author: "George Orwell", year: 1949 },
  { title: "To Kill a Mockingbird", author: "Harper Lee", year: 1960 }
])

// Define WiredTiger cache size variable
// Your code here

Hint

Use const wiredTigerCacheSizeGB = 1 to set the cache size variable.

3

Query all documents from the books collection

Write a query using db.books.find() to retrieve all documents from the books collection.

MongoDB

db.books.insertMany([
  { title: "The Great Gatsby", author: "F. Scott Fitzgerald", year: 1925 },
  { title: "1984", author: "George Orwell", year: 1949 },
  { title: "To Kill a Mockingbird", author: "Harper Lee", year: 1960 }
])

const wiredTigerCacheSizeGB = 1;

// Query all documents from books collection
// Your code here

Hint

Use db.books.find() to get all documents.

4

Display WiredTiger cache usage statistics

Add the command db.serverStatus().wiredTiger.cache to display the current WiredTiger cache usage statistics.

MongoDB

db.books.insertMany([
  { title: "The Great Gatsby", author: "F. Scott Fitzgerald", year: 1925 },
  { title: "1984", author: "George Orwell", year: 1949 },
  { title: "To Kill a Mockingbird", author: "Harper Lee", year: 1960 }
])

const wiredTigerCacheSizeGB = 1;

db.books.find()

// Show WiredTiger cache usage statistics
// Your code here

Hint

Use db.serverStatus().wiredTiger.cache to check cache stats.

Practice

1. What is the default storage engine used by MongoDB that balances speed and storage?

easy

A. WiredTiger

B. MMAPv1

C. InMemory

D. RocksDB

Solution

1. Step 1: Recall MongoDB default engine

   MongoDB uses WiredTiger as its default storage engine since version 3.2 for better performance and compression.

2. Step 2: Compare options

   MMAPv1 is older, InMemory is for volatile data, RocksDB is not default in MongoDB.

3. Final Answer:

   WiredTiger -> Option A

4. Quick Check:

   Default engine = WiredTiger [OK]

Hint: Default MongoDB engine is WiredTiger [OK]

Common Mistakes:

• Confusing MMAPv1 as default
• Thinking InMemory is default
• Assuming RocksDB is default

2. Which configuration file setting correctly specifies WiredTiger as the storage engine in mongod.conf?

easy

A. storage:
engine: wiredtiger

B. storage:
engine: WT

C. storage:
engine: wiredTiger

D. storage:
engine: WiredTiger

Solution

1. Step 1: Check correct case for engine name

   The engine name is case-sensitive and must be 'wiredTiger' with lowercase 'w' and capital 'T'.

2. Step 2: Validate YAML syntax

   storage: engine: WT uses unrecognized abbreviation; C uses all lowercase; D uses incorrect capitalization.

3. Final Answer:

   storage: engine: wiredTiger -> Option C

4. Quick Check:

   Correct engine name is wiredTiger [OK]

Hint: Use exact 'wiredTiger' (lowercase w, capital T) in config [OK]

Common Mistakes:

• Using all lowercase 'wiredtiger'
• Using 'WiredTiger' with capital W
• Using abbreviations like 'WT'

3. Given this mongod.conf snippet:

storage:
  engine: WiredTiger
  wiredTiger:
    engineConfig:
      cacheSizeGB: 2

What does the cacheSizeGB setting control?

medium

A. The disk space allocated for WiredTiger files

B. The amount of RAM WiredTiger uses for caching data

C. The number of CPU cores WiredTiger uses

D. The network bandwidth limit for WiredTiger

Solution

1. Step 1: Understand cacheSizeGB meaning

   cacheSizeGB sets how much RAM WiredTiger uses to cache data in memory for faster access.

2. Step 2: Eliminate other options

   It does not control disk space, CPU cores, or network bandwidth.

3. Final Answer:

   The amount of RAM WiredTiger uses for caching data -> Option B

4. Quick Check:

   cacheSizeGB = RAM cache size [OK]

Hint: cacheSizeGB sets RAM cache size for WiredTiger [OK]

Common Mistakes:

• Thinking it controls disk space
• Confusing with CPU or network settings
• Ignoring memory tuning importance

4. You set cacheSizeGB: 0.5 in mongod.conf but MongoDB starts with poor performance. What is the likely cause?

medium

A. cacheSizeGB must be at least 1 GB

B. cacheSizeGB cannot be a decimal value

C. cacheSizeGB must be set under storage.engine directly

D. cacheSizeGB is ignored and does not affect startup

Solution

1. Step 1: Check WiredTiger cache size limits

   WiredTiger performs poorly if cacheSizeGB is less than 1 GB.

2. Step 2: Validate config placement and value type

   Decimal values are allowed; placement under wiredTiger.engineConfig is correct; it is not ignored.

3. Final Answer:

   cacheSizeGB must be at least 1 GB -> Option A

4. Quick Check:

   Minimum cacheSizeGB = 1 GB [OK]

Hint: cacheSizeGB minimum is 1 GB for good performance [OK]

Common Mistakes:

• Using decimal values thinking they are invalid
• Placing cacheSizeGB under wrong config section
• Assuming cacheSizeGB is optional for startup

5. You want to optimize MongoDB performance on a server with 16 GB RAM. Which cacheSizeGB setting is best for WiredTiger, considering MongoDB and OS need memory?

hard

A. Set cacheSizeGB to 14 to maximize cache

B. Set cacheSizeGB to 16 to use all RAM for cache

C. Set cacheSizeGB to 2 because more cache slows down MongoDB

D. Set cacheSizeGB to 8 to leave memory for OS and other processes

Solution

1. Step 1: Understand memory needs

   MongoDB needs memory for cache and other operations; OS and other apps also need RAM.

2. Step 2: Choose balanced cache size

   Setting cacheSizeGB to about half or slightly more (8 GB) leaves enough RAM for OS and avoids swapping.

3. Step 3: Evaluate other options

   14 or 16 GB risks OS starvation; 2 GB is too low for good performance.

4. Final Answer:

   Set cacheSizeGB to 8 to leave memory for OS and other processes -> Option D

5. Quick Check:

   Balance cache and OS memory = 8 GB [OK]

Hint: Use about half RAM for cache to keep system stable [OK]

Common Mistakes:

• Assigning all RAM to cache causing OS issues
• Setting too low cacheSizeGB hurting performance
• Ignoring OS memory needs