Delete all documents in collection in MongoDB - Time & Space Complexity

Time Complexity: Delete all documents in collection

O(n)

Understanding Time Complexity

When deleting all documents in a MongoDB collection, it's important to understand how the time it takes grows as the collection gets bigger.

We want to know how the number of documents affects the work MongoDB does to remove them all.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

    db.collection.deleteMany({})
    

This command deletes every document in the collection by matching all documents with an empty filter.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: MongoDB scans through each document to delete it.
• How many times: Once for every document in the collection.

How Execution Grows With Input

As the number of documents grows, the time to delete all of them grows roughly in direct proportion.

Input Size (n)	Approx. Operations
10	About 10 document deletions
100	About 100 document deletions
1000	About 1000 document deletions

Pattern observation: The work grows steadily as the number of documents increases.

Final Time Complexity

Time Complexity: O(n)

This means the time to delete all documents grows linearly with the number of documents.

Common Mistake

[X] Wrong: "Deleting all documents is instant no matter how many there are."

[OK] Correct: MongoDB must visit each document to remove it, so more documents mean more work and more time.

Interview Connect

Understanding how operations scale with data size helps you explain database behavior clearly and shows you think about efficiency in real projects.

Self-Check

"What if we delete documents using a filter that matches only half the collection? How would the time complexity change?"