[DOCS-5907] WiredTiger cache size Created: 27/Jul/15 Updated: 30/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eitan Klein | Assignee: | Kay Kim (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 1 day ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
1) For 3.2 - Default cache size set for 60% of the RAM, we should refresh the docs 2) Our docs should highlight the use cases when smaller wiredtiger cache produce better throughput
3) We can gain throughput w/ larger cache when running w/ database (Dataset) < RAM |
| Comments |
| Comment by Education Bot [ 01/Nov/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |
| Comment by Eitan Klein [ 27/Jul/15 ] |
|
See user feedback on this subject |