Introducing Dragonfly Cloud! Learn More

Question: How does WriteConcern affect performance in MongoDB?


WriteConcern in MongoDB is a setting that allows developers to specify the level of acknowledgment requested from MongoDB for write operations. It determines the level of assurance that MongoDB provides when reporting on the success of a write operation, which directly impacts both data durability and the performance of your database operations.

Understanding WriteConcern

The WriteConcern setting can take several forms:

  • { w: 0 }: The driver returns immediately without waiting for any acknowledgment from the server. This mode offers the highest performance but the least data safety.
  • { w: 1 }: MongoDB acknowledges the write operation after committing it to the primary's in-memory storage. This is the default setting, offering a balance between performance and data safety.
  • { w: >1 }: The write operation is acknowledged after being replicated to a specified number of replica set members. Increasing this number enhances data durability at the cost of performance.
  • { w: 'majority' }: The write operation is acknowledged after being committed by a majority of the replica set members, ensuring the write will not be rolled back under normal conditions.

Impact on Performance

  • Low WriteConcern (e.g., { w: 0 }) speeds up write operations because the application does not wait for MongoDB to acknowledge the operation. This is suitable for applications where losing some writes is acceptable compared to the benefit of faster response times.
  • High WriteConcern (e.g., { w: 'majority' } or { w: 3 }) ensures greater data safety but requires more network communication and disk I/O operation among replica set members. This can significantly slow down write operations, particularly in high-load systems or systems with large geographical distances between replica set members.

Use Cases

  • High-throughput logging or analytics: Where losing some data is permissible, a lower WriteConcern can improve performance.
  • Financial transactions or critical data management: Applications requiring high data integrity should use a higher WriteConcern to ensure data is safely replicated across multiple nodes.

Code Example

Adjusting WriteConcern in a write operation:

db.collection('users').insertOne( { name: "John Doe", email: "" }, { writeConcern: { w: 'majority', j: true, wtimeout: 5000 } } );

In this example, the insert operation waits for a majority of the replica set members to acknowledge the write and also requests that the write operation be journaled (j: true). It sets a timeout (wtimeout) of 5000 milliseconds, after which the operation will fail if the desired WriteConcern cannot be satisfied.


Choosing the right WriteConcern is crucial for balancing performance and data durability in a MongoDB application. Lower levels of WriteConcern can significantly speed up write operations at the risk of losing data, whereas higher levels ensure data safety but can impact performance. Consider your application's requirements carefully when configuring WriteConcern.

Was this content helpful?

White Paper

Free System Design on AWS E-Book

Download this early release of O'Reilly's latest cloud infrastructure e-book: System Design on AWS.

Free System Design on AWS E-Book

Start building today 

Dragonfly is fully compatible with the Redis ecosystem and requires no code changes to implement.