Document size and growth patterns in MongoDB - Time & Space Complexity

Time Complexity: Document size and growth patterns

O(n)

Understanding Time Complexity

When working with MongoDB, the size of documents affects how long operations take.

We want to understand how the time to read or write a document changes as the document grows bigger.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// Insert a document with a growing array
const doc = { name: "example", items: [] };

// Add n items to the array
for (let i = 0; i < n; i++) {
  doc.items.push(i);
}

// Insert the document into the collection
await db.collection('test').insertOne(doc);
    

This code builds a document with an array that grows in size, then inserts it into the database.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Adding items to the array inside the document.
• How many times: The loop runs n times, where n is the number of items added.

How Execution Grows With Input

As the number of items n increases, the document size grows, making the insert operation take longer.

Input Size (n)	Approx. Operations
10	About 10 array additions and a small insert
100	About 100 array additions and a larger insert
1000	About 1000 array additions and a much larger insert

Pattern observation: The time grows roughly in direct proportion to n, because each added item increases the document size and work done.

Final Time Complexity

Time Complexity: O(n)

This means the time to build and insert the document grows linearly as the document size grows.

Common Mistake

[X] Wrong: "Adding more items to the document does not affect insert time much because it's just one insert operation."

[OK] Correct: The insert operation must write the entire document, so bigger documents take more time to process and store.

Interview Connect

Understanding how document size affects operation time helps you design efficient data models and answer questions about scaling in real projects.

Self-Check

"What if instead of one large document, we split the items into multiple smaller documents? How would the time complexity change?"

Practice

1. What is the main reason to keep MongoDB documents reasonably small?

easy

A. To make documents harder to read

B. To avoid using indexes

C. To increase the number of collections

D. To improve database speed and reduce storage costs

Solution

1. Step 1: Understand document size impact

   Larger documents take more space and slow down database operations.

2. Step 2: Connect size with performance and cost

   Smaller documents improve speed and reduce storage needs, saving costs.

3. Final Answer:

   To improve database speed and reduce storage costs -> Option D

4. Quick Check:

   Small documents = faster and cheaper [OK]

Hint: Smaller documents mean faster queries and less storage [OK]

Common Mistakes:

• Thinking bigger documents are always better
• Confusing collections with document size
• Ignoring storage cost impact

2. Which MongoDB command shows statistics including average document size and storage size?

easy

A. db.collection.stats()

B. db.collection.insert()

C. db.collection.find()

D. db.collection.update()

Solution

1. Step 1: Identify command for collection stats

   The command db.collection.stats() returns detailed stats about the collection.

2. Step 2: Confirm it includes document size info

   This command shows average document size, storage size, and growth info.

3. Final Answer:

   db.collection.stats() -> Option A

4. Quick Check:

   Stats command = db.collection.stats() [OK]

Hint: Use .stats() to check collection size and growth info [OK]

Common Mistakes:

• Using find() which only queries documents
• Confusing insert() or update() with stats
• Not knowing stats() returns size info

3. Given a collection with documents growing in size over time, what will db.collection.stats() likely show?

medium

A. Increasing avgObjSize and storageSize values

B. Decreasing avgObjSize and storageSize values

C. No change in avgObjSize but increasing storageSize

D. Only the number of documents changes

Solution

1. Step 1: Understand document growth effect

   As documents grow, their average size (avgObjSize) increases.

2. Step 2: Connect growth to storage size

   More or bigger documents increase storageSize to hold data.

3. Final Answer:

   Increasing avgObjSize and storageSize values -> Option A

4. Quick Check:

   Growth means bigger avgObjSize and storageSize [OK]

Hint: Growth means both average document and storage sizes rise [OK]

Common Mistakes:

• Assuming storage size stays constant
• Thinking avgObjSize decreases with growth
• Ignoring storage size changes

4. You run db.collection.stats() but get an error. Which is a likely cause?

medium

A. You used find() instead of stats()

B. You misspelled the collection name

C. You forgot to connect to MongoDB

D. You ran stats() on a database instead of a collection

Solution

1. Step 1: Check command usage context

   A common error is misspelling the collection name, causing 'ns not found' error since the collection doesn't exist.

2. Step 2: Identify error cause

   db.collection.stats() requires an existing collection; misspelling prevents access.

3. Final Answer:

   You misspelled the collection name -> Option B

4. Quick Check:

   stats() works on existing collections only [OK]

Hint: Verify collection name spelling before running stats() [OK]

Common Mistakes:

• Misspelling the collection name
• Forgetting to connect to MongoDB
• Confusing find() with stats()

5. You have a collection where documents grow unpredictably. What is a good strategy to manage document size and growth?

hard

A. Ignore document size and rely on hardware upgrades

B. Keep all data in one large document to avoid joins

C. Split large documents into smaller related documents using references

D. Delete old documents frequently to reduce size

Solution

1. Step 1: Understand document growth challenges

   Unpredictable growth can cause documents to become too large and slow.

2. Step 2: Apply best practice for size management

   Splitting large documents into smaller ones with references keeps sizes manageable and improves performance.

3. Final Answer:

   Split large documents into smaller related documents using references -> Option C

4. Quick Check:

   Split documents to manage size and growth [OK]

Hint: Use references to split big documents for better growth control [OK]

Common Mistakes:

• Keeping all data in one big document
• Ignoring size issues hoping hardware helps
• Deleting data instead of managing structure