Read the article to learn more about WiredTiger Memory Usage in MongoDB. Bobcares, as a part of our Server Management Service offers solutions to every query that comes our way.

WiredTiger Memory Usage in MongoDB

Several DBMS often use the WiredTiger storage engine. The speed can be greatly enhanced by WiredTiger’s efficient use of storage to cache frequently accessed data. It also avoid the need to fetch data from disk. It can also change its caching methods in response to changes in system resources and workload.

The version 3.2 uses the WiredTiger storage engine by default. CacheSizeGB allows us to set up the maximum amount of memory that the engine will use. By default, this is set to around 60% of the system’s useable storage.

So, to prevent user requests from being blocked when storage is full, the engine will starts removing storage when the use exceeds a specific limit.

We can either set the property storage.wiredTiger.engineConfig.cacheSizeGB to a value less than the amount of RAM available in the container. Else, we can also use wiredTigerCacheSizeGB in order to avoid memory issues.

When using the version 3.2, the default setting is to use 1GB of memory. We can also use 60% of the available storage when it exceeds 1GB. Version 3.4 changed this rate with 50%. So, to accept values less than 1Gi, a solution is needed due to a flaw in MongoDB 3.2. So, in the setup, the attribute configString: cache_size= must be set.

MongoDB also uses the filesystem cache. The default engine internal cache size as of MongoDB 3.4, is 256 MB or 50% of RAM minus one GB.

[Want to learn more? Click here to reach us.]

Conclusion

To sum up, our Tech team went over the details of WiredTiger Memory Usage in MongoDB in this article.