[SERVER-22204] Tests should lower WT cache size Created: 15/Jan/16 Updated: 31/May/17 Resolved: 13/Jun/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.8, 3.3.9 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Michael Grundy |
| Resolution: | Done | Votes: | 0 |
| Labels: | test-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Backport Completed: | |||||||||||||||||||||||||||||
| Sprint: | TIG 13 (04/22/16), TIG 14 (05/13/16), TIG 15 (06/03/16), TIG 16 (06/24/16) | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||||||||||
| Description |
|
Currently each mongod gets the default of 60% of total memory. This causes a problem when running tests in parallel since 2 mongods are told they can use over 100% of ram. This is exacerbated by test that spawn many mongods (eg tests of sharded replica sets). |
| Comments |
| Comment by Githook User [ 16/Jun/16 ] |
|
Author: {u'username': u'mgrundy', u'name': u'Mike Grundy', u'email': u'michael.grundy@10gen.com'}Message: (cherry picked from commit dd3d9e3077094a7a19943c8973175725276348db) Conflicts: |
| Comment by Michael Grundy [ 13/Jun/16 ] |
|
mongod will now be launched with --wiredTigerCacheSizeGB=1 by resmoke.py |
| Comment by Githook User [ 13/Jun/16 ] |
|
Author: {u'username': u'mgrundy', u'name': u'Mike Grundy', u'email': u'michael.grundy@10gen.com'}Message: |
| Comment by Robert Guo (Inactive) [ 02/Jun/16 ] |
|
rocks has a similar server option called "rocksdbCacheSizeGB" See this commit for some more detail: https://github.com/mongodb-partners/mongo-rocks/commit/982c182382fdb0de1ebd1c9770bc9fa79372f893 |
| Comment by Mathias Stearn [ 15/Jan/16 ] |
|
We could remove the workaround committed under |