[DOCS-7669] wiredTigerCacheSizeGB, inMemorySizeGB default and floor lowered and can now be specified as a float Created: 16/Apr/16 Updated: 06/Dec/22 Resolved: 20/Oct/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.5 |
| Type: | Task | Priority: | Critical - P2 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | docs-3.4 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 7 years, 17 weeks ago | ||||||||||||||||
| Story Points: | 0.25 | ||||||||||||||||
| Description |
|
See: The minimum floor for wiredTigerCacheSizeGB has been lowered from 1GB to 256MB to better support low memory machines. Also, the default setting has been lowered from 60% to 50% of available memory (I believe the documentation was never updated to reflect the 60% change made in 3.2, so this may be a no-op). To better support fine grained control of the cache size, it is also now possible to specify the setting as a float, for example --wiredTigerCacheSizeGB 2.4, etc. The maximum cache size remains 10TB. These settings are the same for both the WiredTiger and the inMemory storage engine. This change is onlyl in effect for current master which will become 3.4.0 |
| Comments |
| Comment by Kay Kim (Inactive) [ 20/Oct/16 ] |
|
xgen-internal-githook Githook User added a comment - Oct 19 2016 09:16:10 PM GMT-0400 Message: |