[SERVER-36396] WiredTiger cache size should be specifyable in megabytes Created: 01/Aug/18  Updated: 20/Jul/20  Resolved: 01/Aug/18

Status: Closed
Project: Core Server
Component/s: WiredTiger
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Oleg Pudeyev (Inactive) Assignee: Kyle Suarez
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-23624 Allow wiredTigerCacheSizeGB to be spe... Closed
is duplicated by SERVER-44007 Collection level metadata Closed
Participants:

 Description   

Drivers run tests on different cluster configurations, and all of these cluster configurations are run on the same machine (the one the driver developer uses). The tests deal with very small amounts of data, several megabytes at most for the entire test suite. Even so my mongod processes are growing from 150 mb RSS to 500 mb RSS.

The commonly referenced tunable is wired tiger cache size, and this is specified in gigabytes. 1 gb is too much for driver tests, and many other tests in fact. I would prefer to have a cache on the order of 100-250 mb.



 Comments   
Comment by Oleg Pudeyev (Inactive) [ 01/Aug/18 ]

My bad, it is.

Comment by Kyle Suarez [ 01/Aug/18 ]

I think SERVER-23624 gives you what you want – specify the value as a floating-point number.

Generated at Thu Feb 08 04:42:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.