[SERVER-18885] Readahead startup warning is inconsistent with the documentation Created: 09/Jun/15 Updated: 11/Oct/18 Resolved: 11/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MMAPv1 |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Joanna Cheng | Assignee: | Gregory Wlodarek |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Storage NYC 2018-10-22 | ||||||||
| Participants: | |||||||||
| Description |
http://dochub.mongodb.org/core/readahead links to http://docs.mongodb.org/manual/administration/production-notes/#readahead, where we recommend:
These 2 suggestions are inconsistent. We should just refer to the docs and keep our recommendation in one place. |
| Comments |
| Comment by Gregory Wlodarek [ 11/Oct/18 ] |
|
Marking this as gone away because if others need to use a non-standard read-ahead value (32kB), that's fine, we don't need to warn them. In regards to the inconsistency with the documentation, the documentation states that 32kB is a value that often works well, and MongoDB recommends a value of 256kB orĀ less. 256kB being the reason to let at least one read-ahead of one large document, since 256kB is the chunk-size of GridFS. |