[DOCS-12587] Is maxIndexBuildMemoryUsageMegabytes and wiredTigerCacheSizeGB related? Created: 01/Apr/19  Updated: 29/Oct/23  Resolved: 01/May/19

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Feedback Priority: Major - P3
Reporter: Manivannan Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 4 years, 41 weeks, 1 day ago
Epic Link: DOCSP-1769

 Description   

wiredTigerCacheSizeGB

Defines the maximum size of the internal cache that WiredTiger will use for all data.

For example, on a system with a total of 4GB of RAM the WiredTiger cache will use 1.5GB of RAM (0.5 * (4 GB - 1 GB) = 1.5 GB). So the remaining 2.5 GB RAM is available to the system processes.

maxIndexBuildMemoryUsageMegabytes

Default: 500

Limits the amount of memory that simultaneous foreground index builds on one collection may consume for the duration of the builds.

My question here is, the 500 MB of maxIndexBuildMemoryUsageMegabytes will be used from 1.5 GB of Wired Tiger Cache or 2.5 GB remaining RAM?



 Comments   
Comment by Kay Kim (Inactive) [ 01/May/19 ]

Heh - Forgot to resolve ticket earlier.

Comment by Githook User [ 03/Apr/19 ]

Author:

{'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}

Message: DOCS-12587: v3.4 clarification between maxIndexBuildMemoryUsageMegabytes param and wiredTigerCacheSizeGB conf setting
Branch: v3.4
https://github.com/mongodb/docs/commit/bbac09620e69a789cc753a58c8d5724bbdb594b8

Comment by Githook User [ 03/Apr/19 ]

Author:

{'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}

Message: DOCS-12587: v3.6 clarification between maxIndexBuildMemoryUsageMegabytes param and wiredTigerCacheSizeGB conf setting
Branch: v3.6
https://github.com/mongodb/docs/commit/a633f77de251327da011845eed63fa554f4fbe65

Comment by Githook User [ 03/Apr/19 ]

Author:

{'email': 'kay.kim@10gen.com', 'name': 'Kay Kim', 'username': 'kay-kim'}

Message: DOCS-12587: v4.2 clarification between maxIndexBuildMemoryUsageMegabytes param and wiredTigerCacheSizeGB conf setting
Branch: master
https://github.com/mongodb/docs/commit/b0799d13c7e80770495121226db3d8776c36daf0

Comment by Githook User [ 03/Apr/19 ]

Author:

{'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}

Message: DOCS-12587: v4.0 clarification between maxIndexBuildMemoryUsageMegabytes param and wiredTigerCacheSizeGB conf setting
Branch: v4.0
https://github.com/mongodb/docs/commit/be58cb125091a7b6ccda87eca5cfa0519f69391a

Comment by Manivannan [ 02/Apr/19 ]

Thanks Eric for the clarification.

Comment by Eric Milkie [ 02/Apr/19 ]

The memory used by index builds for sorting is not shared with the WiredTiger cache. In your question, the answer is "2.5 GB remaining RAM".

Generated at Thu Feb 08 08:05:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.